A long meeting that produces no decision often begins in a familiar way: each person reports what they have done, what is blocked and what they will do next week. That information may matter, but it does not necessarily require an hour of shared time. When the group only listens to updates, the meeting becomes an oral bulletin rather than a place to resolve difficult choices.
The answer is not to ban updates. It is to separate updates from decision time. An organisation that does this can reserve meetings for work that benefits from direct discussion: choosing priorities, resolving resource conflicts, identifying risk and assigning a clear owner for the next step.
Separate information from decisions
Before sending an invitation, the meeting owner should write one short sentence: what must this meeting decide? If that question cannot be answered, the session is probably an update and should become a short written record in a shared system. If the answer is “choose between two options”, “decide which team receives more resources” or “determine whether to stop an experiment”, the meeting has a clear reason to exist.
Consider a marketing team preparing a year-end campaign. Reach and advertising-cost reports can be sent in advance. The meeting should focus on one question: should part of the budget move from a channel that creates many views to a channel that creates fewer leads but converts at a higher rate? With that question visible from the start, every piece of information in the room serves a particular choice.
Send a decision pack before the meeting
A useful decision pack need not be long. It usually contains four parts: a short context, the essential data, realistic options and the preparer’s initial recommendation. Participants should know what they are being asked to consider; they should not wait for someone to read aloud what was already written.
Instead of an invitation titled “CRM project progress meeting”, the owner might write: “Decide whether to move the launch back two weeks to complete order-data integration, or keep the current date and remove automated segmentation.” The pack then states the cost of each option, customer risks and the implementation owner. The discussion starts where it creates value: which trade-off is acceptable.
Bring the right people into the room
Inviting everyone who is “related” is the easiest way to create a crowded meeting that cannot decide. The people who need to attend are the decision maker, those with irreplaceable data or expertise, and those who will carry out the work after the decision. People who need the outcome but do not need to debate or commit resources can receive the record afterwards.
This does not mean excluding viewpoints. Before the meeting, the owner can seek written input from affected parties. During the meeting, it should be explicit who makes the final call. If everyone discusses but nobody can conclude, the session easily becomes a repeated feedback loop.
Close with a decision that has an owner
A good meeting does not end with “let’s look into it.” That may sometimes be necessary, but it must come with a clear condition: what more must be known, who will obtain it, by when, and when the decision will be made. Otherwise, the unresolved work is merely pushed to another meeting.
At the end, record three lines: the decision, the next-step owner and the review date. For example: “Keep the 15 November launch date; defer automated segmentation; Lan completes order-flow testing by 8 November; the team meets on 9 November only to confirm readiness.” Those three lines matter more than the entire discussion because they turn conversation into operations.
Measure meeting quality by outcomes, not hours
Many organisations track the number of meetings or attendance rates but miss the more important question: after each meeting, what was decided, and was it carried out? Three simple indicators can help: the share of meetings with a recorded decision; the share of agreed actions with an owner and deadline; and the share of decisions reopened because data or the right participants were missing.
Not every meeting requires a major decision. Some exist to coordinate, learn or handle a crisis. But for recurring management meetings, the principle should be clear: information is read beforehand, discussion is used to choose, and the session ends with a commitment that can be followed. A less crowded calendar then does not mean the organisation communicates less. It means shared time is used for the work only shared time can do.
