Quality Engineering

5 Why Analysis in Manufacturing

5 Why is the simplest root cause tool in manufacturing, and also one of the most misused. Done well, it moves the discussion from symptoms to a cause the team can actually control.

By Career Plus Academy — manufacturing career development for Production and Quality professionals in India.

What it means

5 Why analysis means repeatedly asking "why did this happen?" and answering with facts until you reach a cause that, when removed, prevents the problem. "Five" is a guide, not a rule — sometimes three whys are enough, sometimes seven are needed.

Why it matters in manufacturing

It is fast, needs no software and can be used at the machine within minutes. It is ideal for simple and moderate problems and as part of 8D investigations.

How to run a 5 Why

  1. 1

    Write a clear problem statement

    State the observed problem with facts, e.g. "Line 2 stopped 40 minutes due to hydraulic pump failure".

  2. 2

    Go to the place

    Look at the part, machine and records before answering.

  3. 3

    Ask why and verify each answer

    Each answer should be checked, not guessed.

  4. 4

    Stop at a controllable cause

    Stop when you reach a cause in a process or system you can change.

  5. 5

    Run two chains

    One for why it happened and one for why it was not detected.

  6. 6

    Define actions

    Assign actions against the root cause and check the result.

Practical shop-floor example

Illustrative learning example — not a client result

Example: machine stoppage

Why did the machine stop? Pump overheated. Why? Oil level was low. Why? Leak at a fitting. Why? Fitting was loose. Why? Fitting is not in the preventive maintenance checklist. Action: add fitting check to the PM checklist and inspect similar machines.

Common mistakes

  • Answering with opinions instead of verified facts.
  • Stopping at a person ("operator forgot").
  • Following only one chain when several causes exist.
  • Writing actions that do not address the final why.

Practical checklist

  • Problem statement is factual and specific
  • Each answer verified at the gemba
  • Occurrence and detection chains both completed
  • Root cause is in a process or system
  • Action directly addresses the root cause

Frequently asked questions

Do I always need exactly five whys?

No. Continue until you reach a cause you can control and verify. The number varies.

When is 5 Why not enough?

For complex problems with several interacting causes, combine it with a fishbone diagram, data analysis or other root cause tools.

Want to check how well you know this topic?

Take the Skill Assessment

Preparing for interviews too?

Check Interview Guide & Kit Availability