RE: Features of a well-written procedure

Subject: RE: Features of a well-written procedure
From: Bill Burns <bburns -at- scriptorium -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 18 Dec 2000 08:49:26 -0700


The five-to-seven rule is a valid principle used in documentation, sales,
and marketing.

In some contexts, yes.

The Rule of Seven is also observed in ancient literature for the exact same
reason: easy recall for the oral traditions.

And this is one of those contexts.

These are just a few examples. I once presented a workshop on using the Rule
of Seven for marketing. Someone in the audience asked about "the 10
commandments." Good question. I asked everyone to write down the 10
commandments as they remembered them. Then, I took an unscientific poll
(raising hands) by asking "how many did you get?" The average
was...........seven.

The similarity in both of these contexts is that the individual needs to remember the 7 steps?to internalize them. As I recall, that figure based on limitations to our short-term memory. Essentially, people can usually store 5-to-9 pieces of information in their short-term memory. (I've most commonly seen people say "7, plus or minus 2", but it all works out the same.)

If you're writing procedures that you want someone to internalize (that is, if your purpose is to train them to act without assistance), then this rule might be useful. It would then make sense to break down procedures into groups of 5-to-9 steps.

Not all procedures are written for people to internalize immediately. Sometimes, it's information that a user will rarely use. In this case, the rule is pointless. Recall isn't your aim; clear instruction is. And sometimes, clear instruction requires more than 9 steps. Mind you, I'm not suggesting that we all need to be less concise, just that we shouldn't artificially constrain a procedure because of a rule that might not be applicable in all situations.

I've read a few articles debunking this "rule" for use in procedure writing, and we've had a few discussions about it on this list in the past. The archive should have quite a bit on this topic, as well as citations for a number of good articles.


Bill Burns, Senior Technical Consultant, Scriptorium Publishing
FrameMaker ACE, WebWorks Publisher Certified Trainer
bburns -at- scriptorium -dot- com - 208-484-4459
http://www.scriptorium.com


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY.
http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.

Take XML and Tech Writing courses online! Our instructor-led courses
(4-6 hrs/wk) give you "hands on" experience at your convenience. STC members
get 20% off! http://www.online-learning.com/index.html.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.


Previous by Author: Re: FWD: RE: Troublesome Writers
Next by Author: RE: Features of a well-written procedure
Previous by Thread: RE: Features of a well-written procedure
Next by Thread: RE: Features of a well-written procedure


What this post helpful? Share it with friends and colleagues:


Sponsored Ads