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: Dev. Cycle and the Manual From:Chris Kowalchuk <chris -at- BDK -dot- NET> Date:Tue, 4 May 1999 14:21:12 -0400
Sounds tricky to coordinate on a completely new product. However, I once
worked for a company that used the manual as part of the specifications
when it came to redesign, or a new rev. if you will. That's because the
manual was written in accordance with specs (requirements), modified
after field testing and user input (of the previous product). When it
came time for rev 2, the manual was used to record management decisions
based on user feedback. Thus, if there was any doubt as to how the thing
was supposed to work (or look), even the designers could refer to the
manual. Doing it on a new product though? Sounds like a tall order in
practice. It would be nice to work in an environment that organized--a
sort of manager's dream, I suppose...
