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: stone soup From:Cyndy Davis <kivrin -at- ZDNETMAIL -dot- COM> Date:Tue, 1 Sep 1998 15:25:10 -0700
And the next soldier down the line adds a couple more:
> 1. Someone tells me 'we don't really have a procedure for that'.
(CD)1a. They ask, "Could you whip one up? I'm sure it will only take 1 or 2 pages. How about tomorrow?"
> 2. I ask them what information DOES exist.
> 3. They give me a few lines of information.
(CD)3a. They remember that so-and-so once emailed them and might know something. They'll forward you the email.
> 4. I type those up.
[Betsy Shoolbred] 4a. Look at whatever screen graphics are
available or maybe get an alpha version of the procedure installed. From
what I can decipher, type up something that seems logical to me.
> 5. I give the typed up version to someone else in the process. who says,
> "Well, that's almost true - except that we also do the following." And
> adds/corrects lines.
> 6. I take it back to the first person who responds, usually by remembering
> yet
> something else.
(CD) 6a. Three weeks later you get those emails mentioned in 3a.
6b. Correspond several times with original emailer. Add more information to document.
6c. Scour internal library for text that original emailer remembers having some info in it "Its a size A4 paper manual with a blue cover." You find the manual, its 8 1/2 by 11 with a red cover.
> 7. After several iterations of this sort, I find myself with something
> like an
> actual first draft. Maybe I even see spots where a diagram would help.
> 8. A few drafts and diagrams later, WE HAVE A DOCUMENT!!!