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.
I try to leave a basic list of where things are, where they stand, and who
to contact for various information. Other than that, I leave little else
normally.
A few years ago I was asked to document all that I did, but for a different
reason that most here think. We were being forced to accept employees who
were laid off in another area and they would be replacing a few of us, but
they had to come in through a normal internal hiring process to replace
existing people. Our boss didn't want to lose several of us and have to hire
a bunch that would take several months to come to speed on our projects, as
this would greatly impact the metrics of the project. We had been running
about $20 million under budget for the last two years and the impact would
have seriously jeopardized that.
I was to document what I did with such detail that even I couldn't get hired
for my position.
A year and a half later, even that couldn't save us.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
