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.
Downing, David wrote:
> Lauren
>
> Okay, so you just refer to the window without explicitly saying it
> opened. That makes sense. However, I am still concerned about the
> situation where something goes wrong and the window isn't displayed as
> it should be. You say that's outside the scope of the instructions
Instructions fail if task analysis fails.
Take the "Print" task as an example. Assume that you've ruled out all of
the peripheral print topics about changing toner cartridges, installing,
administering, configuring printer, ...
You just want to write the procedure for the user who needs to print.
You know where the buttons that need clicking are. Have you analyszed
the task sufficiently to write a foolproof procedure? Is a simple
instruction telling how to locate and click buttons enough for this task?
Let's get serious about this. The user's goal in doing this procedure is
not to locate and click buttons. The procedure is supposed to get
something printed. Failure to accomplish that, with results like
walking down the hall to the printer room and finding no printout,
aren't what this procedure is about, is it? It will be part of the
result set if the procedure abandons you before you before giving the
result of the print command.
1. Click the Print button.
The print job should appear immediately in the print queue.
For more information, see "Print Queues."
IMHO, foolproof does not come easy, but stating what the result is
supposed to be, is cheap, graphic insurance that you, at least, haven't
sent your users down the hall for no good reason.
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-