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.
> There's always at least a title, which may be sufficient to identify
> the task to be performed. For example, "Create a New Project File" or
> "Delete a File" might not need any further description.
You might have a point if all procedures consisted of a linear sequence
of steps that led to precisely one end result completely described by
the title or introduction.
But in my experience, that's often not the case. Even for a procedure
entitled "Create a New Project File," I suspect there might be some
options offered and decisions to be made. The question is, how do you
inform the reader of the options about which they must decide?
I contend that it's been pretty well accepted for many years that the
form
If you want A, do X.
If you want B, do Y.
imposes less cognitive load on the reader than
Do X if you want A.
Do Y if you want B.
In the former, the reader who doesn't want A can stop and skip ahead
upon learning the condition, without having to read the instruction
regarding what to do. In the latter, the reader must absorb the
instruction, refrain from acting on it immediately (hopefully), and then
discard it upon learning that it only applies to those who want A.
Sorry, I can't even understand why there's any argument about this.
Richard
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-