1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice
You must be a registered member in order to post messages and view/download attached files in this forum.
Click here to register.

Fundamental Questions to ask when an Issue arises...

Discussion in '5S, 5Why, 8D, TRIZ, SIPOC, RCA, Shainin Methods...' started by Tom Waite, Aug 3, 2015.

  1. Tom Waite

    Tom Waite Member

    Joined:
    Aug 3, 2015
    Messages:
    45
    Likes Received:
    33
    Trophy Points:
    17
    Location:
    Grand Rapids Michigan Area
    One of the first questions I ask when digging into an issue is:

    If we followed the system as written would we still have the issue?

    If yes, it is a systematic issue, if no, it's a human factor issue. Sometimes it's a little bit of both.

    What is one of the fundamental questions you ask when an issue arises?
     
    Tom Waite, Aug 3, 2015
    #1
    Claes Gefvenberg likes this.
  2. Claes Gefvenberg

    Claes Gefvenberg Moderator Staff Member

    Joined:
    Jul 31, 2015
    Messages:
    230
    Likes Received:
    208
    Trophy Points:
    42
    Location:
    Eskilstuna, Sweden
    Good question. I would say that the fundamental question is: What could we do better?
     
    Claes Gefvenberg, Aug 4, 2015
    #2
    Tom Waite likes this.
  3. PaulJSmith

    PaulJSmith Well-Known Member

    Joined:
    Jul 30, 2015
    Messages:
    107
    Likes Received:
    113
    Trophy Points:
    42
    Location:
    Midwestern USA (STL area)
    I think the two most important questions are;
    1) Where/why did the failure occur?
    2) What can we do to improve it?
     
    PaulJSmith, Aug 4, 2015
    #3
    Tom Waite likes this.
  4. Ganesh Sundaresan

    Ganesh Sundaresan Active Member

    Joined:
    Jul 31, 2015
    Messages:
    66
    Likes Received:
    36
    Trophy Points:
    17
    On a lighter side, Who can be given the ball. Jokes apart, my fundamental question, is there a standard or specification or rule or guidelines or a mechanism or a commonly agreed way of doing things?
     
    Ganesh Sundaresan, Aug 4, 2015
    #4
    Tom Waite likes this.
  5. Bev D

    Bev D Moderator Staff Member

    Joined:
    Jul 30, 2015
    Messages:
    671
    Likes Received:
    729
    Trophy Points:
    92
    Location:
    Maine
    Well since humans developed the system there is always some contribution of the human to the problem (or issue); that's not to say that they are to blame as it is about root cause not root blame.

    the first questions that I ask are about defining the Problem:
    "What is the Problem" in terms of object/event and defect/failure. This is terms of effect and not cause
    "What is the Y": This is the characteristic that can be measured or observed/assessed that results in the problem when in a 'bad' state.
    "How is measured or assessed": This is a first hint at the effectiveness of the measurement system
    "Why Does it matter". What is the negative effect to customer, delivery or cost of this Problem.
    "What is the occurrence rate and trend"
     
    Bev D, Aug 4, 2015
    #5
    Mark Paul, Marc Smith, Tom Waite and 3 others like this.
  6. RoxaneB

    RoxaneB Moderator Staff Member

    Joined:
    Jul 31, 2015
    Messages:
    926
    Likes Received:
    1,081
    Trophy Points:
    92
    Location:
    Ontario, Canada
    This is, in my opinion, the most important question to ask and should be asked first. After all, if it does not matter, is it truly a problem? If it's not an issue, is it truly worth spending time, money, resources on...at least at this point in time?
     
    RoxaneB, Aug 5, 2015
    #6
    Tom Waite, Jennifer Kirley, Claes Gefvenberg and 1 other person like this.
  7. reynald

    reynald Member

    Joined:
    Jul 31, 2015
    Messages:
    19
    Likes Received:
    24
    Trophy Points:
    2
    Location:
    Manila, Philippines
    I think somewhat similar to this, though the exact questions in my head are (1) is the issue real or just perceived, (2) to whom is it an issue, and (3) why is it an issue.
    The first question is to check alignment in operational definitions. Some people could be raising hell on what they thought they understood but when definitions are checked it turns out they just misunderstood something and thought there is an issue. The next is the stakeholder (and do they matter?). It is a reality that there will be some trade-offs in the business. If someone buys for instance two UPS (un-interruptible power supply) to reduce risk, a lean manager (the st*pid me, let's say) may say there is a waste. If I ask the IT manager, he/she would say it is not. This may not be a good example but the point is an issue may depend on a who is looking.
     
    reynald, Aug 5, 2015
    #7
    Tom Waite likes this.
  8. Pancho

    Pancho Active Member

    Joined:
    Jul 30, 2015
    Messages:
    76
    Likes Received:
    84
    Trophy Points:
    17
    Location:
    Cypress, Texas, USA
    I'm with Bev. "Digging into an issue" should mean gathering facts, so the first question we try to ask is "What happened?".

    Facts can be difficult to collect, but it's important to have them before starting to analyze.
     
    Pancho, Aug 6, 2015
    #8
    Tom Waite, Chris Glover and Bev D like this.
  9. Chris Glover

    Chris Glover Active Member

    Joined:
    Aug 7, 2015
    Messages:
    54
    Likes Received:
    32
    Trophy Points:
    17
    We put this together a few years back when we had several new QA associates who needed step-by-step guidance
     

    Attached File(s): 1. Scan for viruses before using. 2. Report any 'bad' files by reporting this post. 3. Use at your own Risk.:

    Chris Glover, Aug 7, 2015
    #9
    reynald, Tom Waite and Rachel like this.
  10. David Bradley

    David Bradley Active Member

    Joined:
    Aug 2, 2015
    Messages:
    57
    Likes Received:
    55
    Trophy Points:
    17
    Location:
    Michigan
    One of the first questions I ask is: "What changed?" If we were making good parts for months (or the process was working properly ), or years and suddenly we aren't. Something changed. Variation is always the cause of issues. Either we introduced a new source of variation, or increased the amount of existing variation.
     
    David Bradley, Aug 7, 2015
    #10
    Tom Waite, PaulJSmith, Chris Glover and 3 others like this.
  11. Bev D

    Bev D Moderator Staff Member

    Joined:
    Jul 30, 2015
    Messages:
    671
    Likes Received:
    729
    Trophy Points:
    92
    Location:
    Maine
    The New Science of Fixing Things (www.tnsft.com) has a paper entitled "3 good questions and 1 not so good question" that apply to questions regarding the diagnostic search for cause, particularly when approaching a new Problem that you know little about. (They also have a saying "equipment have Problems and People have issues" that alwasy make me laugh...we tend to use the term issue as a softer phrase than Problem) These are different questions than those used to describe the Problem which helps with prioritization and resourcing as well as providing a solid foundation to begin the diagnostic process. It's all a bit of an art and a bit of a discipline....

    you might find these useful:

    Question 1: What's wrong? this is the equivalent of "is it plugged in and turned on" type of question when you are looking for the obvious actionable immediate cause. "is it in specification" is another of these questions.
    Question 2: What Changed? fairly obvious what it's getting after but it's the weakest of the 4 questions from a diagnostic standpoint. It is very susceptable to 'post hoc ergo propter hoc' errors of coincidence. (the paper's John Allenalways answers this one with "everything" and of course he's right) Why is it so weak? because lots of things change continually so it's easy to see a surface change and think it caused the Problem. We can and should answer this question, but my expereince is that we only do this once we understand the causal mechanism through other means first. I will say that I do send my teams out to try to answer this question in the beginning anyway as due diligence demands we check the easy stuff first...
    Question 3: What's Different? This is a great question and gets us to the answer to "what changed" quicker. Whats different between the good parts or events or lots and the bad parts or events, or lots...
    Question 4: What's Happening? This may be more difficult or as easy as observing the actual failure happen.
     
    Bev D, Aug 10, 2015
    #11
    Jennifer Kirley, Marc Smith, Jim Gardner and 5 others like this.
  12. Tom Waite

    Tom Waite Member

    Joined:
    Aug 3, 2015
    Messages:
    45
    Likes Received:
    33
    Trophy Points:
    17
    Location:
    Grand Rapids Michigan Area
    Good feedback everyone. This is an example of the many ways we all look at things but ultimately getting to the same place with different paths. I think fundamentally we are all saying the same thing just with our own twists.

    Good stuff!
     
    Tom Waite, Aug 12, 2015
    #12
    Bazinga likes this.
  13. tony s

    tony s Well-Known Member

    Joined:
    Sep 10, 2015
    Messages:
    1,367
    Likes Received:
    1,069
    Trophy Points:
    112
    Location:
    Laguna Philippines
    Since I always believe that a problem will only happen if an event, condition, situation, or outcome doesn't happen as expected or desired, I will usually start with this question: Why is it a problem?
     
    tony s, Jun 6, 2016
    #13
    Bev D likes this.
  14. ncwalker

    ncwalker Well-Known Member

    Joined:
    Sep 21, 2015
    Messages:
    261
    Likes Received:
    170
    Trophy Points:
    42
    Location:
    North Carolina
    Today I find my first question often is: Is this information real?

    Too many times I chase off after an issue only to find during investigation, it wasn't really an issue. Or the severity of it, at least, is apt to get quite overstated.
     
    ncwalker, Jun 6, 2016
    #14
    Marc Smith and Bev D like this.
  15. MarkMeer

    MarkMeer Well-Known Member

    Joined:
    Dec 3, 2015
    Messages:
    138
    Likes Received:
    62
    Trophy Points:
    27
    I'm a bit wary of the distinction between "systemic" and "human factor".

    How does this help? How does such a distinction affect the action(s) you take?

    To me, the better distinction is between:
    - "Systemic" - issues that have a reasonable probability of recurrence, or potential to impact other elements (product quality, customer satisfaction, record integrity, ...); versus
    - Issues that may be isolated incidents, with low probability of recurrence, and minimal potential impact.
     
    MarkMeer, Jun 6, 2016
    #15
    Candi1024 likes this.
  16. Marc Smith

    Marc Smith Active Member

    Joined:
    Aug 1, 2015
    Messages:
    60
    Likes Received:
    86
    Trophy Points:
    17
    Reality: If we followed the system as written would we still have the issue?
    A) If not, Five Whys starting with why the person or persons didn't follow the protocol/procedure.
    B) If you did - Five Whys.

    * Five Whys = Ask relevant questions (see post 11).
     
    Marc Smith, Jun 7, 2016
    #16