The Most Expensive Conversations Your Organisation Isn’t Having

There’s a dynamic I’ve observed inside transformation programmes so consistently that I’ve come to treat it as a warning sign.

The steering committee meeting runs smoothly. The update is delivered. Questions are invited. A few are asked and answered. Heads nod. The plan is approved. People leave the room and return to their desks.

And then, in the corridor, in the smaller meeting that follows, in the messages exchanged between people who trust each other, the real conversation happens. The concerns that weren’t raised. The assumptions that felt too risky to challenge. The doubts about whether the approach will actually work in practice that nobody wanted to be seen voicing in front of the sponsor.

That gap, between what gets said in the room and what people actually think, is one of the most costly and least visible problems in large-scale transformation. And in my experience, it’s operating at some level in almost every organisation navigating significant change.

Why silence looks like agreement

The social dynamics that produce this pattern are entirely understandable. Speaking up in a meeting carries risk, particularly when the person at the head of the table has clearly already formed a view. Raising a concern can be read as obstructionism. Challenging an assumption can feel like questioning someone’s competence or commitment. In cultures where harmony is valued and conflict is uncomfortable, the path of least resistance is to stay quiet, let the decision be made, and hope that the concern you didn’t raise turns out not to matter.

The problem is that it usually does matter. And by the time it surfaces, the organisation has committed resources, made promises to the board, and built a plan on a foundation that several people in the room knew was fragile and said nothing.

This is not a hypothetical risk. It’s a specific and recurring failure pattern in transformation programmes. Decisions get made with apparent consensus that masks significant private doubt. Implementation runs into exactly the resistance or complexity that someone around the table could have predicted. The cost of course-correcting at that point is a fraction of what it would have been if the concern had been surfaced earlier.

What leaders inadvertently do to make this worse

Most senior leaders don’t intend to suppress honest disagreement. In fact, most would describe themselves as genuinely open to challenge and alternative perspectives. The issue is that intention and impact are not always the same thing.

When a leader enters a meeting having clearly already formed a strong view, the room reads that signal and responds to it. When challenge in previous meetings has been met with defensiveness or dismissal, people learn quickly that the invitation to disagree is theoretical rather than real. When the culture rewards alignment and smooth delivery over the kind of honest friction that surfaces problems early, people optimise accordingly.

The result is a leadership team that is systematically less well-informed than it believes it is. Assumptions that should be tested aren’t. Risks that are visible to people closer to the work never reach the people making the decisions. And the organisation develops a kind of institutional overconfidence, not because things are going well, but because the signals that things aren’t going well are being filtered out before they arrive.

The difference between productive disagreement and destructive conflict

None of this is an argument for making meetings more combative or for treating challenge as inherently virtuous. There’s an important distinction between productive disagreement, focused on ideas, assumptions and trade-offs, and destructive conflict, focused on personalities, territory or blame.

The first is one of the most valuable inputs a leadership team can have. It stress-tests decisions before they’re made. It surfaces the concerns that would otherwise emerge as resistance during implementation. It creates the kind of genuine collective commitment that comes from having been heard and having participated in a real decision, rather than the surface compliance that comes from being told.

The second erodes trust and wastes energy and should be managed firmly.

What creates productive disagreement isn’t the absence of conflict. It’s the presence of enough psychological safety that people feel the risk of speaking honestly is lower than the risk of staying quiet. That’s a condition that leaders create or fail to create through their own behaviour, consistently and over time.

What this looks like in a transformation context

The specific cost of suppressed disagreement in a major technology programme is worth being concrete about. Assumptions about how people will respond to new ways of working go unchallenged in design sessions because nobody wants to be seen as the person questioning the approach. Concerns about implementation timelines aren’t raised in steering committees because the pressure to maintain confidence in the programme is too high. Risks that are visible to frontline managers never reach the programme board because the escalation culture doesn’t support it.

Each of these silences is individually small. Cumulatively, they produce a programme that is less resilient, less well-designed, and more likely to encounter avoidable problems than it needed to be.

The most effective antidote I’ve found is straightforward in principle, though it requires consistent effort in practice. Leaders who want honest input need to signal, repeatedly and credibly, that honest input is genuinely valued. That means responding to challenge with curiosity rather than defensiveness. It means actively seeking out the views of the people least likely to volunteer them. It means occasionally changing a decision based on something someone said in a meeting, and making that visible.

None of that is complicated. But it requires a degree of deliberate attention that the pace of most transformation programmes tends to crowd out.

The conversations your organisation isn’t having are not a minor cultural nuance. They are a material risk to your programme’s success. And they are, unlike many of the challenges in large-scale transformation, almost entirely within your control to address.