RE: Developing a Methodology

Subject: RE: Developing a Methodology
From: "Nuckols, Kenneth M" <Kenneth -dot- Nuckols -at- mybrighthouse -dot- com>
To: "Johnson, Tom" <TJohnson -at- starcutter -dot- com>, "John Posada" <jposada01 -at- yahoo -dot- com>, "Zuercher, Darrell" <dzuerche -at- tva -dot- gov>, <eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com>
Date: Fri, 26 May 2006 08:38:13 -0400

Tom Johnson wondered...

>
> Are you saying if you write a document has lots of defects but they
aren't
> discovered you've achieved Six Sigma? Somehow that doesn't seem right.
>
> ------------------
>
> John Posada wrote:
>
>
> 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 (even if it means that 3.4 readers discovered the SAME
> defect). In other words, if 500,000 people read it, there will be a
> cumulative number of 1.7 defects noticed (3.4/2), and if 250,000 read
> it, .85 defects will be noticed.
>

That's technically what he said, but I don't think that's the intent.
I've not done any Six Sigma training, but I would imagine they envision
a pool of "perfect" readers: thorough, knowledgeable, detail oriented,
and dependent on the accuracy of the documentation.

I'm not sure what constitutes a "documentation defect" in Six Sigma
parlance, and I'm wondering if someone can elaborate:

Would a defect be the fact that a person misused a comma that violated
some obscure and arcane (but still valid) rule, and only 1 reader out of
250,000 was savvy enough to think "Gee, that might be wrong, but I'm not
completely sure about it"?

Or would a defect be leaving out a step in a process that is so rarely
used that only 1 in 250,000 readers would actually go through it and
would figure out there was an error, but would still be able to find a
work-around based on the other information you provided in the document?

Or would both the above be considered a defect?

CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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!. http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList

---
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 http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com


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
http://www.techwr-l.com/techwhirl/ for more resources and info.


Follow-Ups:

Previous by Author: RE: ANN: Microsoft update (WinHelp)
Next by Author: Re: visio
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