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:Doc Department Blueprint From:"Schweizer, Alex" <alexs -at- VISTEON -dot- COM> Date:Tue, 9 Jun 1998 12:40:12 -0400
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.
