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:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:RShuttleworth -at- visualplant -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:09 Feb 2004 17:19:07 GMT
Documentation belongs in whatever organization in your
company values it the most. This will vary regardless
of the size of the company.
In my own experience as a writer/publications manager,
I have reported to R&D (2 companies), Product Support
(2 companies) and Marketing (1 company). R&D has been
the best, followed by Marketing, with Product Support
trailing all in the dust.
Gene Kim-Eng
------- Original Message -------
On
Mon, 9 Feb 2004 10:01:28 -0700 ?wrote:
One of the issues we face is the question of advocacy when it comes to
budget allocations, etc. I don't think R&D really understand what we do,
anyway (they just accept that manuals are produced), but wherever we fit
we would need someone to fight our corner.
So we are looking at where Documentation belongs, and I'd like to draw on
the opinions of those who have gone this route. We're clearly not talking
about the IBMs or GMs of this world, but if you work for a small-to-medium
company, I'd be interested to know where you fit in.
