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: Organizational structure - where does From:Janice Gelb <janiceg -at- marvin -dot- eng -dot- sun -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Tue, 10 Oct 2000 09:45:33 -0700 (PDT)
While certainly technical writing work can get done no matter where the
writers report in the org chart, I do think there is an advantage to
*not* reporting to engineering: most people here have probably been in
a situation where a company wanted to ship *right now* even if the docs
had not been revised to match bug fixes, late technical changes, etc.
If the writers report to engineering, they're going to be under
pressure from their bosses and not have much leeway to resist. If
they're in a separate pubs department, or at least QA, they will at
least have the support of their upper management for this stand.
*******************************************************************
Janice Gelb | The only connection Sun has with
janice -dot- gelb -at- eng -dot- sun -dot- com | this message is the return address. http://www.geocities.com/Area51/8018/index.html
"The first Halloween prank ever, played by a group of Druid
teenagers, was Stonehenge. (`HEY! You kids get those rocks
OFF my LAWN!')" -- Dave Barry
