Mind map template · Analysis

5 Whys template, as a mind map

Find the root cause of a problem with your team on one map: separate facts from guesses, ask why five times, and leave with a fix someone owns.

Shiko is in closed beta: this takes you to the wishlist first.

The template as it opens. Every prompt is a node you answer under or replace.

What's inside

What went wrong?

  • Facts to check first
    • What do we know for sure?
    • What is only a guess?
  • Why 1: why did this happen?
    • Why 2: why did that happen?
      • Why 3: why did that happen?
        • Why 4: why did that happen?
          • Why 5: why did that happen?
            • Root cause
              • Countermeasure
                • Make it stick (a task list)
  • When to stop

How to run it with your team

  1. Write the problem in the middleReplace "What went wrong?" with one specific problem: "The release went out with a broken login", not "Quality is bad".
  2. Check the facts firstUnder Facts to check first, split what you know for sure from what is only a guess, so the chain starts on solid ground.
  3. Ask why, five timesEach Why sits under the one before it, with a "Because…" to fill in. Keep going until the answer is something you can change, not someone to blame.
  4. Fix the root causeBelow Why 5 come the root cause, a countermeasure and a task list: assign an owner, agree a deadline and check a month later that the problem is gone.

What is the 5 Whys technique?

The 5 Whys technique finds the cause of a problem by asking "why?" again and again, each time about the answer before. It comes from Toyota: Sakichi Toyoda used it, and Taiichi Ohno made it part of the Toyota Production System, where a problem on the line was traced back to its cause instead of just patched.

It works because the first answer is usually a symptom. A machine stopped because a fuse blew; the fuse blew because a bearing was dry; and so on, until you reach something a team can change, such as a missing check or an unclear rule. Five is a guide, not a target. The method needs facts at each step, not guesses, and it points at processes, not people.

Written as a list, the five whys hide the moments where an answer splits in two. On a mind map each why sits under the one before, a second answer becomes a second branch, and the root cause and its fix sit at the end of the chain, where the whole team can see how you got there.

When to use it

After an incident, a missed deadline, a customer complaint or a defect that keeps coming back. As a root cause analysis template, the 5 Whys is the simplest there is: no scoring, no diagrams, just one question asked until the real cause shows up.

Five is a rule of thumb, not a law. The When to stop branch is there for that: stop when the answer points to a process you control, and add a second chain when a why has two answers.

Questions

Can my whole team edit it at once?

Yes. Everyone you invite works on the same map live, and you see who is typing where.

What does a 5 Whys example look like?

The release went out with a broken login. Why? A config value was wrong. Why? It was changed by hand on the day. Why? The release checklist has no config step. Why? The checklist was written before config moved to the dashboard. Why? Nobody owns the checklist. Root cause: no owner. Countermeasure: name one and add the config step.

Is a 5 why template the same as a five whys template?

Yes, people spell it both ways. It is one method: a chain of why questions that ends in a root cause and a fix.

What if a why has more than one answer?

Add a second branch under that why and follow both. A map handles a fork far better than a numbered list does.

Can I export the analysis?

Yes. Every map exports to PNG and SVG; Pro adds PDF and JSON.