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: Corporate writing group structure From:Alexia Prendergast <alexiap -at- SEAGATESOFTWARE -dot- COM> Date:Thu, 2 Oct 1997 16:52:33 -0400
I've worked for doc managers, development managers, as part of a group,
and on my own. To be honest, the experience depended on the people
(managers, the corporate culture, my fellow writers) more than the
actual organizational structure. I've always gotten involved with the
product, regardless of the structure. That depends on your initiative,
Again, I think all of these structures can work--depends if the
structure works for the people and the organization.
Tech Pubs Manager
Seagate Software (Durham, NC, USA) mailto:alexiap -at- seagatesoftware -dot- com
>Larry Weber pondered:
>Presently, the writers in our company are assigned to a particular
>product. These writers report to the product manager. One of the
>management honchos wants to hire a Writing Manager and have all writers
>report to that person. This would allow them to distribute writers to
>different products more efficiently. It's said that the writers will be
>"experts" in a particular product, but will help out as needed on
>I'm not exactly thrilled about this. I like to dig my teeth into a
>product and contribute to the design--something I fear will be difficult
>if I'm being reassigned to different products often.
>Anyone have any experience--good or bad--in such a transition?