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.
From: Bob Boeri, 76001,2114
TO: Tech Writer List, INTERNET:listserv -at- vm1 -dot- ucc -dot- okstate -dot- edu
DATE: 1/19/96 12:50 PM
RE: Copy of: Tec Pub's Reporting Structure
Hi,
My name is Bob Boeri and I'm new to this list. I started my career nearly 25
years ago as a software technical writer and have been involved with technical
publishing in one way or another since then. For the last several years I've
worked in an MIS organization dealing with publishing issues (tools,
technologies, etc.). (I can't get away from writing though; currently write a
bi-monthly column for CD-ROM Professional.) Although I was an active member of
the Society for Technical Communications for many years, I've not been a member
of STC for about 10 years. Enough introduction; here is my question.
I am interested in current organizational reporting structures for technical
publishing groups. To what organization is your technical publishing group
attached? That is, does your technical publishing manager report to the head of
Marketing Communications? Research and Development? Information Systems? Other?
How well does that reporting structure work; do you wish it were otherwise? If
so, what would you prefer? In my distant experience Technical Publishing tended
to report to R&D; had the advantage of being close to the subject matter
experts; had the disadvantage of being downsizing targets when R&D budgets
shrank.
