A status update can be read.
A leadership meeting should do work that cannot be completed by reading alone.
It should surface reality, resolve the most important issues, make decisions, and create commitments that can be reviewed later.
When a meeting only moves information around the room, the company pays a high coordination cost for a low operating return.
Updates consume the time decisions need
A familiar meeting begins with each leader describing what happened in their area.
The first update runs long. Someone adds context. A second leader responds. The group follows a detail that matters to two people but not the whole team.
By the time the agenda reaches the difficult issue, fifteen minutes remain.
The group discusses it.
No decision is made.
The issue returns next week.
The problem is not that updates have no value.
The problem is that synchronous leadership time is scarce.
Use it for work that benefits from shared judgment:
- Resolving cross-functional conflict
- Making tradeoffs
- Changing a priority
- Assigning ownership
- Testing an assumption
- Escalating risk
- Deciding what will stop
- Committing resources
Routine information should arrive before the meeting in a form that leaders can review.
The meeting should begin where the written update ends.
The agenda should follow the operating system
A useful leadership meeting reflects how the company runs.
The agenda does not need to be elaborate.
It needs to connect the same operating elements each week:
- What changed?
- Which important measure is outside the expected range?
- Which priority is at risk?
- Which issue requires leadership attention?
- What decision must be made?
- Who owns the next action?
This creates continuity.
The team does not have to invent the meeting every week. Leaders know how to prepare. Recurring work has a home. Issues do not disappear because the agenda changed.
Consistency also makes the meeting easier to improve.
If decisions are not closing, the team can inspect the issue process. If metrics are never discussed, the scorecard may be too large or too weak. If every issue becomes a status update, the team may not be identifying the actual decision.
An issue is not a topic
Teams often place broad topics on the agenda.
Sales.
Hiring.
Product.
Customer success.
Those headings create discussion without defining the problem.
A useful issue is stated as a gap that requires a decision.
Instead of:
Hiring
Use:
The implementation team will exceed planned capacity in six weeks, and the company has not decided whether to hire, delay work, or change scope.
Instead of:
Pipeline
Use:
The current qualified pipeline cannot support the quarter target, and the team has not chosen whether to change the target, increase demand activity, or narrow the forecast.
The issue statement should make the decision visible.
That reduces the time spent discovering why the topic is on the agenda.
Decide at the right level
Leadership meetings become crowded when the team solves work that belongs somewhere else.
A departmental issue should stay with the department unless it crosses authority, strategy, resources, or risk.
A leadership issue usually includes one or more of these conditions:
- Two functions need different outcomes.
- A priority requires a company-level tradeoff.
- The owner lacks authority to decide.
- The risk crosses an agreed threshold.
- The issue affects the company model or customer promise.
- A senior role or resource decision is required.
Pushing every issue upward slows the company and weakens managers.
Keeping a company-level issue inside one function creates local optimization and delayed conflict.
The meeting should solve at the lowest level with enough authority and context.
The decision needs a record
A verbal decision can disappear by the next morning.
People remember different conditions. The owner interprets the commitment differently. A leader who missed the meeting reopens the question.
A decision record can be short.
It should capture:
- The issue
- The decision
- The owner
- The date
- The important reasoning or evidence
- The commitment
- The review point
- The condition that would cause reconsideration
The goal is not meeting minutes.
It is operating memory.
A company that repeatedly debates the same issue may not have a disagreement problem.
It may have no durable record of what was decided.
What this does not mean
Not every leadership meeting needs a dramatic decision. Some weeks the system is operating within its boundaries. The standard is not decision volume. The standard is whether important issues are surfaced early and the team can close decisions when they are required.
Candor determines meeting quality
A perfect agenda cannot repair a team that avoids reality.
The meeting depends on leaders being willing to say:
- The priority is off track.
- The number is wrong.
- The plan is no longer credible.
- The customer promise cannot be kept.
- The owner lacks capacity.
- The founder is reopening decisions.
- The team is discussing a symptom.
This requires a working level of trust.
It also requires standards.
Candor without accountability can become repeated confession without change. Accountability without candor becomes status theater.
A useful meeting holds both conditions:
People can state what is true.
The team still has to decide what happens next.
End with commitments, not summaries
A long recap often signals that the meeting did not produce enough clarity.
The close should be simple.
For each decision:
- What was decided?
- Who owns the next action?
- By when?
- What evidence will be reviewed?
- Who needs to be informed?
Then inspect the meeting itself.
Did the team solve the most important issue?
Did everyone have the information needed?
Did a senior person dominate the decision without evidence?
Did the meeting start and end on time?
What should change next week?
The meeting is part of the operating system.
It should be managed like one.
The leadership-meeting test
Ask:
- Could the routine updates have been read before the meeting?
- Are issues written as decisions or gaps?
- Does the agenda protect time for the most important issue?
- Is the issue at the right organizational level?
- Does the person with authority participate?
- Can the team state uncomfortable facts without punishment?
- Is the decision recorded?
- Is one person accountable for the next action?
- Is there a review date or evidence threshold?
- Does the same issue return because the decision was weak or because reality changed?
The answer should shape the next meeting.
Not another meeting about meetings.
Conclusion
A leadership meeting should not be a live inbox.
It should be a decision system.
Written information prepares the room. Clear issues focus the discussion. Authority closes the decision. A durable record protects the commitment. Follow-through turns the meeting into operating progress.
A meeting that only reports status transfers information.
A leadership team should leave having changed what the company will do.
Sources and notes
- Gino Wickman, Traction, on recurring leadership reviews, issue identification, prioritization, decision closure, and the relationship between measures and operating action. Reference does not imply affiliation, certification, or licensed use of a branded framework.
- Gino Wickman and Mike Paton, Get a Grip, on prioritizing root issues, avoiding endless discussion, and making decisions with clear ownership.
- Jack Stack and Bo Burlingham, The Great Game of Business, on recurring operating rhythms that connect numbers, forecasts, communication, and action.
- Simon Sinek, The Infinite Game, on trusting teams, truthful reporting, and the need for leaders to model the behavior required for useful information to surface.
