The 5 Whys: From Root Cause to Real Learning

Mar 16
3 min read

We've created a simple two-page worksheet to help you run the 5 Whys with your team. You can download it at the end of this article.

That deadline your team missed last month? There was a reason. The stakeholder complaint that landed on your desk? Something triggered it. The policy rollout that went sideways? It didn't happen in a vacuum.

Yet in the rush of public sector work, we rarely stop to ask why. We remediate. We patch. We move on to the next fire. The issue gets "resolved" in the system, but the underlying cause stays right where it was, waiting to create the next problem.

This is how individuals, teams and divisions get stuck in cycles. The same issues resurface, dressed up in different clothes. People get frustrated. Leaders get fatigued. And slowly, the culture shifts from proactive to reactive. Always responding, never getting ahead.

The missing ingredient? Getting to the root cause.

When something goes wrong, whether in policy, programs or service delivery, we need to pause, even briefly, and ask: What actually caused this? Not the surface-level answer. The real one. The one that, if addressed, means this problem doesn't come back.

And finding root causes isn't just about fixing things. It's about learning. Every issue is an opportunity to understand your environment better. How work flows. Where it gets stuck. What's fragile in your systems and processes. When you dig into root causes properly, you're not just solving today's problem. You're building insight that makes you sharper for tomorrow's.

The 5 Whys is one of the simplest and most effective tools for this. It forces you to move past the obvious, peel back the layers, and land on something you can actually act on.

How it works

State the problem. Ask "Why?" Answer it. Then ask "Why?" again. Repeat until you've asked five times, or until you've hit something that feels like the genuine root cause.

No software. No complex framework. Just disciplined questioning.

The Five Whys in action

Your team is consistently missing project deadlines. Here's how the 5 Whys might play out:

Problem: We're consistently missing project deadlines.

Why? Our team is submitting work late.
Why? We're waiting on information from other teams.
Why? There's no clear process for cross-team requests.
Why? We've never established formal communication channels.
Why? We've relied on informal networks, which aren't scaling with our growth.

By the fifth question, you've uncovered something that wasn't obvious at the start. The issue isn't effort or time management. It's a structural gap in how teams communicate. Fix that, and the deadline problem goes away. Ignore it, and you'll be having the same conversation again in six months.

That's the learning. And it only comes when you push past the surface.

Run it as a team

The 5 Whys works fine as an individual exercise, but it's more powerful with a group. Different perspectives surface insights that no single person would reach alone. It also builds shared understanding, so when you land on a root cause, the whole team owns it.

Keep it blame-free. The goal isn't to find someone to hold responsible. It's to understand why something happened so you can prevent it from happening again.

Watch the pitfalls

Stopping too soon. It's tempting to land on a plausible answer and call it done. Push deeper. The real insight often comes at the fourth or fifth question.

Being too vague. "Poor communication" or "lack of resources" are too broad to act on. Be specific. What communication? Which resources? The more precise your answers, the more useful your root cause.

Treating five as a rule. It's a guideline. Sometimes you get there in three. Sometimes it takes seven. Keep going until you've genuinely uncovered something new.

From diagnosis to action

Finding the root cause is only half the job. The other half is doing something about it. Once you've landed on a cause, ask: What's one thing we can change to address this? Make it specific. Assign it. Follow up.

And document what you learned. Not in a lengthy report that nobody reads, but somewhere your team can reference. Over time, these insights compound. You start recognising patterns earlier. You stop repeating the same mistakes. You shift from firefighting to leading.

That's the real payoff of the 5 Whys. Not just solving problems, but building the diagnostic muscle that makes you and your team better at navigating whatever comes next.

If this sounds familiar, you're not alone.

Want to go deeper?

In our Managing Uncertainty course, the 5 Whys is one of several diagnostic tools we cover for navigating complexity in government. Through interactive case studies and practical exercises, you'll build the skills to find root causes, turn problems into learning, and lead with confidence.

Don't start from scratch. We have a one-page worksheet you can print and take into your next team meeting.