Why, Why, Why, Why, Why

I was that kid, the one who kept asking “why.” I wasn’t doing it to be difficult; I genuinely wanted to understand how things worked. “Because I said so” or “because that’s the way we’ve always done it” never felt particularly satisfying, so I would persist. There was always another question beneath the answer that brought me closer to understanding. As it turns out, I was onto something.

Companies are remarkably good at solving problems. The challenge is that they are often solving the wrong ones: an operating model worked at another company, so we apply it here; teams struggle to align cross-functionally, so we roll out a new suite of tools to do it for them; a project falls behind, so we add more people to the work. The pressure to act is understandable. Timelines, targets, and market demands rarely reward investigation. As a result, visible issues receive attention because they are easy to see, while the conditions creating them remain untouched.

The deeper we look, the more often we discover that what appeared to be an isolated problem is actually a systems problem. What looked like a performance issue becomes a clarity issue. What looked like resistance to change becomes a gap in understanding.

The story changes as understanding deepens.

We often mistake the first explanation for the explanation. We see a symptom and immediately move into solution mode. Yet the ability to solve problems effectively begins with a different skill entirely: the ability to remain curious long enough to understand them.

Curiosity is a leadership discipline that requires humility. It requires suspending expertise long enough to investigate reality rather than immediately imposing an interpretation of it. The strongest leaders and operators I know are willing to sit with uncertainty longer than is comfortable, because they know that every symptom treated without addressing its cause will return.

One of the most effective problem-solving methods ever developed is the Five Whys. Originally created by Sakichi Toyoda, the founder of Toyota, and later refined by Taiichi Ohno, the method is deceptively simple. When a problem occurs, ask why. Then ask why again. Continue until you move beyond symptoms and uncover the conditions that made the problem possible in the first place. The number five is less important than the discipline itself; the power lies in resisting the temptation to stop at the first answer.

The Five Whys is a mindset. As the layers unfold, patterns begin to emerge: incentives, assumptions, structures, communication gaps, and competing priorities often reveal themselves as the true source of the issue.

In the age of AI, root cause work is even more critical. AI can accelerate analysis and build infrastructure at unprecedented speed, but it cannot determine whether we are solving the right problem. That responsibility remains ours. Technology amplifies understanding but cannot replace it. The quality of the solution will always be constrained by the quality of the question.

AI delivers most where understanding runs deepest. Understanding starts with curiosity, and curiosity begins with a simple word many of us stop asking too soon: Why?

The question was never the problem; stopping too soon was.