Something I have noticed in leadership team meetings is how easily a decision can appear more settled than it really is. The discussion may have been thorough, different views have been heard, and the person leading the meeting eventually brings matters to a close. A decision is stated, nobody raises another objection, and several people may even nod. Everyone leaves believing the subject has been dealt with.
A few days later, however, the organisation is behaving as though the choice remains open. One department continues with the previous approach, another waits for further clarification, and somebody produces additional analysis that quietly returns the original question to the table. Nobody has openly refused to implement the decision, but neither has much changed because of it.
It is easy for the leader to conclude that people were not listening, are resisting change, or simply need to be told more clearly what was decided. Any of those things may be true. Before repeating the instruction, however, it is worth considering another possibility: perhaps the disagreement did not end in the meeting. It simply moved into execution.
Silence is not the same as commitment
When a leadership team has spent a long time debating an issue, silence can feel like closure. The leader looks around the room, hears no further challenge, and assumes that the team is ready to move. Sometimes that assumption is entirely justified. People understand the reasoning, accept the choice, and leave knowing what they must now do.
At other times, the same silence conceals something less settled. A person may still believe that the decision creates an operational problem, but no longer expect another challenge to alter the outcome. Someone else may feel that their concern was acknowledged without being answered. Another may assume that the decision will soften once the practical difficulties become visible. What appears to be agreement is therefore only the absence of another objection.
The consequences rarely present themselves as open rebellion. They appear in more ordinary forms: delayed action, partial implementation, repeated requests for clarification, or a tendency to interpret the decision in whichever way requires the least change. By the time the leader recognises that commitment was missing, several weeks may have passed and frustration has begun to replace the quality of discussion that was needed in the first place.
This is an important distinction because a decision can end a discussion without creating the conditions required to carry it out. The organisation may understand what was decided while remaining uncertain about whether the people responsible for delivery have genuinely committed themselves to making it happen.
Why the room moves on
There is nothing unusual about a leader wanting to accept the nod and continue with the agenda. The conversation has already taken time, the arguments may be repeating themselves, and other matters are waiting. Asking whether people are truly committed risks reopening the disagreement just as the meeting appears to have escaped it.
This is where the leader's own reaction deserves attention. In my Leading Unmasked approach to coaching senior leaders, I use the word Mask to describe an automatic, learned response that becomes active when something feels psychologically dangerous. The Mask is organised around the false belief, 'I am not enough', and tries to prevent that belief from being exposed. Because it works through our own thoughts and feelings, its influence can sound remarkably like sensible judgement.
In this situation, the Mask may insist that everybody has already had their opportunity to speak and that a capable leader now needs to take control and move on. Doing so restores a sense of authority and certainty. Inviting one more honest response creates the less comfortable possibility that the room is not as aligned as it appears, or that the leader has not yet brought people with them.
The same process may be operating for other people around the table. Challenging a decision again can feel like challenging the leader, particularly when the direction of travel is already obvious. A person who says that they cannot yet support the decision may fear being regarded as difficult, negative, or disloyal, so silence becomes easier than candour. None of this means that every hesitation is Mask-driven, or that discussion should continue until everybody agrees. It means only that a leader should be careful not to mistake the end of debate for the beginning of commitment.
Give disagreement somewhere useful to go
McKinsey recently described professional dissent as a duty rather than an act of defiance. The argument is not that leaders should surrender decisions to endless discussion. It is that better decisions become possible when challenge is legitimate before the choice is made, and when the people involved can then move into disciplined execution afterwards. That distinction is useful because it separates agreement, which may never be complete, from commitment, which the organisation still requires.
Read McKinsey's article on courageous conversations.
Instead of asking whether everybody agrees, I would end a consequential discussion by asking three more precise questions. First, what concern have we not resolved? This allows dissent one final opportunity to improve the decision, without pretending that every concern must determine the outcome. Second, can each person commit to implementing the decision even if it was not their preferred choice? This makes it possible to disagree honestly without withdrawing from collective responsibility. Finally, what will each person now do differently, and by when? Commitment becomes far easier to assess when it is translated into observable action.
A hesitation at this point is useful information. It is better to discover in the room that somebody cannot yet commit than to infer their commitment from silence and discover the truth three weeks later through missed actions and quiet resistance. The purpose is not to force a declaration of loyalty, but to make the remaining difficulty discussable while the people who can resolve it are still together.
If the CEO in our earlier meeting had taken another five minutes to test commitment, an executive might have named the implementation risk that was still troubling them. Another might have said that the chosen option was not their recommendation, while confirming that they could support it. The team could then have agreed what would actually change on Monday morning, rather than leaving the organisation to decide whether the decision was real.
The quality of a leadership decision is not measured only by the reasoning that produced it. It is also revealed by what happens after people leave the room. When disagreement is given a legitimate place in the discussion, it is less likely to find an unhelpful one in the execution.
Until next week,
Gavin