TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Never lead with a graphic From:rebecca_hopkins -at- comcast -dot- net (Rebecca Hopkins) To:"Tech Whirlers" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 08 Jul 2008 20:33:45 +0000
John,
The graphic represents the functionality at a very basic level - the big picture. The explanation is the detail the graphic does not express. It is the most important thing, because it is the starting point. If they don't understand why they are being presented with the graphic, then the graphic needs improvement, not the text.
This graphic is like a bus map. First you want to see the map that shows where the bus goes, then you want to see the text schedule that lists when the bus stops at your location. If I tell you that the 57 stops at here at 3:45, you'll say so what? If you see the map first, you'll know that you can take the 57 to Packard's Corner - if that's where you want to go, now you care when it stops here.
Does that make sense?
I think that's what Edward Tufte would say. (Thanks, Voxwoman!) I think that's the argument I'll use with my boss.
-----
Rebecca
-------------- Original message ----------------------
From: "John Posada" <jposada99 -at- gmail -dot- com>
> Rebecca...the graphic ISN'T the most important thing and it's not the first
> thing you want the user to see. It is the functionality in the graphic that
> is what you wamt the user to understand, and if you present the graphic
> first, how will they know why they see it and what they are supposed to do
> with it? I'm on your boss' side. Explain what it is they are suppo0sed to be
> doing, then include what they do in the graphic, then show the graphic.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-