What is “5 Whys”?
5 Whys is a root-cause analysis technique developed at the Toyota Production System by Taiichi Ohno. By asking “why” iteratively — typically five times — for any observed problem, the investigator moves past surface symptoms to underlying systemic cause. Eric Ries adapted the technique for Lean Startup, where it has become a standard tool for diagnosing operational and product issues without jumping to premature fixes.
The technique demonstrated
Toyota classic example: Problem: a machine stopped working. Why? A fuse blew. Why? The lubrication system was overloaded. Why? The pump wasn’t pumping enough lubricant. Why? The pump shaft was worn out. Why? The maintenance schedule didn’t include shaft inspection. The “real” problem isn’t the broken fuse — it’s a maintenance-process gap. Fixing only the fuse ignores the systemic cause.
Why most people stop too early
The natural impulse is to stop at the first plausible cause and apply a fix. “Fuse blew — replace fuse” feels like a complete answer. But the second-order cause (lubrication overload) and third-order cause (worn pump shaft) and fourth-order cause (maintenance schedule gap) are where the real intervention lies. Sustaining each “why” question requires conscious discipline against the impulse to solve.
5 Whys in startup operations
Three common applications. (1) Production incidents — when a deployment causes downtime, 5 Whys identifies whether the cause is the deployment, the testing process, the engineering culture, or the engineering hiring decisions. (2) Customer churn spikes — why did churn rise in this cohort? Why did engagement drop? Why did the user lose interest? Each layer surfaces different intervention points. (3) Sales close-rate decline — why are deals slipping? Why are budgets dropping? Why is the buying committee resistant? Same problem, very different root causes.
5 Whys vs. fishbone analysis
Both are root-cause techniques. 5 Whys follows a linear causal chain — fast but can miss parallel causes. Fishbone (Ishikawa diagram) maps multiple causal categories (people, process, technology, environment) — comprehensive but slower. Startups generally favour 5 Whys for speed; mature operations use fishbone for systemic process improvement. Combining both is standard for serious incident reviews.
Türkiye context
Türk startup teams often skip 5 Whys because the “obvious” explanation feels efficient. The result: repeated incidents from the same root cause, mistaken in each occurrence for a new problem. Discipline around 5 Whys — particularly in customer-success and engineering post-mortems — meaningfully improves operational maturity. Combining 5 Whys with KVKK-incident-response procedures produces both compliance and learning.
Related: Build-Measure-Learn, Customer Development, Strong Opinions, Weakly Held.