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: Doc Department Blueprint From:George Mena <George -dot- Mena -at- ESSTECH -dot- COM> Date:Tue, 9 Jun 1998 10:35:57 -0700
Alex:
One structure (from a previous contract) might be as follows:
* Pubs manager (also acts as production coordinator)
* tech writers
* illustrators / digital photographers
* copy editors
* translation coordinator
Another structure (from a previous employer) might be as follows:
* Pubs manager (also acts as production and translation
coordinator)
* tech writer / illustrator / digital photographer / editor (also
performs blue line checks)
A third structure (from a previous contract and employer) might be as
follows:
* Pubs manager / tech writer / illustrator / editor / digital
photographer / production coordinator
Having worked in all three environments before, I find my talents are
utilized the most in the second and third structures. While the first
structure is probably the most traditional in the large corporate
environment, a lot of times it's impractical for smaller companies and
start-ups. Remember, smaller companies and startups don't always have
the funding available for a full-blown documentation department
infrastructure because the leadership components of such companies is
more concerned with growing the business and especially the gross and
net profit margins.
The second scenario is probably the most prevalent, in my opinion.
While the pubs manager has to make sure the projects get out on time,
s/he is also a working writer who's got to wear more than one hat at
work and expects the rest of the staff and contractors to do likewise.
That's not an unrealistic expectation, either. If anything, it's
essential for everyone to be a jack of all trades until such time as the
company decides it's finally big enough to actually afford to hire more
folks for the pubs function.
George Mena
> -----Original Message-----
> From: Schweizer, Alex [SMTP:alexs -at- VISTEON -dot- COM]
> Sent: Tuesday, June 09, 1998 9:40 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Doc Department Blueprint
>
> I'm looking for typical ways (real life scenarios) in which a
> documentation department might be structured personnel-wise (that is,
> writers, help developers, desktop publishers, etc). If you have any
> ideas/experience of what's good, what's bad, what works, what doesn't,
> I
> would like to hear from you. Please respond off list if this is not
> an
> appropriate topic of discussion.
>
> &^~~~
> Send commands to listserv -at- listserv -dot- okstate -dot- edu (e.g., SIGNOFF
> TECHWR-L)
> Check out topic summaries at
>http://www.raycomm.com/techwhirl/topics.htm
>
