A meeting needs a decision, not another report

A useful management meeting turns reliable information into clear decisions, named responsibilities and an agreed way to check whether the action worked.

The meeting lasts an hour, every department gives an update and the same issues return next week. The missing ingredient may not be commitment. It may be that nobody has defined which decisions the meeting must produce or what evidence will show that an action is complete.

A useful meeting gives information a purpose. It separates matters that can be read beforehand from matters that need discussion, challenge or a decision. It also makes the next action clear enough that people do not leave with different interpretations.

Decide what belongs in the room

Start with the outcome. Is the meeting reviewing performance, resolving an obstacle, allocating resources or making a choice? A broad label such as management meeting does not answer that question. Several outcomes can share a meeting, but each agenda item should have an explicit job.

Reports should arrive early enough to be read. The agenda should identify what requires a decision and what is included for information. If an update needs no discussion, consider whether written circulation serves it better. Do not remove useful conversation merely to shorten the meeting; remove ambiguity about why the conversation is happening.

Ayodeji's established meeting structure begins with previous minutes and action review, then departmental updates with feedback, other business and adjournment. The value of that order is continuity: current discussion begins with what the team already agreed to do.

Use the action review to learn

An action register needs more than a task and a due date. Record one accountable owner and the evidence that will demonstrate completion. Improve customer service is too broad. Review the last set of unresolved complaints and agree an escalation rule is clearer.

When an action is incomplete, ask what prevented it. The explanation may be an unrealistic estimate, a missing decision, competing work or a genuine performance issue. Treating every delay as laziness hides information the manager needs. Accepting every explanation without consequence is equally unhelpful.

If the same action moves from week to week, change something. Reduce its scope, resolve the dependency, assign the correct owner or explicitly cancel it. Repeatedly copying it into the next minutes creates the appearance of management without a decision.

Make reports comparable

A department update should distinguish the intended result, actual result, explanation of the gap and proposed action. Use the same definitions and periods so the team can compare changes. A sales total for one period and a cost total for another can produce a misleading discussion.

Ask for a small number of useful measures, not every figure available. The right measure depends on the work. Delivery reliability, qualified enquiries, collection timing and rework may reveal more than a long list of activities completed.

A report should make exceptions visible. If everything is described as progressing well until a problem becomes urgent, the reporting system is not serving management. The team needs a safe, clear way to raise an issue early while retaining responsibility for addressing it.

A good meeting ends with fewer unresolved decisions, not merely more detailed minutes.

Close the loop before leaving

Read back the decisions and actions. Confirm the owner, due date and completion condition. Clarify who needs to be informed and which existing plan has changed. This short step catches misunderstandings while the relevant people are still available.

Keep a distinction between a decision and a suggestion. A discussion can contain many ideas without approving all of them. The minutes should not make tentative exploration look like a binding instruction. Similarly, an agreed decision should not disappear into a vague summary.

Estimate meeting time cost where it helps judgement, but do not confuse cost with waste. A necessary decision can justify an expensive gathering. The question is whether the outcome merits the people and time involved.

Improve the next meeting with one change

Do not redesign every management routine at once. Choose one recurring meeting and add a decision required line to each agenda item. Ask participants to submit the relevant information in advance. Reserve discussion for interpretation, obstacles and choices.

At the next review, examine whether actions were clearer and whether fewer items returned without progress. Ask the team which information was missing and which part of the agenda served no useful purpose. A routine should improve through use rather than become a ritual nobody is allowed to question.

Which matters should be resolved before the meeting?

Basic factual corrections should be made before the discussion where possible. If a department report contains a missing total or an unexplained date, ask for clarification early enough that participants can read a coherent version. Meeting time is valuable when people interpret the evidence and decide what to do. It is less useful when several managers wait while somebody searches for a figure that should already have been prepared.

That does not mean disagreement must be removed in advance. Different interpretations can be exactly what the meeting needs to examine. Keep the distinction clear between a disputed fact, a different explanation and a different preference. A fact may require another record. An explanation may require a test. A preference may require a decision about trade offs. Treating all three as the same kind of disagreement makes the conversation longer and the conclusion less clear.

What should happen when an action is blocked?

Ask the owner to describe the dependency precisely. Waiting for finance is less useful than naming the approval required, the information already supplied and the date by which the decision is needed. The meeting can then resolve the dependency, assign an escalation or change the commitment. A vague obstacle cannot be managed because nobody can tell what would remove it. Clear reporting gives the team an opportunity to act before the deadline becomes a missed promise.

Record any change to the action rather than quietly moving its date. If the scope or priority has changed, preserve the reason so that the next review can understand the new agreement. Repeated delays may indicate that the estimate was poor, the task is not important enough to resource or the owner needs support. The appropriate response should follow the evidence. Repeatedly accepting a new date without changing any condition is unlikely to produce a different result.

How do you protect useful disagreement?

Ask participants to challenge the proposal with evidence and alternatives. A team that only confirms the most senior opinion may reach decisions quickly while missing important information. The chair should keep the discussion focused on the business question and make clear when a decision has been reached. People need room to raise a concern and clarity about the instruction that follows once the responsible person decides.

At the next meeting, review whether the decision produced the intended effect. Separate execution from effectiveness: an action can be completed exactly as agreed and still fail to solve the problem. That is a reason to revisit the underlying explanation, not to conceal the outcome in a completed task count. A management rhythm becomes valuable when it can learn from that distinction. Before approving the next action, name both the evidence of completion and the evidence that would show it made a useful difference.

Before sending the next agenda, write the decision required beside each item. If you cannot name it, decide whether the item needs a meeting at all.