The Power of Why

The employee who asks questions is the one your business cannot afford to silence

By Carmen Neagu, 31 March 2026

There is always one person in the team who asks why. Why is this process still done this way? When did we last review this? What problem is this actually solving? They are not being difficult. They are doing something most organisations say they want but quietly discourage — and the businesses that learn to harness it rather than manage it out tend to be sharper, more resilient, and far less likely to find themselves wedded to a process that stopped serving them two years ago.

The cost of silencing this instinct is real. The CIPD Good Work Index 2025 found that only 37% of UK employees feel they can actually influence decisions at work — not just be consulted, but genuinely heard. Google’s Project Aristotle, which studied over 250 teams, found that psychological safety — the sense that it is safe to ask questions and challenge assumptions — was the single most important factor in team effectiveness. More important than talent, experience, or resources. The environment you create around that question matters more than the person asking it.

Most businesses do not silence the question deliberately. It happens through accumulated patterns: a concern raised in a meeting that is noted and never returned to, a suggestion met with “we’ve always done it this way”, a manager who consistently has the answer before the discussion has finished. None of these are acts of cruelty. They are acts of busyness. But the cumulative effect is the same — people learn that asking why is unlikely to lead anywhere useful, so they stop. And with that, the business quietly loses its ability to catch its own errors.

A practical framework: the four conditions for the question to land

Rather than a list of tips, here is a framework you can actually apply — whether you run a team of five or five hundred. The question only lands when four conditions exist simultaneously. Remove any one of them and the culture quietly reverts.

1. Safety to speak — without consequence

This is the foundation. People will not ask why if the last person who did was dismissed, ignored, or subtly penalised. Safety does not require a formal policy — it is built in the moment-by-moment response to questions. The fastest way to build it: when someone raises a concern or asks about a process, thank them for raising it before you respond to the content. It takes three seconds and it changes what the room believes is acceptable.

2. Structure to surface it

Waiting for the question to emerge organically in a busy business is optimistic. Build a moment into your rhythm where it is explicitly invited. A short quarterly process review — not a formal away day, just a focused conversation — where the only question on the agenda is: what are we doing that is no longer serving us? The regularity normalises it. It stops feeling like a challenge and starts feeling like housekeeping. In one-to-ones, try: “Is there anything you have been wondering about but have not felt comfortable raising?” Then leave the silence long enough for an honest answer.

3. Visibility of what happens next

Nothing kills the question faster than it disappearing. If a team member raises a concern and three weeks later nothing has changed and nobody has mentioned it, the message is clear. Even if the answer is “we looked at it and decided to keep it as it is, and here is why” — that is enough. Visibility of the decision, not just the conversation, is what builds trust in the process. Where something does change as a result of a question, say so explicitly: “We changed this because someone asked whether it was still doing what we needed it to do.” That sentence is worth more than any engagement survey.

4. Separation of the question from the person

When asking why is heard as a personal criticism — of the manager who designed the process, or the colleague who maintains it — it will stop being asked. Make it explicit and habitual that the question is always about the work, not the person who created it. The framing matters: “Is this process still right for where we are now?” lands very differently from “why did we design it like this?” Model this yourself. When you ask why your own process exists, or acknowledge something you introduced has not worked as intended, you change what the question means for everyone watching.

Applying this in small and large organisations

In smaller businesses, the advantage is proximity — fewer layers between the question and the person who can act on it. The risk is that everything feels personal, because the team is small and the relationships are close. Separating the question from the person (condition four) is therefore the one to invest in most heavily early on.

In larger organisations, the barrier is usually structural. There are more inherited processes, more decisions made by people who have since left, and more layers insulating senior leadership from the frontline. Here, conditions two and three do the most work — building the structure to surface questions and making the outcome visible closes the gap that hierarchy creates. Middle managers are the critical group. Research consistently shows that when middle managers do not feel safe to ask questions, information stops travelling up the organisation. Investing in their psychological safety is an organisational intelligence issue, not a soft people programme.

Constructive challenge versus friction for its own sake

Not every person who asks why is genuinely curious about the answer. Some use the question to delay, avoid accountability, or re-litigate a decision that has been made. Leaders who have been on the receiving end of this are understandably more cautious, and that caution is legitimate. The distinction is usually visible over time: constructive challenge is specific, anchored in the work, and interested in the evidence when it arrives. Friction for its own sake is broader, more personal, and resistant to the evidence regardless. The response to both is the same in form — you investigate, you respond, you make the outcome visible. That process exposes the difference clearly enough that you can address the behaviour rather than the question, with a much stronger factual basis for doing so.

Where to start this week

Pick one process that has been running unchanged for more than two years. Bring it to your next team meeting or one-to-one and ask, openly, whether it is still the right approach. Observe what happens. If people engage readily, you are already most of the way there. If the room goes quiet, that tells you which of the four conditions needs the most attention.

The employee who asks why is not a disruption. They are your early warning system, your process reviewer, and your most efficient investment in staying sharp — all without a consultancy fee. They just need to know the question is welcome.

People Potential Success supports businesses with operational strategy, people management, and organisational development — and individuals with career transformation and support. If you would like to explore how we can help your business build a culture where people bring their best thinking to work, get in touch.