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.
> >The problem that arises is that in
> >our user manuals, there tends to be
> >a lot of duplication of very simple
> >information, as writers try to cover
> >all possible bases in each section/
> >procedure... we also tend to illustrate
> >every freakin' move a user has to make
> >in a procedure... even a simple
> >"Click OK."
Having worked in a crisis center before (and working under extreme stress),
my thought processes were taken up in accessing the situation - there was
none left for wondering about - should I click ok or not. For the procedures
for any situation we had flow charts (this was before the center had
computers) with yes/no, if yes, then .., if no, then... Every little step
was there - all based on previous real life situations and tested to the
max. And like several others have mentioned, turnover was high so few ever
had the chance to etch the procedures on their brains and be able to do them
in their sleep.
Keep the "Click ok."s. Repeat them in every procedure when appropriate. It
may be a pita for you but it helps save brain functions for more important
things...