The Five Whys

A simple tool for uncovering the real reason behind a problem (or a mission).

Earlier this week I wrote about the importance of understanding your “why.” When a challenge becomes difficult, as most meaningful challenges do, a compelling sense of purpose can impact whether leaders continue forward or step away.

One simple tool that can help uncover that deeper motivation is something called The Five Whys.

The concept originated inside the Toyota Production System and was popularized by Taiichi Ohno. The idea is straightforward: when you encounter a problem, ask “why?” Then ask it again. And again. Each subsequent “why” helps reveal the underlying reason.

This framework is most commonly used in engineering and operations to diagnose root problems. But (as a recovering engineer), I’ve found that it can be just as useful for leaders trying to understand the deeper reason behind a decision, a challenge, or a mission.

A few years ago, while working at Microsoft, our team was involved in efforts to expand broadband access in rural communities. One of those communities was a small town that happens to host one of Microsoft’s largest datacenter campuses.

Using the Five Whys, the reasoning behind the project might look something like this:

Why #1
Why help bring broadband access to this community?
Because many residents in the community still lack reliable internet connectivity. (And, it isn’t a good look for the datacenter to be connected to broadband while the surrounding community was not.)

Why #2
Why does that matter?
Because reliable internet access is increasingly essential for education, healthcare, and economic opportunity.

Why #3
Why is that important for this community?
Because communities without connectivity risk falling further behind economically and socially.

Why #4
Why should Microsoft care about that?
Because Microsoft operates significant infrastructure in Boydton and is part of that community.

Why #5
Why does that responsibility matter?
Because technology should expand opportunity, not concentrate it.

The specific question you ask at each step isn’t as important as the process itself. What matters is continuing to iterate and push one layer deeper each time.

By the time you reach the fifth “why,” the work feels different. It’s no longer just an infrastructure project; it becomes part of a broader mission.

That deeper understanding often changes how teams approach difficult work. There’s a very different level of commitment when people believe the work truly matters rather than simply doing something because it’s part of the job.

The Five Whys can be applied almost anywhere:

• diagnosing a recurring operational problem

• understanding why a project stalled

• clarifying why a leader or founder started something in the first place

The point isn’t that the fifth answer is always perfect. The value comes from pushing past the first explanation, which is often incomplete.

Surface answers explain what we’re doing. But deeper answers explain why it matters.

And when the work inevitably becomes harder than expected, that difference can matter a lot.