The Power of Why

Years ago. The first question did not arrive dressed as courage. It came disguised as confusion.

I was sitting in a meeting about a new customer reporting system, staring at a process map that looked less like a service and more like somebody had attempted to reorganise a bowl of spaghetti with governance. Boxes everywhere. Arrows crossing over one another. Colours meaning things nobody could quite remember. And everybody else seemed utterly calm.

That was the unsettling part to me.

People spoke in polished sentences about streamlined journeys and improved routing logic and enhanced reporting functionality. The sort of language that arrives after enough meetings have slowly transformed uncertainty into confidence by repetition alone.

And sitting there, halfway through a quickly cooling coffee, I found myself thinking: Why does everybody seem to know what we’re doing except me?

I did what most people do. I stayed quiet for a bit. Workplaces reward momentum more than hesitation. Silence can feel strangely professional. You start assuming the confusion belongs to you alone.

But the question kept tapping away.

Why this way?

Why now?

Why does this system feel designed for the organisation instead of the person trying to use it?

Because the more we talked, the less anybody mentioned our customers. We discussed categories, ownership, handovers, escalation routes. The system itself had become the main character.

Eventually I asked, “Why are we making things complicated to actually tell us what they need?”

And the room changed.

Not dramatically. Nobody launched across the table. But I could feel the shift. A pause just slightly too long. A glance down at notes.

That’s the thing about “why”. We imagine it causes conflict. But mostly it just forces everybody to reevaluate and look for assurance we’ve got it right.

Eventually somebody explained the process mirrored the structure of the back-end system. It made internal routing easier.

Fair enough.

But it also revealed something important. We had accidentally started designing the customer around the limitations of our tools instead of designing the software around the needs of the customer.

And nobody involved was unaware. In fact, this kind of drift usually happens because capable people are moving too quickly. Momentum starts replacing meaning. Once enough meetings happen, the existence of the process itself begins to feel like proof the thing makes sense.

If there’s a project plan and a steering group and a roadmap, surely somebody already checked the foundations?

Aye. Surely.

That’s why “why” matters.

Because “why” drags work back toward purpose. It cuts through the fog organisations naturally produce when they become too busy to think. It forces uncomfortable clarity.

Weak leadership tends to experience questions as friction. Delay. Challenge. A threat to authority.

Strong leadership understands the opposite. If people stop asking why, organisations slowly drift away from reality while remaining incredibly busy.

You can feel it when that happens. Meetings multiply. Language gets thicker. Teams become exhausted in ways annual leave can’t fix because deep down they’re carrying work they no longer fully believe in.

And usually, underneath all of it, sits one unanswered question.

Why are we actually doing this?

I think every piece of work should carry that question from the very beginning. Before procurement. Before governance. Before people become emotionally committed to the shape of something that might not make sense yet.

And leaders need to become genuinely comfortable hearing it.

Because sometimes the answer is strong.

And sometimes the answer is, “Aye… actually… that’s a fair point.”

Which might be the most useful sentence any organisation can learn to say.