Many organisations have full meeting calendars yet remain slow to decide, send work through repeated loops, and encounter the same familiar problems almost unchanged the following week. The cause is often not that people have failed to report enough. An operating meeting loses its purpose when it merely collects updates for people to hear, rather than enabling stuck work to move ahead with a clear owner, choice, and review point.
A meeting does not need to resolve everything. Its value is in creating several important shifts that scattered exchanges cannot easily achieve: settling a conflicting priority, unblocking a handoff, choosing between contested options, or intervening early in a risk. Without defining the kind of shift required, teams tend to use shared time to repeat information that everyone could have read beforehand.
Distinguish an update from an operating issue
An update answers, “What happened?” Operating management must also answer, “What do we need to decide or change now?” Sales reports, project progress, and customer feedback remain necessary, but not all information needs to be presented live. Stable information that does not require a shared choice should be sent beforehand in a short structure: metric, trend, exception, and request for support if one exists.
Shared time should be reserved for consequential exceptions. For example, a sales team may report that conversion has fallen. That is only an update. The operating issue begins when the group must choose whether to adjust lead-screening criteria, reallocate technical support, or change the message for a segment responding differently. A well-formed question moves the discussion from describing an observation to making a choice with an accountable owner.
| Content | How to handle it | Sign that the meeting creates value |
|---|---|---|
| Stable information | Send it beforehand for participants to read. | No live time is spent rereading slides. |
| A metric off plan | State the gap, known causes, and what remains uncertain. | The group agrees what to investigate or intervene in. |
| A priority conflict | Bring options, consequences, and the person with decision rights. | A choice is made with its rationale and limits. |
| A blocked handoff | Describe inputs, outputs, timing, and owners on both sides. | The handoff rule or resources are adjusted. |
Prepare with a decision question
Every item brought to the meeting should begin with an answerable question, not the name of a broad topic. “Discuss the fourth-quarter campaign” does not tell the group what it needs to do. “Should we keep the launch date when two content items have not cleared legal review?” identifies the decision, relevant information, and people who need to be present. The preparer does not need to have a solution ready, but does need to clarify context, realistic options, and the consequence of delaying the decision.
This approach also helps invite the right people. Not everyone connected to an issue needs to attend the entire meeting. Invite people with necessary evidence, people who can commit resources, and people with authority to choose when priorities conflict. Those who only need to know the outcome can receive a short record afterward. Respecting time is not about shortening every discussion at any cost; it is about putting the right people with the right problem.
Example: turning a progress report into an operating decision
A digital-services company holds a weekly meeting to update customer implementation projects. For three consecutive weeks, the technical team reports delays caused by late change requests. Previously, the point was recorded and carried into the next week. After changing the meeting design, the coordinator asks: “From this week, should we stop accepting changes once the test plan is locked unless the project director approves an exception?” The group reviews the number of change requests, rework cost, and cases that customers genuinely need urgently. It agrees a new handoff rule, appoints an exception approver, and sets a review two weeks later. The meeting creates value not because people talked more, but because a bottleneck became an observable rule.
Facilitate discussion toward a choice
The chair’s role is to keep the question from drifting. When discussion moves into unnecessary detail, the chair can ask whether that detail changes the choice. When views diverge, separate what is known, what assumption is being used, and what needs checking. This separation reduces debate based on general impressions and helps the group identify where new evidence is actually needed.
Before moving on, four elements need to be spoken clearly: the decision or course of action, the owner, the work to complete, and the time to review it. “Operations will handle more” is not trackable. “Lan will review the ten cases returned this week, propose two changes to the handoff form, and send them before Thursday” lets everyone know what will happen after the meeting. If the outcome is only a vague note, the issue will usually return under another heading.
Design a meeting rhythm, not only individual meetings
Some issues should not be resolved in a weekly meeting. Decisions about direction, capital allocation, or an operating-model change need a longer rhythm and deeper material. Conversely, daily coordination bottlenecks need a short rhythm close to the work. When every type of issue is placed in one meeting, small problems are stretched out and large problems do not receive enough thinking time.
Teams should therefore identify each rhythm clearly: a short meeting for near-term coordination, a weekly meeting for exceptions and priorities, and a monthly meeting for trends, resources, and cross-functional choices. The calendar is only the frame. More important is what input each rhythm requires, what kind of questions it handles, and what output must exist when it ends.
Measure quality through the work after the meeting
A meeting should not be judged mainly by a feeling that it was quick or that everyone participated. Look at the commitments made: are they completed on time, does the same issue return without new information, and are decisions implemented consistently at handoffs? If many commitments remain open, the organisation should examine the volume of decisions, the authority of participants, and the clarity of assignments rather than simply adding more meetings.
A good operating meeting leaves a trace in work: a priority becomes less ambiguous, a rule changes, a risk has an owner, or a commitment is checked at the right time. When a team designs meetings around these traces, shared time becomes part of the operating system rather than an interruption in the work calendar.
