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: Where does Documentation belong? From:"Edwin Skau" <edskau -at- hotmail -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 12 Feb 2004 12:26:54 +0530
Documentation belongs in the department that has a vested interest in your
output.
In a company where poor documentation does not represent (at least not
realised by management) a significant impact on the bottomline*, you will be
treated as a prop/necessary evil.
It is very very very important to map to someone who understands the
importance of empowering users with the knowledge to use your products
efficiently. Without this, you're the filling in an idiot sandwich, driving
those below you (and incurring their everlasting wrath) to achieve goals
that mean nothing to those above.
Then, even if you sit your ass down and work it to the bone like Andrew
always advocates, and your technical, analytical and writing abilities made
the mountains crumble and the seas roar, your nuts are popcorn.
