A weekly leadership meeting is useful when it helps the team make decisions that require more than one function and review commitments that affect shared outcomes. It should not become the only place anyone can obtain a status update. Move routine information into an approved shared record so meeting time can focus on what needs leadership attention.
This illustrative 45-minute agenda is designed for an operating leadership team. Adapt it to your cadence, complexity and existing governance. The time boxes are prompts for focus, not evidence that every decision should be rushed into a weekly slot. Execution Is a Leadership Discipline explains why the review of actual commitments matters.
Before the meeting: submit decisions, not surprise presentations
Each leader updates the status of their prior commitments and identifies any item needing the group. A useful request states the decision needed, why it matters now, the relevant evidence, options, affected teams and the authorized owner. Keep confidential information in approved channels. A slide deck is optional; a clear decision request is not.
The facilitator separates routine updates, decisions and problems that need deeper investigation. Invite the necessary decision-maker or acknowledge that the group can only make a recommendation. Share the agenda before the meeting, including what is out of scope. An item does not become urgent merely because it was submitted late.
Minutes 0–10: review commitments and exceptions
Begin with the outcomes the team previously agreed, not a full recital of each department's activity. For an incomplete commitment, establish its current state, consequence and next action. Distinguish a changed business priority from a forgotten obligation. Reconfirm or change the commitment explicitly rather than letting it vanish between agendas.
Use a small record with owner, agreed result, review point and actual evidence. A green label needs a meaning: delivered, accepted by the receiving team, or simply started are different states. Leadership accountability depends on an understood agreement, not a color-coded impression.
Minutes 10–30: address the decisions needing the team
Take the highest-consequence decision first. The owner states the question and evidence; affected leaders explain constraints and consequences. Decide within the right authority or record the specific missing input and who will obtain it. If the issue needs root-cause investigation, define that work instead of guessing a solution to finish the agenda.
Record a decision as something a receiving team can use: the choice, owner, applicable boundaries, affected commitments and communication step. 'We discussed capacity' is not a decision. 'The authorized owner will confirm the permitted priority after receiving the missing capacity evidence' is an unresolved item with a usable next action.
Minutes 30–40: resolve dependencies and capacity conflicts
Check where one leader's commitment depends on another team's input or resources. Name the receiving need and the supplying owner. If two priorities compete for the same capacity, the appropriate leader must choose what takes precedence or explain what evidence is needed. Do not assign every item first priority.
For example, a fictional team may agree that a planning record cannot be finalized until a designated owner confirms an unresolved customer requirement. The dependency is recorded against both commitments. The meeting does not authorize bypassing that requirement; it makes the missing decision and its effect visible.
How should the team retire a commitment it can no longer support?
Retiring a commitment is a leadership decision, not an unexplained disappearance from the next agenda. Name the affected outcome, the reason for reconsidering it and the authorized owner who can change it. The priority review helps distinguish continue, pause, stop and investigate decisions without pretending that every request still fits the same capacity.
In a fictional planning review, stopping one initiative also removes an input another team expected. Before closing the item, agree the revised dependency, who tells the receiving team and what remains owed. The change-communication plan supports that explanation and a check of understanding. A clean meeting record is not the outcome if people outside the room are still working against the old commitment.
Minutes 40–45: close with a read-back
Read the decisions, new commitments, changed priorities and remaining questions. Each owner confirms what they will do and when the team will review the evidence. Identify who communicates the decision to people who were not in the room. A meeting note without a communication owner can leave the operating teams following yesterday's priorities.
Keep a stable decision record rather than issuing a new competing version every week. If the facilitator is absent, use an agreed alternate. If a required decision-maker is absent, do not treat the meeting's preference as approval. The cadence supports governance; it does not replace it.
Check whether the meeting is doing useful work
After several cycles, examine commitments repeatedly carried forward, decisions reopened and dependencies discovered too late. Ask whether the issue is an unclear request, unavailable authority, unrealistic capacity or weak follow-through. Shorter meetings alone are not the goal; neither is a perfect completion count achieved by making trivial commitments.
Remove information-only items that can be read beforehand, but preserve time for questions that reveal a real constraint. If the meeting repeatedly revisits the same unresolved priority, discuss the leadership operating system rather than increasing the frequency of status reporting.
About this resource: Prepared with AI-assisted drafting. Timing and examples are illustrative, not a guaranteed meeting method or a record of client results. Cover illustration: AI-generated.