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.
One thing I haven't seen mentioned is, if you document your job, there is a record for those who determine your fate of what you actually DO. Many times people really don't understand all the tasks a technical writer manages (or any employee, for that matter).
Dana
****************************
Dana Worley
Product Manager, Software Products
Campbell Scientific, Inc.
****************************
Jester's Baubles Fused Glass Designs http://www.jestersbaubles.com
-----Original Message-----
Is there a good reason, from the writer perspective, to pull all the documentation for such an environment together in one place, one document? Without the carrot/stick of ISO preparation looming?
I figure if I get killed or long-term hospitalized, I'm past caring what my replacement does. If I get laid off, well, you can fill in the blanks regarding how helpful I want to be to my lower-paid replacement, or to a company that tossed me to the curb. They'll figure it out, or reinvent it.
If I get promoted/transferred, I'll have time to coach my replacement.
Let's hear other perspectives.
</kevin>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
