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: Mission Statements From:"Parks, Beverly" <ParksB -at- EMH1 -dot- HQISEC -dot- ARMY -dot- MIL> Date:Fri, 8 Aug 1997 14:08:01 -0700
I agree 100 percent with Bob Morrisette. You know those classes where
the instructor gets everybody to write down their personal short- and
long-term goals? I've always hated those...thought it was an incredible
waste of time. Sure, it makes you think about your goals at the time you
write them, but after the class they are soon forgotten. Mission
statements are like that. Everybody gets charged up about writing one,
then when it's written it is done and soon forgotten.
Besides, they all end up sounding the same. It's always obvious stuff.
What company or group *doesn't* want to provide complete customer
satisfaction or increase company profits?
>From: Bob Morrisette[SMTP:Robert -dot- Morrisette -at- ENG -dot- SUN -dot- COM]
>>>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 ms is one of my sore points.<<