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.
In your company, who decides what the documentation requirements are?
We are implementing the Software Product Life Cycle concept (attempting to
impose order on chaos), and I just got out of a meeting in which I was
informed that Marketing decides what documentation is required, whether a
user manual, or online help, or both or something else entirely, and this
seems ridiculous to me.
I can see Marketing making *recommendations*, but I think that the decision
about what documents are created should be made by the people who have the
best idea what vehicle will best serve the product and the audience in
question.
What do you think?
==========================
Obligatory bad haiku:
Ah, reality
sets in too soon. Alarm rings:
Monday morning! ARGH!
Linda Castellani
Technical Writer
GRIC Communications, Inc.
1421 McCarthy Blvd.
Milpitas, CA 95035
