Re: Developing a Methodology

Subject: Re: Developing a Methodology
From: eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 25 May 2006 15:45:46 -0400

In all seriousness,

John Posada <jposada01 -at- yahoo -dot- com> wrote on 05/25/2006 01:42:24 PM:
> BTW...the goal of Six Sigma, from the perspective of documentation,
> means that if a million people read a document, only 3.4 defects will
> be discovered ...

True. If your only applying to Six Sigma to the documentation output.
However, in that limited scope, what constitutes a "defect" is dependant
on the definition of a defect and how those "defects" are being measured.

Really, Six Sigma can be applied to any part of the documentation
lifecycle, from information gathering/creation to document archiving, with
any measurable metric used to try and detect a bottleneck or other process

Otherwise, documentation is central to all effective Six Sigma/ISO/Total
Quality or other priesthood-run-acronym-driven-process(tm) following
organisation. Even those that simply use good sense to get the job done.

Document what you do, do what you document. Consider change only once a
problem has been quantified. Evaluate and document possible replacement
procedures. Once you can prove the benefit outweighs identified (and
preferably mitigated) risks. Follow the new documented process.

The backbone of all the big name process "methodologies" and the simple
secret to success and repeatable outcome. No need to partake of the
kool-aid if you can see the logic of good procedure planning, execution,
and well designed fail-safes and/or idiot proofing. Include a little
logical failure planning and exception handling and you're done.

Otherwise, Poke Yoke yer heart out. :)

Eric L. Dunn
Senior Technical Writer


This e-mail communication (and any attachment/s) may contain confidential
or privileged information and is intended only for the individual(s) or
entity named above and to others who have been specifically authorized to
receive it. If you are not the intended recipient, please do not read,
copy, use or disclose the contents of this communication to others. Please
notify the sender that you have received this e-mail in error by reply
e-mail, and delete the e-mail subsequently. Please note that in order to
protect the security of our information systems an AntiSPAM solution is in
use and will browse through incoming emails.
Thank you.

Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut
contenir des renseignements confidentiels ou protégés et est destiné à
l?usage exclusif du destinataire ci-dessus. Toute autre personne est par
les présentes avisée qu?il est strictement interdit de le diffuser, le
distribuer ou le reproduire. Si vous l?avez reçu par inadvertance,
veuillez nous en aviser et détruire ce message. Veuillez prendre note
qu'une solution antipollupostage (AntiSPAM) est utilisée afin d'assurer la
sécurité de nos systems d'information et qu'elle furètera les courriels


WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!.

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Re: Developing a Methodology: From: John Posada

Previous by Author: Re: Developing a Methodology
Next by Author: RE: Developing a Methodology
Previous by Thread: Re: Developing a Methodology
Next by Thread: Re: Developing a Methodology

What this post helpful? Share it with friends and colleagues:

Sponsored Ads