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: Starting from scratch From:"Humbird, Len - CFC" <Humbird -dot- Len -at- cfwy -dot- com> To:"'TECHWR-L (E-mail)" <TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM> Date:Fri, 7 Jan 2000 11:06:50 -0800
I've been there. I haven't done these steps, but it makes sense if you're
given the leeway.
1. Define your charter. What is your purpose there? What needs do you serve?
Who do you serve? What will you produce? Where are you on the org chart?
2. Meet with each of the managers in IT. Assess their situations with
respect to how you could facilitate.
3. Prioritize. Determine if you need more heads to get the work done.
Propose your findings to whomever you're reporting to. And the next person
up the ladder.
4. If you're being pulled by multiple departments, define some policies and
5. Put together a style guide for each type of document you're producing.
6. If it's a big IT department, put together a "press release" that promotes
to you/your department to the IT department.
7. Announce to the IT department (through email, intranet, etc.) of your
existence, your charter, and policies/procedures on how to utilize your
8. After you've produced a few good manuals, put together a bibliography of
publications that you've produced. Make it available online to everyone.
Include how to get to the documents online.
From: mikala morgan [mailto:dolphina -at- visto -dot- com]
Sent: Thursday, January 06, 2000 4:18 PM
Subject: Starting from scratch
I have accepted a job with a company that is rebuilding its IT division.
They have never had a tech writer and don't have a stick of
I have plenty of ideas, but would like to know what some of you would do to
your documentation departments if you could start with a clean slate and a
(within reason) blank check.