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.
From: Paul Hanson <PHanson -at- Quintrex -dot- com>
>I'd be interested in reading any documentation department mission
>statements that you use or have heard. Looking for opinions.
I could not resist including my post on this subject from
August, 1997. Sorry I cannot be more constructive, Paul.
__My advice about a mission statement is to forget it. I've spent
many hours in meeting rooms at several companies creating mission
statements. Management only asks for these because it is one
of the buzz phrases. After many drafts and approvals up and down
the chain, the mission statement will be filed away and everyone
will forget about it until a new manager comes in and says,
"I think we should start working on a mission statement."
Sorry to be so negative, but the mission statement is one of my
sore points.__
