Scribd
Upload
83 views1 page

5 Whys Study: "A Problem Well Defined Is A Problem Half Solved"

The document outlines a 5 Whys technique for problem analysis and root cause identification. It provides a framework to define the problem symptom, then ask "why" five times to get to the root cause by investigating why the problem occurred, why it was not detected, and why the system allowed it. The goal is to have a well-defined problem and identify responsibility for corrective actions by finding the underlying causes through repeated questioning.

Uploaded by

JSH100
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
83 views1 page

5 Whys Study: "A Problem Well Defined Is A Problem Half Solved"

The document outlines a 5 Whys technique for problem analysis and root cause identification. It provides a framework to define the problem symptom, then ask "why" five times to get to the root cause by investigating why the problem occurred, why it was not detected, and why the system allowed it. The goal is to have a well-defined problem and identify responsibility for corrective actions by finding the underlying causes through repeated questioning.

Uploaded by

JSH100
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 1

Corrective Action

with Responsibility

5 Whys Study
A problem well defined is a problem half solved

Define symptom
Use this path for
the specific
nonconformance
being investigated
(Define Problem)

5-Why:
Specific problem:
Why did we have the problem?
Problem not detected:
Why did the problem reach the Customer?
System failure:
Why did our system allow it to occur?

Therefore

WHY?

Root Causes

WHY?

Therefore

Use this path to investigate


why the problem was not
detected
WHY?

Therefore

WHY?

Therefore

WHY?

Therefore

A
Problem definition

Therefore

WHY?

Use this path to investigate


the systemic root cause
(Quality System Failures)
WHY?

Therefore

C
Therefore

WHY?

WHY?

Therefore

B
Next
Reported by

WHY?

Therefore

Break Point

Date

WHY?

Revision

Reference PN

Product / Process

Therefore

WHY?

Therefore

C
Next
Problem Resolution Complete

Lessons
Learned:
Team
Members:

Communicate to .. Date:

Javier Rubio Barragn, Cadiz Spain Europe.

Process Change Break Point Date:

Implement System Change Date:

Date

You might also like