Decisions Don’t Travel: Making Agreement Survive the Walk to the Lift

A familiar pattern plays out in many UK organisations. A meeting reaches its conclusion. Heads nod. Actions are mentioned. Everyone returns to the corridor, the lift, or the tea point, and within ten minutes a quieter conversation begins: ‘I wasn’t sure about that’, ‘That won’t work in practice’, or ‘I thought we had decided something different.’

The decision was not necessarily wrong. The problem is that it never travelled. Agreement in the room is often a social achievement rather than an operational one. It reflects the tone of the discussion, the seniority of those present, and the politeness that characterises much of British working life. It does not always reflect what people will do when they return to their desks.

For managers and team leads, the task is not to eliminate corridor conversation. Informal discussion is often where useful information surfaces. The task is to design meetings and follow-up so that dissent is heard before it becomes drift, and so that decisions arrive in the working week with owners, context, and a realistic chance of being enacted.

Why the room flatters agreement

Meetings are poor environments for honest disagreement. Time is short. Senior people are present. Challenging a proposal can feel like challenging the person who proposed it. Silence is easily read as consent, especially when the chair is keen to finish and the agenda is already running late.

In 2026, with many teams working across hybrid patterns, the problem is sharper. Some colleagues attend in person; others join by video. Side conversations happen in different spaces. The people most likely to raise a concern may be the least likely to do so in front of the group, particularly if they are junior, new to the team, or dependent on the decision-maker for their next assignment.

The corridor conversation is therefore not automatically disloyal or obstructive. It is often the first safe opportunity to test a concern. The mistake is to treat it as noise rather than as evidence that the decision was insufficiently tested.

Close with ownership, not applause

A meeting should not end with a general sense that something has been agreed. It should end with a small number of explicit statements that can survive outside the room.

At the close, ask for four things to be stated aloud: the decision, the person accountable for delivery, the date by which the first visible step will happen, and the person responsible for communicating the decision to those who were not present. These are not administrative details. They are the difference between a discussion and a commitment.

Use names rather than teams. ‘Operations will handle it’ is not ownership. ‘Priya will confirm the revised rota by Thursday and will tell the Birmingham supervisors before Friday’ is ownership. If no name can be given, the decision is probably not ready to leave the room.

It is also worth stating what has not been decided. Meetings often produce a false sense of completeness. A clear note that ‘we have not agreed the budget for this’ prevents people from filling the gap with assumption and then discovering the mismatch three weeks later.

Test for dissent before the room empties

A chair who asks ‘any questions?’ at the end of a meeting will usually receive none. A better approach is to make disagreement a specific, bounded task.

One simple method is a final round in which each person is asked to complete a sentence: ‘The thing most likely to stop this working is…’ The answers do not need to be long. The purpose is to give the room permission to name a risk while everyone is still present. The chair should record the risks and decide whether they change the decision, require a mitigation, or need to be carried forward as a known issue.

A second method is to ask people to distinguish between support and acceptance. Some colleagues will never love a decision but can work with it. That is different from active opposition. Asking ‘Can you support this, or can you only live with it?’ is more useful than a vague request for buy-in, because it surfaces the difference between commitment and compliance.

For hybrid meetings, use the chat function deliberately. Ask for concerns to be typed before the close, then read them aloud without attribution if necessary. This lowers the cost of raising a problem and prevents the meeting from ending on a false consensus.

Make follow-up do real work

Most follow-up communication is a summary. It restates what was discussed and confirms the actions. That is necessary, but it is not enough. A good follow-up should extend the decision into the working week.

Send a short decision note within twenty-four hours. It should include the decision, the owner, the first milestone, the impact on other work, and a clear invitation to correct the record. Add a line such as: ‘If you have a concern that was not raised in the meeting, please reply by midday tomorrow so it can be considered before work begins.’ This gives the corridor conversation a formal route into the process.

Follow-up should also distinguish between new information and unresolved dissent. If someone raises a genuine new risk, the decision may need to be revisited. If someone is simply unhappy with a choice that was properly made, the manager should acknowledge the concern without reopening the whole debate. The aim is not endless consultation. It is a fair and visible process for raising issues before they harden into resistance.

Treat the corridor as an early warning system

If the same concern keeps appearing in corridor conversations, it is no longer a corridor issue. It is a signal that the team lacks a safe or structured way to raise it earlier.

Managers should therefore listen for patterns rather than individual complaints. Are people repeatedly unsure who owns a decision? Are they hearing about changes from colleagues rather than from the manager? Are they agreeing in meetings and then seeking reassurance afterwards? These are process problems, not personality problems.

A short implementation check two weeks after a significant decision can help. Ask the people closest to delivery what they are hearing and what is getting in the way. Do not ask whether they agree with the decision. Ask what has become clearer, what has become harder, and what they need now. That conversation is more likely to reveal drift while it can still be corrected.

Agreement is not the same as alignment. A meeting can end with the first and leave the second untouched. The practical work is to make the decision explicit, test it before the room disperses, and give follow-up communication enough substance to carry it into the ordinary routines of the team. Decisions do not travel by themselves. Managers have to send them.