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:Mon, 11 Aug 1997 09:43:34 -0700
>John Posada[SMTP:JOHN -dot- POSADA -at- EY -dot- COM] wrote:
>>>I agree on one hand that most mission statements sound alike and tend to
>>>state
>the obvious. However, speaking from one who just handled the process that
>spanned almost two months, I can identify some benefits that would have come
out of it even if the statement had never seen the light of day.<<
Well, I didn't spend two months devising a mission statement, but I did
spend two months performing a software process assessment, and then
another two months developing the action plan based on the findings of
the assessment. I agree with you that the process *for the people
involved* was exciting and beneficial. It's what happens when it is all
said and done that's the killer. Management signs off on the action plan
-- a gesture that presumably shows their support -- then two months
later reorganizes the organization so that all our hard work becomes
invalid. Yeah, we were pumped while it was happening, but if there's no
>follow-through from management then that bubble is easily popped.
>
>>>A mission statement is not for the primary benefit of a customer. The
>>>mission
statement is for the benefit of the organization.<<
>No argument there. I think this is a basic understanding.
>
>>>
>----------------
>
>The Tactical Applications Group of Ernst & Young LLP will be responsible for
>the analysis, design, development, deployment, implementation, and support of
>a
>wide spectrum of information management applications for our customers at
>Ernst & Young.
>
>The needs and desires of our customers will drive us to develop best-of-class
>applications. We will respect each of our customers as equal partners. As
>partners, we will strive to produce the most cost-effective,
>technology-appropriate application using current development tools,
>processes,
>and disciplines.
>
>---------------
<<
Yup, that's a mission statement all right.
>
>Bev Parks
>parksb -at- emh1 -dot- hqisec -dot- army -dot- mil
>The Friendly Faces of TECHWR-L -
>http://www.bayside.net/users/cbsites/techwr-l/
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html