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.
Too many steps, take some out (was RE: If you were making a FAQ...
Subject:Too many steps, take some out (was RE: If you were making a FAQ... From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:Paul Hanson <twer_lists_all -at- hotmail -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 30 Aug 2012 17:21:10 -0400
Paul Hanson [mailto:twer_lists_all -at- hotmail -dot- com] said:
> I used to work at a company that had a long procedure to add a XYZ to
> system. One of the tasks I completed while I was there was an audit
> of that
> procedure and it expanded to something like 34 steps (totally
> breaking the
> +/- 7 rule but don't go there).
I'm going there. There's no such rule.
A procedure takes as many steps as it takes.
If it's a LOT of steps, you can insert some headings at milestones,
and maybe restart the numbering after each heading. Maybe,
number - or letter - the headings. But if it's that long AND is broken
into sections, you should probably put a note at the front
telling the customer to expect that the entire procedure goes
all the way from major-step A to major-step F, each one of those
major steps including several numbered sub-steps... or however
you want to phrase it.
Whatever you do, don't give the customer an opportunity to
think that they are done before they've actually accomplished
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.