At a board meeting, a difficult decision is made. The presentation is polished, the discussion short, several heads nod in time with the slides. The minutes say: adopted unanimously.
Three weeks later the decision isn’t working. Not because someone blocked it – in three departments, nothing simply happened. Implementation is “ongoing”. Questions like “how’s it going” get the answer “we’re working on it”. After a quarter, the topic comes back to the board in the form: we need to discuss this again.
Nobody killed that decision. It’s just that nobody fed it.
Over years of working with management teams, I’ve learned that this isn’t an accident. It’s a repeatable mechanism – and it has a name.
What is false agreement?
False agreement is a situation in which a management team formally adopts a decision even though some of its members have significant, unspoken reservations about it. In the room there is consensus; the dispute moves outside it – to one-to-one conversations, to the departments, to the way the decision is later implemented. Or not implemented.
It differs from ordinary disagreement in one way: it is invisible to the decision-maker. The CEO leaves the meeting feeling that the team is behind them. What they have behind them is the minutes.
Why do experienced people stay silent?
In none of the teams I have assessed did the silence come from having no opinion. Board members are people with strong views – which makes it all the more worth understanding what silences them.
The first reason is the calculation that the matter is already settled. If the CEO’s tone suggests the decision has already been made, voicing doubts stops being influence and becomes a demonstration. Experienced managers don’t spend political capital on demonstrations.
The second is the organisation’s memory. People know perfectly well what happened to the last person who said “I disagree” in front of everyone. If they paid for it – even only with coldness – the whole team learned the lesson, for years.
The third reason is mundane: the materials arrived late last night. It’s hard to challenge an analysis there was no time to read. It’s easier to nod and keep the doubts for later.
The fourth is the most human: caring about relationships. In long-standing management teams, a dispute can be perceived as an attack on the person rather than the argument. So for the sake of the atmosphere, people say “fine” – and go their own way.
Note that each of these reasons is rational from the individual’s point of view. False agreement isn’t the sum of weaknesses of character. It is people’s rational response to a system in which open disagreement doesn’t pay.
How does a decision that nobody feeds die?
A strategic decision doesn’t implement itself. To survive, every board member has to explain it in their own area, defend it, shift resources towards it and send information about problems back up.
That is the feeding – the daily, invisible work that isn’t in any minutes.
Someone who isn’t convinced won’t do this work. They don’t have to sabotage – it’s enough for them to be neutral. They’ll pass the message on to their team in the words of the presentation, without their own signature on it. They’ll answer questions with “that’s what was agreed”. When there’s a conflict of priorities, the decision will lose to whatever they really believe in. And when implementation starts to grind, they won’t be the first to report it – because why be the bearer of bad news on something you never bought into?
Multiply that by two or three unconvinced directors and you get exactly this picture: the decision dies in three departments at once, without a single act of opposition.
The most expensive conflicts in companies are the ones that never erupted – because the cost of a dispute that did happen is measurable and one-off, while the cost of a suppressed dispute is spread over months of an implementation that never stood a chance.
A cost you can’t see in the quarter
The loss on a single decision is only the start of the bill.
More serious is that the board loses its calibration. If everything passes unanimously, the decision-maker stops getting signals about which ideas are strong and which the team accepted through gritted teeth. The quality of decisions falls – while the sense that everything is fine grows.
And one level down, something even more lasting happens: the organisation learns that meetings are a ritual.
Directors who stay silent on the board then read their own people’s silence as agreement – and the pattern cascades down. The company becomes skilled at unanimity at exactly the rate at which it loses the ability to make decisions.
How to recognise false agreement before it sends you the bill
A few signals I see most often when assessing management teams:
Unanimity is the norm. A team in which nobody has voiced a dissenting view for quarters isn’t in sync – it’s been silenced. Given the real complexity of business, differences of opinion are a statistical necessity; their absence in the room only means they live somewhere else.
Decisions come back. Matters that were formally closed reappear on the agenda “for clarification”. That’s a dispute that wasn’t allowed to happen the first time.
Implementations start without energy. Between “adopted” and the first real action, time passes that nobody can explain.
The most interesting conversations happen after the meeting. If “this won’t work, you know why” is said in the doorway and by the cars – that’s where the real board is meeting.
What to do about it: work on how the meeting runs, not on appeals
An appeal to “be honest with each other” doesn’t work, because it doesn’t change the cost–benefit calculation of disagreeing. Concrete practices for running decisions do.
The decision-maker speaks last. If the CEO opens a topic with their own recommendation, the rest of the discussion is just people positioning themselves relative to the boss. Reversing the order – the team’s voices first, the decision-maker’s last – is the cheapest intervention with the biggest effect that I know of.
Doubts on request. Instead of asking “any comments?” (to which the answer is silence), it’s worth asking by name: “Marek, what in this plan will crack first?” The question assumes that reservations exist – and removes the cost of being the one who spoils the mood. In a more mature version: a permanent role of devil’s advocate, assigned on a rotating basis before every significant decision.
Separating exploration from decision. Disagreement needs a space where it’s acceptable to think out loud without declaring a position. If the discussion and the decision happen in the same agenda item, people stay silent so as not to commit themselves. Two passes – first an open conversation, the decision at the next meeting – change the dynamics beyond recognition.
A commitment test instead of a vote. After the decision, every board member says one sentence: what specifically they will do in their area within two weeks to keep this decision alive. Anyone who can’t name anything has just signalled that they haven’t bought it – and it’s better to find that out now than in the third month of implementation.
A return date. The decision gets a review date written down at the moment it is made. That legitimises talking about problems – reporting “it isn’t working” stops being a betrayal and becomes an agenda item.
The most common mistake
Boards that recognise false agreement in themselves most often reach for the least effective solution: a message to the team about openness and a feedback culture. That addresses declarations, not behaviour – and people stopped believing declarations long ago; they believe what they have seen.
Reversing the pattern starts with proof: someone says “I disagree” in front of everyone – and nothing bad happens to them. More than that: their reservation changes the shape of the decision, and this is said out loud. One episode like that does more for the safety of disagreement than a year of communication workshops. Two or three begin to change the culture.
That’s why this work always starts at the top – with the decision-maker’s behaviour in the room, not with training the team.
One question for today
When did someone on your board last say out loud “I disagree” – and what happened to them afterwards?
If the answer requires reaching far back into memory, that isn’t proof of agreement. It’s proof that the disagreement that should be happening at your table is happening somewhere else – and that you find out about it last, after the costs.
Agreement can be distinguished from silence – by behaviour, not by declarations. That is exactly what a management team assessment is for: it shows how your team really makes decisions before the next one dies of starvation. If this text sounds familiar – write to me. Thirty minutes of conversation, your examples, not my slides.