Eliminating Defects - part one

Tuesday, January 13th, 2009

Eliminating defects - that’s something that everyone can agree is a good thing to do - whether it’s getting rid of the bad golf swing, the poor purchasing decision (these shoes don’t match anything I own!) or the manufacturing or design error, we want to eliminate defects from our lives.

Before we eliminate a defect, we have to all agree on what a defect is.   Let’s start by defining a defect, so we’re all on the same page.  A defect, according to Webster’s dictionary, is

1 a: an imperfection that impairs worth or utility : shortcoming <the grave defects in our foreign policy>
b: an imperfection (as a vacancy or an unlike atom) in a crystal lattice
2 [Latin defectus] : a lack of something necessary for completeness, adequacy, or perfection : deficiency <a hearing defect>
moreover, the Etymology gives us additional insight into the word: Middle English, from Latin defectus lack, from deficere to desert, fail, from de- + facere to do

So, defect comes from a lack, from deserting a “do”.   Sums it up pretty well, I think.  Shortcoming, deficiency - yup, that sounds like a defect.

We can have defects in anything in life - in what we eat, what we wear, what we do, even a pessimist will see defects in who they are.  In some cases, it’s easy to eliminate a defect; in others, it may be much more difficult to do so.
What’s the methodology for eliminating a defect?  The first step in most methodologies is understanding of what the defect is.  We’ll call this Definition.  Not word definition, as we did above, but defect definition.
What is defect definition?  Simply put, it’s defining the defect or problem in such a way that elimination of it will eliminate the other factors.
The definition is not as easy as it sounds, since it requires that we define the defect in such a way that it can be eliminated.  So, we have to ensure that we are identifying the true defect, not merely a symptom of that defect.
How do we separate the symptom from the defect? One of my favorite ways to do this is to steal a technique from a toddler - the 5 Whys method.  When you have a problem you want to eliminate, you want to identify the defect so it can be removed.  The 5 Whys help you to do this.

Here’s an example of the 5 Whys:

I didn’t have a good time at dinner last night.    WHY?
Every time I tried to chat, I had to yell above the noise.  WHY?
The restaurant was too crowded to relax.           WHY?
A busload of travelers got there just before us.  WHY?
The restaurant is a favorite of bus tour operators.  WHY?

As you can see, the technique can go on forever - was it that it was too noisy, too crowded, too popular?  You need to decide when you’ve gotten the true root causes.  Once there, then you can decide how to define the defect.  The noise and the crowd are just symptoms; the root cause is that you were looking for a restaurant where you could chat and relax, and selected the wrong one.

Do you agree that this is the root cause?  Why or why not?

Add to Del.cio.us RSS Feed Add to Technorati Favorites Stumble It! Digg It!
    www.sajithmr.com

Technorati Tags: , ,

Systems Thinking, Part 2 - Application

Thursday, December 11th, 2008

In Part 1 of Systems Thinking post, I talked about how systems thinking can be used to see how our actions and task fit into the bigger picture.  Instead of looking at what we are doing as a finished task by itself, it will help us to understand how we fit into the whole, in order to make the whole at least the sum of its parts, if not more than that.  Some examples:

  • If you are in management, the single most important thing you can do to drive systems thinking within your organization is to provide some context to the requests/work orders.   When I look back on my own experiences, and the leaders that I was always eager to follow, they all shared some common traits.  One of the key traits was their ability to explain what we were doing, and why we were doing it, to the entire organization.  It allowed me (and indeed, all of us) to see the systems picture.   It was very easy for us to see why we were announcing new products once we saw external customer feedback on our existing product line, and competitive analysis on what our competition was announcing.   You could almost hear the collective, “OK, we are doing well on A, B, and C; but need to beef up X, Y, and Z; and hey!  I can affect X - I can’t wait to get out of this meeting and kick around ideas on how we can do that!”  Once we all had a common vision of the finished product  in use, we were better able to work in alignment to drive towards accomplishment of that vision — as a team.
  • That’s great; but what if your management doesn’t do this?  Well, you can try to figure this out youself, using the “5 Whys” technique to understand how our work fits into the larger framework.  The 5 Whys technique asks us to keep asking “Why?” to go to the true root cause; this technique is also key to understanding our tasks.  An example of this — someone who is doing assembly may ask “Why am I doing this assembly?”  [To meet customer demand.]  “Why is there customer demand for this part?”  [Because customers like (our low price, our high quality, our color selection, etc.)]  “Why do customers like this product?” [Because we meet a need (for entertainment, for easier living, for higher productivity at work, etc.)]  “Why are we meeting this need?”  [Because it allows us to be competitive in the world marketplace, helps us to become market leaders in our niche, helps us meet a need at a fair price while providing jobs and profits to our stakeholders, etc...]   There is a famous story about a man who is working on a small component in an assembly line.  When asked what he worked on, he always said, “I build rockets that take men to the moon.”  He had the concept of systems thinking down pat.  Another litmus test - when you talk to craft workers, and ask them what they are doing, listen to their answers:  “I’m an electrician.”  “I’m a roofer.”  “I’m building the world’s most energy efficient office building.”  The last person - they’re a system thinker.

Systems thinking is understanding how your work fits in contextually.

I’d love to hear other comments on business applications for systems thinking - just drop a comment below!

Add to Del.cio.us RSS Feed Add to Technorati Favorites Stumble It! Digg It!
    www.sajithmr.com

Technorati Tags: ,




Bad Behavior has blocked 84 access attempts in the last 7 days.