RE: Visuals in work instructions: how many is too much?

Subject: RE: Visuals in work instructions: how many is too much?
From: "Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 6 Jun 2007 08:52:19 -0600

Stephanie Bryant wrote:

> Today, I encountered a fun problem on my computer involving
> user interfaces. Every time I launched a particular program,
> it displayed the window and the menu bar, but no buttons or
> other UI elements. And yet, if I clicked randomly on the
> toolbar, things happened. The non-displaying buttons were
> *active* but did not show up. <snip>
>
> If there had been a set of screen shots showing me what the
> screens looked like, I would at least have known what I
> should be looking at, and what areas of the screen would "do
> stuff." I would have known which area to click to accept the
> license agreement that I couldn't read.
>
> Moral of the story: Use as many graphics as you need to to
> give the user a complete picture of the task. One per step in
> a task isn't too many, if the layout supports it. Be generous
> and articulate with your graphics, be they screen shots,
> diagrams, flowcharts, or photographs.

Umm, yeah -- if the goal of your manual is to enable your readers to use
the product _in an absurdly defective state_. And to encourage them to
accept a license agreement they can't read.

Or, instead of showing your readers a bunch of pictures so they can
"live with" a completely broken UI, you could put in something like
this: "Note: If you don't see the ABC and DEF buttons, there is a
problem with your XYZ file. To display the window correctly, ..." --
thus making a few words worth many pictures.

Just an idea.

Richard


------
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------




^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.


References:
Re: Visuals in work instructions: how many is too much?: From: Stephanie Bryant

Previous by Author: RE: This too is technical communication
Next by Author: RE: This too is technical communication
Previous by Thread: Re: Visuals in work instructions: how many is too much?
Next by Thread: RE: Visuals in work instructions: how many is too much?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads