The yes that does not mean yes

A manager announces a reorganisation of their department. They explain, they answer two or three questions, they ask whether everyone is on board. Nobody objects. They leave the meeting thinking it went well.

Three weeks later, nothing has changed. Deadlines slip, the old habits hold, and in a conversation at the pantry they discover that part of the team had considered the decision unworkable from day one.

They conclude there is a commitment problem. That is almost always wrong.

Nobody lied

Surface agreement is not a collective lie. In most cases everyone said the only thing available to them at the moment they were asked.

Three things make “no” unavailable in a meeting. The first is the order of speaking: once the senior person has given their view, and especially once they have defended it, the discussion is closed before it opens. Contradicting is no longer discussing a proposal but opposing a person, which is a different act and carries a different price.

The second is the presence of colleagues. An objection raised one to one is a contribution; the same objection raised in front of twelve people is a position, and it commits whoever voices it well beyond the subject at hand.

The third is sharper in Singapore than many managers arriving here expect. Seniority is respected, and in a great many teams it is respected in silence. Someone who thinks a decision is poor will often consider that saying so in the room is not their place — not out of fear, but out of a convention of respect that is not irrational and that nobody is going to abolish with an invitation to speak freely.

On top of that, the meeting is almost always held in English, which nearly everyone follows easily and which, for a large share of the room, is a second or third language. Following a discussion and arguing in it are not the same skill. The cost of objecting rises again.

Disagreement does not disappear, it relocates

This is the most underestimated part. A disagreement that could not be voiced before the decision does not evaporate. It resurfaces elsewhere, in forms the manager does not connect back to the meeting:

• deadlines that slip with no precise explanation;
• the instruction followed exactly to the letter and never beyond it;
• repeated technical questions which, taken together, say the project makes no sense;
• the informal version circulating in a side chat, which is the only place you hear what people actually think.

It is also what makes reorganisations fail.

Each of those signals costs time. Together they cost far more than the ten minutes a real discussion would have taken.

Six devices that produce the objection

What works is not exhortation. Nobody speaks up more because they were told speech is free. What works is procedural.

Have people write before they talk. Two minutes, everyone notes the two obstacles they can see. Then the notes are read out. A written objection has already come out; saying it aloud has become much cheaper.

Hold your own view back. The senior person speaks last, without exception. It is the cheapest measure and the hardest to sustain.

Change the question. “Any questions?” never gets an objection. “What could stop this working?” almost always does, because it asks for expertise rather than for opposition.

Assign the objector role. One person is charged, for this meeting, with finding what will not hold. With the role assigned, contradicting costs nothing socially — it is what they were asked to produce.

Start with the least exposed. Ask the least senior or most recently arrived people first. Once the department head has spoken, nobody is going back.

Check by having it said back. Ask two people to state, in their own words, what they are going to do and in what order. It is the only reliable test of understanding, and it surfaces the disagreements that “can, no problem” had covered over.

What you have to accept in exchange

These devices work, and they have a price: meetings become less comfortable. You hear objections, some badly worded, some poorly founded. They have to be received without being treated as attacks, including the ones that call the manager’s own work into question.

Holding that requires a frame set beforehand, which is what the core programme on the manager-leader toolkit works on.

That is the real condition for the whole exercise. A team always tests once: it raises a serious objection and watches what happens to the person who raised it. If the response is defensive, the process is dead and will not restart. If nothing unpleasant happens, the rest follows on its own.