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: On-Line Help User Data From:Glenda Jeffrey <jeffrey -at- HKS -dot- COM> Date:Wed, 27 Mar 1996 13:22:54 GMT
Susan W. Gallagher (sgallagher -at- expersoft -dot- com) wrote:
: * Users won't read procedures that are more than 3 or 4 steps
So, what is the alternative if the procedure you're writing truly
has 8 or 9 steps? I can think of a few:
o Remove any steps which seem obvious and hope the novice figures
it out.
o Combine multiple steps into logical "meta-steps" with more detailed
steps underneath.
o Break the procedure into several procedures.
Any other suggestions? Any ideas on what works best in which situation?
(The procedures I have in mind are the type that document how to
use various parts of a GUI.)
--
Glenda Jeffrey Email: jeffrey -at- hks -dot- com
Hibbitt, Karlsson & Sorensen, Inc Phone: 401-727-4200
1080 Main St. Fax: 401-727-4208
Pawtucket, RI 02860 Web: http://www.hks.com
