HomeFrameworksProblem Solving › 5 Whys
// framework

5 Whys

Sakichi Toyoda / Toyota Production System, early 20th century

A root cause analysis technique that asks "why?" five times in succession — the first answer is almost never the real answer, and the fifth why is usually the uncomfortable one that actually tells you what to fix.

// description

A root cause analysis technique that involves asking "why?" five times in succession to drill past surface symptoms into the true underlying cause of a problem.

// history

Developed by Sakichi Toyoda, founder of Toyota Industries, the 5 Whys became a cornerstone of the Toyota Production System in the 1950s. Taiichi Ohno, architect of the TPS, popularised it as the basis for kaizen (continuous improvement). The insight was deceptively simple: problems don't fix themselves when you treat the surface-level symptom. You need to ask why until you reach the systemic or behavioural root.

// example

Your coloring book sales dropped this month. Why? → Fewer people are clicking your listings. Why? → Your thumbnail images aren't standing out in search. Why? → You haven't updated your cover designs since last year. Why? → You've been too busy creating new books to refresh old ones. Why? → You have no system for auditing and refreshing your back catalogue. Root cause: no maintenance workflow. Fix: schedule quarterly catalogue audits.

// katharyne's take

I use 5 Whys constantly — especially when a launch underperforms. The first answer is almost never the real answer. "Sales were low" isn't useful. "I launched to an audience who didn't know I existed yet" is. Keep asking why until you hit something you can actually change. The fifth why is usually uncomfortable, which is exactly how you know you're close to the truth.

// creative uses
// quick actions
// prompt ideas
Run the 5 Whys process with me on this problem: [describe your business problem — e.g., my Etsy conversion rate dropped 30% this month]. Ask me "why?" after each answer I give. Don't accept the first answer. Keep pushing until we reach a root cause that's specific and actionable.
I have a KDP or Etsy product that has [zero sales / declining sales / bad reviews]. Help me run a 5 Whys analysis on it. I'll describe the product and its stats: [paste details]. Guide me through each why and help me identify whether the root cause is in the product itself, the listing, the cover, the niche, or my keyword strategy.
My last course launch underperformed — I expected [X] enrolments and got [Y]. Walk me through the 5 Whys framework applied to a launch debrief. Start by asking me what happened at each stage of the funnel, then help me trace the root cause so I can fix the actual problem before the next launch.
See also: Fishbone Diagram · PDCA Cycle · A3 Problem Solving
← Problem Solving Fishbone Diagram →