Everyone Agreed but Nobody Made the Decision

The meeting ends warmly. The proposal sounds sensible. People thank the person who prepared it, offer a few suggestions, and say they are happy to move forward.

The following week, the work stalls. One person thought the budget was approved. Another thought approval would happen after revisions. The person expected to authorize the change believed the group was still discussing options.

There was genuine agreement in the room. Its meaning was never made precise enough to support a decision.

Distinguish support from authorization

“That looks good” can mean several things. Someone may like the direction, agree with the reasoning, or consider the document ready for a formal approval process. The sentence alone does not tell you which.

In a fictional publishing meeting, a team discusses changing a launch date. The editor supports the change. The designer says it would help. The person responsible for confirming arrangements has not yet decided. If the minutes record “new date agreed,” discussion has quietly become authorization.

Before closing, ask what decision has actually been made and by whom. Follow the organization's rules about authority, consultation, and approval. A useful record reflects those rules; it cannot replace them.

Where a formal decision is still pending, state that plainly. “The team supports moving the date. Confirmation is pending the publisher's approval.” This prevents a favourable conversation from becoming a promise to other people.

Write the decision in a sentence that can be checked

A record such as “We discussed the supplier” does not establish what anyone should now rely on. Describe the choice and its scope: “The authorized manager approved obtaining quotations from two suppliers; no purchase was approved.”

That sentence distinguishes permission to investigate from permission to commit. It protects the next person from filling the gap with their own expectation.

Include conditions that materially affect the choice. Perhaps a date applies only if required information arrives by Thursday. Perhaps an exception applies to one event rather than every future event. Keep those limits with the decision rather than burying them in background notes.

Do not fill the record with every sentence spoken. Preserve what is needed to understand the authorized choice, the reasoning that affects its application, and the next action. If the wording is disputed, resolve the dispute through the appropriate route before others rely on it.

Give a pending decision a route

Some meetings cannot make the decision. Required information may be missing, or the decision-maker may be absent. A meeting can still make progress if it establishes what must happen next.

Identify the missing item, who will obtain it, who will decide, and the point at which the matter will return. Agree those responsibilities with the relevant people; do not assign an absent colleague a deadline they have never accepted.

If nobody has authority to decide, name that as the unresolved problem. Another round of preparation may be unnecessary until the organization identifies the appropriate route.

Similarly, do not keep asking a researcher or coordinator to improve a document when the real obstacle is an approval nobody is willing to give. The distinction matters because more work on the paper will not necessarily move the decision.

Check what different people heard

Near the end, read back the proposed decision record. Ask whether it accurately states the choice, conditions, and authority. Give participants a clear opportunity to correct it.

This is particularly useful when polite language has carried much of the discussion. Silence should not automatically be recorded as formal consent unless the governing process expressly permits it and its requirements have been met.

Use accessible wording and allow clarification. A participant working in an additional language may need a moment to inspect the exact decision. So may anyone encountering unfamiliar terminology. Precision helps the whole group.

Then share the record through the approved channel and distinguish any proposal still awaiting confirmation. In regulated or high-consequence work, follow the required approval and recording procedures; these general prompts do not substitute for them.

A short record can keep the distinctions together: “Decision: obtain two quotations. Approved by: the manager responsible for this budget. Limit: no order may be placed. Pending: compare the quotations and return for purchase approval on Thursday.” These entries are an illustrative structure; use your organization’s required record where one exists.

At your next meeting, reserve a brief closing moment for one question: “What can someone outside this room accurately say we decided?”

If the answer remains unclear, keep the uncertainty in the record. An honest pending decision is easier to manage than a completed task built around approval that never happened.

Related reading: A Handover Ends When the Next Person Can Act.