A meeting is a commitment
A management meeting earns its place when it changes the work. Attendance alone proves very little. A room can be full while overdue actions remain untouched, risks stay unnamed and decisions wait for another committee. The useful question is whether the routine makes a problem visible soon enough for someone to act on it.
My starting point is to protect one operating review. It should happen at a predictable time, use the same decision structure and finish with commitments the team can explain. That creates a reference point for the operation. People know where a concern belongs, when it will be considered and how an unresolved issue moves forward.
Three pressure tests
The first test is absence. If the senior leader cannot attend, can the team still hold the review and make decisions within its authority? A deputy chair and explicit decision rights make the answer practical. Issues beyond that authority need an escalation route; the entire meeting does not need to wait for an executive diary.
The second test is an apparently empty agenda. The routine should still examine the current work, commitments and emerging risks. It may finish early when there is little to discuss. The purpose is reliable attention, not filling the allotted time. A recurring meeting that regularly finds no decisions or useful checks should have its scope reconsidered.
The third test is attendance. Repeated absence should prompt a conversation about responsibility and usefulness. It may reveal that a necessary owner is disengaged, that the meeting excludes the right people, or that participants have no real role. These are different problems. Treating each as a discipline issue misses the opportunity to improve the routine.
Build an agenda from the work
A daily review can move through safety, yesterday's performance, today's priorities, the most consequential current problem and the next action. A weekly review can examine patterns, recurring constraints and whether countermeasures worked. Keep the levels connected. Daily meetings should not become miniature strategy sessions, and weekly meetings should not repeat every operational update.
Use the board as the agenda. Put the expected condition beside the actual condition. Record the gap in language that describes the work, then assign a next step to someone who can carry it out. Include a date and the evidence needed to close it. “Investigate quality” is vague. “Check where the defect first appears and bring observations to the next review” creates a concrete task.
Do not try to solve every technical problem during the review. Decide which problem needs attention, agree the next investigation and arrange the right people outside the meeting. This protects everyone's time while preserving accountability. A short review depends on preparation in the work, not on a polished presentation.
Judge the routine by its consequences
After several cycles, examine what the cadence has produced. Are old actions closing? Are teams raising difficulties earlier? Can an owner explain what changed after a decision? Are escalations receiving answers? These observations show whether the routine supports execution or merely reports activity.
During a crisis, adapt the review to the situation and preserve its decision function. Make priorities explicit, shorten what can be shortened and record what is deferred. The aim is a management system that remains useful under pressure. Protecting the cadence means protecting the moment when the team sees reality, chooses its next move and accepts responsibility for it.