What Should a Weekly Leadership Meeting Agenda Include?
Your leadership meeting could have been a decision.
A weekly leadership meeting agenda should cover prior commitments, changed priorities, unresolved decisions, and follow-through. Move routine status updates into a pre-read. Use the meeting to resolve tradeoffs with the people who have authority to decide, then record the next action, owner, due date, and affected teams.
A calendar full of leaders is not an operating result. Build the agenda around the choices that need those leaders, then check what changed after the room emptied.
Weekly leadership briefThe launch has two plans
Sales is preparing the announcement. Engineering is protecting reliability work.
- Missing decision
- Which work takes priority?
- Decision maker
- Authorized executive
- Follow-up
- Product revises scope; Sales checks promises
The brief brings the tradeoff into the room. People make the call.
How should you structure a 50-minute leadership meeting agenda?
In this suggested 50-minute leadership meeting, spend 25 minutes on decisions. Use the rest to check commitments, compare changed priorities, and confirm follow-through. Treat the timings as a starting format, not a benchmark; adapt them to the decisions your company needs to make.
| Time | Discussion | Required output |
|---|---|---|
| 0–5 minutes | Check previous commitments | Completed, changed, or escalated, with evidence |
| 5–15 minutes | Review changed priorities and conflicting assumptions | A shared statement of what changed and what stops |
| 15–40 minutes | Resolve the most consequential missing decisions | Decision, decision maker, reason, and effective date |
| 40–50 minutes | Confirm owners and communicate the outcome | Next action, owner, due date, and affected teams |
The COO or Chief of Staff prepares the decision queue, not a speaking slot for every department. Give each issue a presenter and bring the specialist who knows the constraint. If the right evidence or authority is missing, name that before the meeting starts.
Keep the attendee list tied to authority and context: who can decide, who knows the constraint, and who must carry out the result? Attendance alone does not give someone decision authority.
What belongs in a leadership meeting pre-read?
Ask each function for changes that affect a company priority or another team. Use the same fields so the organizer can compare the answers. Share the pre-read early enough for leaders to challenge missing evidence before the meeting.
Copy this block for each proposed discussion:
Company priority:
What changed since the last review:
Evidence and date observed:
Where another team's understanding differs:
Decision requested, in one sentence:
Options and recommendation:
Who has authority to decide:
Latest useful decision date and why:
Work affected if the decision waits:An item without a decision request may still deserve attention. Label it as information, investigation, or a risk to watch. Don't disguise an update as a decision just to get it into the room.
Put the conflicting versions of the plan next to each other.
Suppose Sales expects to announce a new onboarding flow next month. Product believes onboarding is still the main priority. Engineering has moved its available capacity to a reliability issue after a separate discussion with the CEO.
Each function can give an accurate update about its own work. The meeting becomes useful when someone names the conflict: is onboarding still first, or has reliability displaced it?
The decision request is not “Can Engineering provide an update?” It is “Which work takes priority this week, and what customer commitment changes as a result?” Engineering brings the reliability evidence. Sales explains the commitment already made. The authorized executive makes the tradeoff.
Record the result in plain language:
| Question | Decision | Action owner | Due | Who needs to know |
|---|---|---|---|---|
| Which work comes first? | Reliability work comes first; onboarding scope will be revised | Product lead | Thursday | Sales and Customer Success |
| What happens to the customer announcement? | Hold it until revised scope is confirmed | Sales lead | Today | Account owners and Marketing |
The decision is only useful if it changes the scope, the customer message, or the next commitment. Record that change alongside the call.
What should happen when a decision cannot be made?
If the room lacks evidence, assign the investigation and its return date. If it lacks authority, name the decision maker and route the question to them. If the item is lower priority, record the deferral and the condition that would bring it back.
“Discuss next week” is incomplete. “Product will compare the two implementation options by Wednesday; the COO will decide on Thursday” tells people what happens next.
Use a separate working session for detailed design. The leadership meeting should decide the constraint or tradeoff that lets that session proceed. It should not redesign the entire onboarding flow while unrelated leaders wait.
The decision needs to leave the room.
Read the decisions back before people leave. Ask each action owner to state the next step in their own words. Then check who outside the room is still acting on the earlier plan.
At the next review, start with evidence of follow-through: an updated customer message, a changed roadmap item, or a confirmed handoff. A decision marked “communicated” is not proof that the affected team changed its work.
This agenda is deliberately separate from a full operating review. The meeting format organizes leadership time; the operating review supplies business evidence and exceptions. You can use the same meeting for both, provided the pre-read does the reporting work first.
What is Decided?
Decided is an AI operating alignment layer for fast-moving SaaS companies. Clara runs recurring private 1:1 AI voice check-ins about priorities, blockers, decisions, and commitments. Decided compares the answers and prepares an alignment map, a weekly leadership brief, and context for follow-up.
The brief brings the tradeoff into the room. People make the call.
People review the context and make the decisions. Before rollout, explain what is captured, who sees the output, how it is used, and whether participants can review notes. Private 1:1 describes the format, not anonymity. Decided is not hidden monitoring, employee scoring, or an automated employment decision system.
Explore Decided for Chiefs of Staff. Try a live voice check-in to see how it works.
Sources.
Asana's L10 meeting template provides a structured approach to issues and follow-up. Atlassian's DACI play distinguishes the people preparing a decision from the person authorized to make it.
