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: Establishing a documentation process From:Emily Skarzenski <eskarzenski -at- DTTUS -dot- COM> Date:Fri, 8 Mar 1996 10:11:36 CST
Geoff Hart said:
> Here's the simplistic outline that I'd like you folks to help me
> fill in, modify or otherwise debug: <snip>
> 1. Define product features
> 2. Create mockup of user interface
> 3. Begin documentation of features and interface
> 4. Freeze features/interface (if not already done)
> 5. Complete documentation
> 6. Begin beta testing
> 7. Revision and final distribution
Don't forget about audience analysis (for the *product*, not just the
documentation). When this is done for a product, it is often called
"market research."
This should be done before #1... and will make #1-3 easier. Making
decisions about product features, interface, and doc design/style is
hard enough without having to reconcile differing opinions about who
the users are and what they want.
Emily M. Skarzenski
Deloitte & Touche/ICS - Chadds Ford, PA
eskarzenski -at- dttus -dot- com
