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: Jobs Future for Techn From:Marilynne Smith <m -dot- smith182 -at- GENIE -dot- GEIS -dot- COM> Date:Sun, 4 Dec 1994 02:22:00 UTC
Rick talks about the loss of "history" when you use contractors. I think
that's an important issue, but it isn't just a contractor issue. Companies
are not keeping a full staff of technical writers (a cost issue). Even
"permanent" writers come and go. They may go because of layoff, a better
offer, dissatisfaction (usually overwork), or because they are following a
spouse to a new job. In each case that history is lost.
A manager from one company (permanent job) called me at my next job
(permanent job) to ask how I had planned to do the proceedings of an
upcoming conference. I had discussed my plans with this manager and the
manager previous to her. Seeing their glazed eyes, I had written down
details of the agreed upon plan and stored it carefully in a file. Meeting
my replacement, a know it all type, I had cautioned her that this
information needed to be protected. What did my replacement do? She threw
out all my files as irrelevant, even though they contained history of
So, what can you do? I told my ex-manager that I had done everything I
could to protect this history, but no one had respected that effort.
Because these plans were detailed and some parts had already been
distributed to presenters, it was more than could be discussed on the phone.
I wasn't asked to come back and help them (probably a cost issue). They had
So, what Rick says about preserving project histories is valid, but how can
you do it?
m -dot- smith182 -at- genie -dot- geis -dot- com