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: Number of steps per procedure From:"Wollt, Richard C" <Richard -dot- Wollt -at- UNISYS -dot- com> To:"'TECHWR-L'" <TECHWR-L -at- lists -dot- raycomm -dot- com> Date:Wed, 18 Oct 2000 14:00:01 -0600
My opinion is that it takes as many steps as it takes. The + - seven rule
is great for things you need to memorize, but not really applicable to a
procedure that you follow from a written page.
The grouping of sub-steps you have done should help the user follow the
procedure and make it seem more organized.
Please warn the user up front that once he starts the procedure he must
complete it, or start over from the beginning at some later time.
Dick Wollt
Unisys Product Information
-----Original Message-----
From: Tara English-Sweeney [mailto:tesweeney -at- novadigm -dot- com]
Sent: Wednesday, October 18, 2000 2:55 PM
To: TECHWR-L
Subject: Number of steps per procedure
I come from the school of thought that says you should limit the number of
steps in a procedure. The old rule of 7 +/- 2 is usually comfortable to me.
I'm flexible - and am ok going up to as many as 10 or 12 steps. However, in
my current project, there are 20+ steps to complete some of the procedures.
The one that prompted this email is actually 19 steps.
