Setting up Documentation Dept.

[Jim Mastinger <JMMasting -at- AOL -dot- COM>]

Hello -

I am in the process of making a case to my software company to create a
full-time department for Documentation/Tech Writing.

They are agreeable to this, since we currently pay a number of consultants to
do the work, and see the benefits of bringing these people in full-time.  I
just need to define the structure of the department.

In defining the roles and responsibilities, I have individuals with a variety
of skills (writing, project management, online help, etc.) who have spent
varying degrees of time in the industry and with the company.  While "time"
is not necessarily a mitigating factor in determining
competence/promotion/etc., it is still a factor.

I am looking for information to help with my presentation.  Specifically:

1. What kind of titles/roles best work in creating a unit?
Should there be Documentation Specialists, Tech Writers, Documentation
Project Managers, Online Information Analysts?  I don't want to create
specialization, but recognition of certain abilities is important.  What
works?

2. What about seniority or strengths?
What about moves upward?  Doc Person - Senior Doc Person - Doc Projects
Coordinator?  Where can I read guidelines on employee motivational goals and
the steps necessary to reach them?  Is it years+experience+success?  Everyone
needs recognition and something to strive for.

If anyone out there has practical experience or can suggest some literature
concerning setting up such a department, I would be extremely grateful.

JMM

 TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot-  Send commands
   to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
  Search the archives at http://www.documentation.com/  or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html