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.
>2. Does anyone have any suggestions as to dealing with stubborn project
>leaders who don't seem to think these are important . I have tried the
>"legal liability" argument and the "we need them to write the manual"
>argument but to little avail.
Like an old military term, the chain-of-command is only as strong as the
weakest link. If the need is not perceived from above, then it won't from
below. Using that chain of command <<and not jerking it>> let your concern
be heard.
G'Luck!
+------------------------------------------------------------------------+
| Chris Carmichael I've been reformatted with new ideas, |
| Synergy Microsystems however the file allocation table is |
| San Diego corrupt. |
| 619.452.0020 x227 |
+------------------------------------------------------------------------+
..........................................................................
