Toyota developed the Five Whys for manufacturing defects. We adapted it for organizational dysfunction.
The principle is the same: keep asking "why" until you get to the systemic root cause. But in organizations, the chain of causation runs through incentive structures, cultural norms, and structural design — not just process failures.
An Example: The Infinite Backlog
Observable behavior: The engineering team starts many projects but finishes few. Technical debt grows. Morale drops.
Why 1: There are too many competing priorities. Teams can't focus on finishing before new work arrives.
Why 2: Every stakeholder treats their request as urgent. There's no mechanism for making trade-offs.
Why 3: The leadership team avoids the conflict required to actually prioritize. Saying "no" to a peer feels political.
Why 4: The culture punishes people who push back. The last person who challenged a VP's project request got sidelined.
Why 5 (Root Cause): The incentive structure rewards activity over outcomes. Leaders are measured on projects launched, not projects completed. There's no cost to starting things and no reward for finishing them.
Why This Matters
If you stop at Why 1, you "fix" the problem with a better backlog tool or a prioritization framework. It doesn't work because the system still incentivizes the same behavior.
If you stop at Why 3, you send the leadership team to an offsite about "alignment." They come back aligned for two weeks, then revert.
Only at Why 5 do you find the lever that actually changes behavior. Change how leaders are measured — from projects launched to outcomes delivered — and the prioritization problem starts solving itself.
The Six Incentive Dimensions
When we run Five Whys in an organizational context, the root causes almost always map to one of six incentive dimensions:
- Formal: What the systems explicitly reward — comp, promotions, performance reviews
- Informal: What gets praised, who gets the interesting projects, what stories define "success"
- Structural: How the org is designed — reporting lines, budget models, decision authority
- Safety: What happens when things go wrong — are mistakes punished or treated as learning?
- Growth: Career paths, development investment, promotion clarity
- Belonging: Who's included in decisions and information, who's on the outside
Every pattern we catalog in the TRUST Pattern Library includes a Five Whys analysis that traces the behavior through these dimensions to the systemic root cause.
Applying This in Practice
Next time you see a frustrating pattern in your organization, resist the urge to fix the symptom. Instead:
- Name the observable behavior precisely
- Ask "why" — what's the proximate cause?
- Ask "why" again — what enables that cause?
- Keep going until you hit an incentive structure or systemic design choice
- Map it to the six dimensions
- Design the intervention at the root cause level
It takes longer. It's harder. And it's the only thing that actually works.