Skip to article

Leadership team meeting agenda: template and how to run it

A 75-minute leadership team meeting agenda template with a filled example, what belongs on it, and how to run notes, AI notetakers and follow-ups.

Leadership Team Meeting Agenda: A Chief of Staff's Guide
Short answer

A weekly leadership team meeting agenda runs about 75 minutes in a fixed order: late actions (5 minutes), red metrics (10), two decisions and one issue (50), a read-back of decisions, owners and dates (5), and what to tell the company (5). Updates go in writing the day before. The CEO chairs, and the Chief of Staff owns the agenda.

Key takeaways
  • Give a decision slot only to an item written as a choice, with one owner and a one-page pre-read. Anything without a pre-read waits a week.
  • Route every other request before the agenda goes out: updates to writing, one-function calls to their owner, long strategy questions to the next deep dive.
  • Send the decisions, owners and dates within two hours of the meeting, and ask anyone who heard something different to reply within 24 hours.
  • Agree your AI notetaker rules before the first bot joins: one approved tool, consent, topics never recorded, who reads transcripts and when they're deleted.
  • Make the case for change in hours. Ten leaders in a 90-minute weekly meeting spend 15 executive hours there. Run it in 75 minutes, with status in writing, and they get 2.5 hours back every week.

Most leadership meetings fail the same way. Leaders take turns reading updates the room could have read the day before, and the one decision that needed everyone starts with ten minutes left. Fixing that is hard when everyone in the meeting outranks you, so the change has to come through the agenda you control.

If you're the CEO, you chair the meeting and make the calls. You have five other jobs:

  • Agree the agenda with your Chief of Staff in your Monday 1:1.
  • Hold the rule that an item without a pre-read waits a week.
  • At the read-back, ask of each decision: "Is anyone not able to commit to this?"
  • Ask in the meeting about any action that's late twice.
  • Reply briefly to a few written updates each week, so leaders' work stays visible.

What should a weekly leadership team meeting agenda include?

A weekly leadership team meeting agenda needs five parts: last week's late actions, metrics shown by exception, the decisions and issues that need the whole group, a read-back of what was decided, and what the company will hear. Everything else, including department updates, goes in writing before the meeting.

This 75-minute version suits a company of 50 to 500 people. The Example tab fills it in for a 140-person company, and the worked example further down shows why each item made the cut.

Template: Weekly leadership meeting agenda with agenda requests

Leadership team meeting · [Day, date] · [time, length]

Chair: [CEO] · Agenda and notes: [Chief of Staff] · Pre-reads: [link to folder]

Agenda requests (submit by [day, time] for this meeting)

Format: item · decide / discuss / inform · owner · minutes needed · pre-read link

Rule: no pre-read, no agenda slot. Inform-only items go in the written update.

Run of show

TimeItemTypeOwnerPre-read
0:00Open actions: late or blocked onlyInformChief of StaffAction list
0:05Metrics: reds and big moves onlyDiscussEach ownerScorecard
0:15Decision 1: [question as a choice]Decide[owner][link]
0:30Decision 2: [question as a choice]Decide[owner][link]
0:50Issue: [topic]Discuss[owner][link]
1:05Read-back: decisions, owners, datesDecideChief of Staff
1:10What we tell the company, and who tells itDecideCEO

Parked for next week

  • [item] · reason · new date
# Leadership team meeting · [Day, date] · [time, length]
Chair: [CEO] · Agenda and notes: [Chief of Staff] · Pre-reads: [link to folder]

## Agenda requests (submit by [day, time] for this meeting)
Format: item · decide / discuss / inform · owner · minutes needed · pre-read link

Rule: no pre-read, no agenda slot. Inform-only items go in the written update.

## Run of show
| Time | Item | Type | Owner | Pre-read |
| --- | --- | --- | --- | --- |
| 0:00 | Open actions: late or blocked only | Inform | Chief of Staff | Action list |
| 0:05 | Metrics: reds and big moves only | Discuss | Each owner | Scorecard |
| 0:15 | Decision 1: [question as a choice] | Decide | [owner] | [link] |
| 0:30 | Decision 2: [question as a choice] | Decide | [owner] | [link] |
| 0:50 | Issue: [topic] | Discuss | [owner] | [link] |
| 1:05 | Read-back: decisions, owners, dates | Decide | Chief of Staff | |
| 1:10 | What we tell the company, and who tells it | Decide | CEO | |

## Parked for next week
- [item] · reason · new date

Example: Leadership meeting agenda for a 140-person company (illustration)

Leadership team meeting · Tue, July 7 · 10:00, 75 min

Chair: CEO · Agenda and notes: Chief of Staff · Pre-reads: Leadership folder, July 7

Agenda requests (closed Thursday, 3pm)

Five requests came in. Two made the agenda, two are parked and one went to the written update.

Run of show

TimeItemTypeOwnerPre-read
0:00Open actions: two late, one blockedInformChief of StaffAction list
0:05Metrics: reds and big moves onlyDiscussEach ownerScorecard
0:15Decision 1: pause the two open backend roles for the quarter, or keep hiring?DecideVP EngineeringHiring plan memo
0:30Decision 2: sign a second office lease, or extend the current one a year?DecideCOOLease options memo
0:50Issue: net revenue retention down three pointsDiscussVP Customer SuccessRetention analysis
1:05Read-back: decisions, owners, datesDecideChief of Staff
1:10What we tell the company, and who tells itDecideCEO

Parked for next week

  • Q3 renewal pricing · needs more than one decision slot · revenue deep dive, July 16
  • Retire the reports feature · no pre-read yet · back to its owner with the questions it must answer
# Leadership team meeting · Tue, July 7 · 10:00, 75 min
Chair: CEO · Agenda and notes: Chief of Staff · Pre-reads: Leadership folder, July 7

## Agenda requests (closed Thursday, 3pm)
Five requests came in. Two made the agenda, two are parked and one went to the written update.

## Run of show
| Time | Item | Type | Owner | Pre-read |
| --- | --- | --- | --- | --- |
| 0:00 | Open actions: two late, one blocked | Inform | Chief of Staff | Action list |
| 0:05 | Metrics: reds and big moves only | Discuss | Each owner | Scorecard |
| 0:15 | Decision 1: pause the two open backend roles for the quarter, or keep hiring? | Decide | VP Engineering | Hiring plan memo |
| 0:30 | Decision 2: sign a second office lease, or extend the current one a year? | Decide | COO | Lease options memo |
| 0:50 | Issue: net revenue retention down three points | Discuss | VP Customer Success | Retention analysis |
| 1:05 | Read-back: decisions, owners, dates | Decide | Chief of Staff | |
| 1:10 | What we tell the company, and who tells it | Decide | CEO | |

## Parked for next week
- Q3 renewal pricing · needs more than one decision slot · revenue deep dive, July 16
- Retire the reports feature · no pre-read yet · back to its owner with the questions it must answer

Why this order works

Updates are easy to prepare and safe to give, while decisions put the owner's judgment on display. Left alone, the safe items fill the room first, and the decision everyone came for starts at minute 70 of 90. The order above gives late actions and metrics 15 minutes at most. Decisions then get minutes 15 to 50, while people are still fresh.

The second problem is mixing tactics with strategy. Dora Nagy, a former Chief of Staff to the COO at SoftBank, splits the two. A Monday meeting covers KPIs, OKR status, priorities and issues. A separate weekly deep dive rotates through the six to eight strategic topics that matter most, so each comes back every five or six weeks and people know when to prepare. When both share one slot, she said, the meeting can spend its time on a topic that matters to only three of the ten people in the room.

Alexis Summit, then Chief of Staff at Kroll, kept the monthly agenda for its service line leaders predictable on purpose, so they knew what to report: performance, people, and the sales opportunities others could help with.

A 75-minute leadership meeting, minute by minute

The scorecard and written updates go out the day before, so the room looks only at what's late, red or moved sharply. Decisions and one issue get 50 of the 75 minutes.

Open actions · 5 min

Metrics · 10 min

Decision 1 · 15 min

Decision 2 · 20 min

Issue · 15 min

Read-back · 5 min

What we tell the company · 5 min

0:000:150:300:451:001:15
DecideDiscussInform
Source: Chief of Staff Network, leadership team meeting guide (2026)

What topics belong on a leadership team meeting agenda?

The purpose of a leadership team meeting is to make the decisions and solve the problems that need the whole team. A topic belongs on the agenda when it needs more than one leader's agreement or budget, when only the CEO can make or back the call, or when every leader must hear it at the same time.

Topics that usually pass: a hiring pause or a new role, budget moved between teams, a price change, a launch date, an office or lease decision, a reorganization, a large customer at risk, and next quarter's priorities.

Use these rules to route the agenda requests before you build the draft:

  • Department updates and progress on plan go in the written update the day before.
  • Metrics on plan stay on the scorecard. A red metric, or one that moved past your agreed threshold, gets the metrics slot.
  • A decision that crosses functions or changes budget, headcount or a company priority gets a decision slot and a pre-read.
  • A decision that stays inside one function and its approved budget goes to that function's owner, who notes it in the written update.
  • A concern about one leader's performance goes to the CEO's 1:1 with that leader.
  • A strategic question that needs more than one decision slot goes to the next deep dive or the quarterly review, which our operating rhythm guide sets up.
  • Wins and customer stories go in the written update, where the CEO can reply to them.
  • Anything the whole company must hear goes to the last slot, with the name of the person who tells it.

Then check the finished draft against the company's top priorities. Every item should connect to one of them, and an item that connects to none is usually a department update that found its way in.

A worked example (illustration): building one week's agenda

Say you support the CEO of a 140-person software company with nine leaders and a 75-minute Tuesday meeting. On Thursday afternoon your decision queue holds five items:

  1. Pause two open engineering roles for a quarter? Needed by July 10. Pre-read ready.
  2. Raise renewal prices in Q3? Needed in three weeks. Pre-read half written.
  3. Sign a second office lease? Needed in two weeks. Pre-read ready.
  4. Retire an underused product feature? No date, no pre-read.
  5. Offsite dates. Inform only.

Items 1 and 3 become the two decisions, because both have a date and a pre-read. Pricing needs more than one decision slot, so it goes to the next revenue deep dive. The feature item goes back to its owner with a note on what the pre-read needs to answer, and offsite dates go in the written update. Net revenue retention is down three points, so that takes the issue slot. On Monday you agree the draft with your CEO in your 1:1, and it goes out with the pre-reads straight after, 24 hours before the meeting.

Five items came in and two reached the room. Filtering the queue before anyone walks in is most of what a Chief of Staff adds to this meeting.

Five requests, two decision slots. Pausing two engineering roles and signing a second office lease have a date and a pre-read: decisions 1 and 2. Renewal prices go to a deep dive, a feature to its owner, offsite dates to the update.

Judgment calls on the agenda

The first call is one meeting or two. Under about 30 people, one weekly meeting with a strategic item at the end is enough. Once the same strategic topic has overrun the weekly meeting twice in a month, split out a deep dive. I'd rather add one focused meeting than let a 90-minute meeting grow to two hours.

The second is the size of the queue. If more than three items need the whole team every week, the team is deciding things one owner could decide with a heads-up, so ask your CEO which items could be delegated with a rule, such as "spend under $50,000 inside an approved budget goes to the functional lead". In a week when the queue holds no decision, run a short meeting on late actions and red metrics, or cancel it.

The third is what counts as an exception. Agree thresholds once, such as red means more than 10% off plan, and print them on the scorecard. Without them, every leader explains every number.

Adjust for size and setup. A founding team under 30 can run 45 minutes with no metrics section; at 500 people and up, "what we tell the company" becomes a cascade note each leader takes to their own staff meeting. Remote teams should type the read-back into the meeting chat. A functional Chief of Staff runs the same meeting for their principal's staff, plus a standing slot for what the function needs from the company's leadership meeting.

Moving updates into writing has a political cost: leaders who used update time to show the CEO their work lose that stage. Hold the line with one rule your CEO agrees to in advance: if it isn't in the pre-read, it doesn't get airtime. A short reply from the CEO on a few written updates each week keeps the work visible. When the CEO breaks the rule with a last-minute item, let it go ahead, have its owner send the one-pager the same day, and raise the pattern in your 1:1 if it becomes weekly.

You can also give the work a slot of its own. In an operating-rhythm plan a Chief of Staff shared with our community, half of a weekly leadership hour went to two 15-minute presentations from people below the leadership team, which put rising leaders in front of the executives. To fit it into the 75-minute agenda, give one presentation the issue slot every other week.

This week, take last week's agenda and mark each item as decide, discuss or inform. Count the minutes that went to inform: that number is your case for the change.

What is an L10 or huddle meeting, and do you need one?

An L10 (Level 10) meeting is a weekly 90-minute leadership meeting format from EOS, the Entrepreneurial Operating System. Each attendee rates the meeting from 1 to 10 at the close, and the aim is a 10. It runs at the same time every week in a fixed order, with short reviews of metrics, priorities and to-dos, then most of the time on solving issues, a step often shortened to IDS: identify, discuss, solve.

A huddle is a 10 to 15 minute check-in, daily or a few times a week, for a launch, a crisis or a fast sales quarter. Keep it to three lines: what's blocked, who can unblock it, and by when. I'd only start a daily huddle with an end date, so it doesn't outlive the reason for it.

If your company already runs on EOS, use the L10 as designed and put your energy into the issues list. If it doesn't, borrow the two strongest habits: a fixed time and order every week, and most of the meeting spent on issues.

Whatever you adopt, introduce it slowly. Ryan Kelly, the first Chief of Staff at Veremark, presented a full set of weekly, monthly and quarterly meetings at one of his first leadership meetings, and the CTO rejected it in front of the room. On reflection, it put too much governance into the same week for how fast the business moved. His advice: learn the business before you apply a template.

Before you change a leadership meeting's format, walk the plan through with each leader one to one, starting with the one most likely to object.

Who runs the leadership meeting, and what does the Chief of Staff own?

The CEO chairs the leadership meeting. The Chief of Staff owns everything around it: the agenda, the pre-reads, the timekeeping, the record of decisions and the follow-ups. In some companies the Chief of Staff also facilitates while the CEO participates as a decision maker.

17% of Chief of Staff job postings name leadership team management directly, and 61% ask for OKRs, KPIs or the operating rhythm.

Whoever chairs can end a discussion and make the call. If a Chief of Staff chairs, leaders read it as the CEO stepping back, and hard decisions drift to side conversations. Owning the agenda gives you more influence anyway, because you decide what reaches the room and in what order. I'd stay out of the chair even when the CEO offers it.

Once leaders see that the agenda decides what gets the CEO's attention, they'll lobby you for slots. Make the rules public: requests by a set day, a one-line description of the decision needed, and a pre-read before it's scheduled. Put the agenda calls you can make alone in your mandate. Agree the others with your principal, as Alexis Summit did with her two principals at Kroll, so a no comes from both of you.

In a company of 50 to 500 people, the meetings around the leadership team usually split like this. Treat the table as our recommendation and adjust it for yours.

The meetings a Chief of Staff runs or prepares

MeetingLength and frequencyChairChief of Staff's jobInputsOutput
Leadership team meeting75 min, weekly (Tuesday)CEOAgenda, pre-reads, timekeeping, notes, follow-upsWritten updates, scorecard, decision pre-readsDecisions with owners and dates
1:1 with your principal30 to 45 min, weekly (Monday)PrincipalBrings decisions and risks, takes actionsYour Friday weekly updateThis week's priorities, Tuesday's agreed agenda, answers
Huddle10 to 15 min, daily or 2 to 3 times a weekTeam lead or CEOKeeps it to blockers onlyShared blocker listUnblocked work
Monthly business review2 to 3 hours, monthlyCEOBuilds the pack, runs the agendaFunction reviews against planCourse corrections, escalations
Quarterly planning or reviewHalf day to a day, quarterlyCEODesigns the session, owns pre-readsResults vs plan, proposed prioritiesNext quarter's priorities and owners
Offsite1 to 2 days, once or twice a yearCEODesigns the agenda and outcomes, handles the logistics or hands them offStrategy questions, prior commitmentsDecisions, a plan, a shared story

Your 1:1 with your principal makes the others work. Use Monday's 1:1 to agree Tuesday's agenda before it goes out, so the CEO is never surprised in the room. Move status into your weekly update to make that room. Our operating rhythm guide has templates for the weekly business review and the quarterly business review pre-read. For offsites, read our post on mastering offsites.

How do you prepare a leadership meeting without becoming the bottleneck?

Prepare on the same days every week, and send the agenda and pre-reads 24 hours before the meeting. When everyone knows the deadlines, you stop chasing people one by one. For a Tuesday meeting:

  • Thursday: agenda requests close.
  • Friday: chase missing pre-reads, two working days out, and send your principal your weekly update.
  • Monday: agree the draft agenda with your principal in your 1:1, then send the agenda, pre-reads, scorecard and written updates.
  • Tuesday: run the meeting, and send decisions, owners and dates within two hours. Corrections come back within 24 hours.

The core of preparation is a decision queue: a running list of decisions waiting for the leadership team, each with an owner, a date needed and whether the pre-read exists. Urgent items that come up mid-week go into the queue with a date, and each agenda is the top of the queue. That keeps the meeting from being set by whoever shouts loudest.

A good pre-read is one page: the decision needed in one sentence, the options with a recommendation, the trade-offs and who was consulted. If a leader can't write one page, the item usually isn't ready; send it back with a note on what's missing. Our decision-making post covers framing the decision, and our briefing guide has a pre-read template.

Have owners write and send their own pre-reads to a shared folder, and check only that they arrived and are one page. If every pre-read passes through your hands, every late one becomes your fault, and writing them for leaders teaches them to stop. Once the agenda is out, resist changing it in the room: the chair decides whether a new item bumps something or goes to next week's queue.

How do you take notes and decide what to record?

Record decisions, owners and dates for every leadership meeting, with a short note of the reasoning behind each decision. Full recordings and transcripts should be the exception, agreed by the group in advance, with rules on who can access them and when they're deleted. I'd default to notes and a decision record, and record only when the group asks for it.

A transcript of 75 minutes of senior people thinking out loud is a permanent record of half-formed views, disagreements and comments about people. Leaders who know every word is captured speak more carefully, and the candid disagreement the meeting exists for moves to private messages.

AI notetakers make this urgent, because they arrive one person at a time. At Veremark, note-takers multiplied in meetings. The company asked everyone to stick to the Google recording and transcription it already used, and Ryan Kelly said one source is more secure.

In our Chief of AI Report, security, compliance and ethics were the most common concern about adopting AI, at about 41% of responses. One CTO described stopping AI use in internal strategy meetings for that reason. A leadership meeting covers deals, people decisions and numbers that aren't public, so it is the meeting most likely to cross a line.

Before any notetaker joins your leadership meeting, agree five rules with your principal and your legal or security lead:

  1. Which tool, and only that one. One approved tool, under the company's account.
  2. Consent. Everyone in the meeting knows it's running and can ask for it to be paused. Recording consent laws vary by state and country, so check with your legal team before recording anyone outside the company.
  3. Never-record topics. Discuss these with recording paused, and let the notes say only that the topic was covered: people decisions and performance, compensation, health or personal matters, legal matters and disputes, and anything under NDA or not yet public, such as deals and board matters.
  4. Access. Who can read the full transcript, and who sees only the summary.
  5. Retention. How long transcripts are kept before deletion, set with your legal team. In the UK and EU, a transcript that identifies speakers holds personal data under the GDPR (the UK GDPR in Britain), so access and retention rules carry legal weight there.

Once three tools are running, every rule becomes a negotiation with someone's habit.

Maria Mejia, a Chief of Staff we spoke with on our podcast, said her team used an AI meeting companion for meetings of an hour or more, for the summary and the action items. Check every decision and owner in that summary before it goes out, because a summary that records a decision nobody made does more damage than no notes. Our AI setup guide covers connecting an approved notetaker to your other tools.

Template: Meeting notes and decisions

Leadership team meeting notes · [date]

Present: [names] · Absent: [names, and who briefs them] · Notes: [name]

Decisions

DecisionOwnerBy whenWho needs to knowCan be reopened if
[what we decided, in one sentence][name][date][teams, people][new information that would change it]

Actions

ActionOwnerDue
[verb + outcome][name][date]

Still open

  • [topic] · next step · back on the agenda on [date]

What we tell the company

  • [message] · sent by [name] · by [date]

Notes-off topics

  • [topic covered; no detail recorded]
# Leadership team meeting notes · [date]
Present: [names] · Absent: [names, and who briefs them] · Notes: [name]

## Decisions
| Decision | Owner | By when | Who needs to know | Can be reopened if |
| --- | --- | --- | --- | --- |
| [what we decided, in one sentence] | [name] | [date] | [teams, people] | [new information that would change it] |

## Actions
| Action | Owner | Due |
| --- | --- | --- |
| [verb + outcome] | [name] | [date] |

## Still open
- [topic] · next step · back on the agenda on [date]

## What we tell the company
- [message] · sent by [name] · by [date]

## Notes-off topics
- [topic covered; no detail recorded]

Example: Leadership meeting notes for a 140-person company (illustration)

Leadership team meeting notes · July 7

Present: CEO and eight leaders · Absent: VP Marketing (Chief of Staff briefs her) · Notes: Chief of Staff

Decisions

DecisionOwnerBy whenWho needs to knowCan be reopened if
Pause the two open backend roles until October 1VP EngineeringJuly 8Recruiting, hiring managers, financeQ3 bookings come in above plan
Extend the current office lease by one year; no second officeCOOJuly 31All staff, financeThe headcount plan changes

Actions

ActionOwnerDue
Tell recruiting and both hiring managers about the pauseVP EngineeringJuly 8
Update the hiring forecast for the pauseVP FinanceJuly 10
Bring a one-page retention planVP Customer SuccessJuly 13

Still open

  • Net revenue retention · VP Customer Success brings causes and a plan · back on the agenda July 14

What we tell the company

  • We're staying in our current office next year · CEO · Thursday all-hands

Notes-off topics

  • One senior hire discussed; no detail recorded
# Leadership team meeting notes · July 7
Present: CEO and eight leaders · Absent: VP Marketing (Chief of Staff briefs her) · Notes: Chief of Staff

## Decisions
| Decision | Owner | By when | Who needs to know | Can be reopened if |
| --- | --- | --- | --- | --- |
| Pause the two open backend roles until October 1 | VP Engineering | July 8 | Recruiting, hiring managers, finance | Q3 bookings come in above plan |
| Extend the current office lease by one year; no second office | COO | July 31 | All staff, finance | The headcount plan changes |

## Actions
| Action | Owner | Due |
| --- | --- | --- |
| Tell recruiting and both hiring managers about the pause | VP Engineering | July 8 |
| Update the hiring forecast for the pause | VP Finance | July 10 |
| Bring a one-page retention plan | VP Customer Success | July 13 |

## Still open
- Net revenue retention · VP Customer Success brings causes and a plan · back on the agenda July 14

## What we tell the company
- We're staying in our current office next year · CEO · Thursday all-hands

## Notes-off topics
- One senior hire discussed; no detail recorded

How do you make follow-ups actually happen?

Make follow-ups happen with three habits: send the decisions and actions within two hours of the meeting, keep one action list that every meeting reads from, and open the next meeting by reviewing only the actions that are late. Owners then hear about their commitments from a list, on a schedule, without you chasing them individually.

Actions die for predictable reasons: the room agreed a direction but never an owner or a date, ownership spread across "we'll look into it", or nothing brought the action back before its deadline. The follow-up email tests whether the decision was real. Sent within two hours, it gets corrected while people remember the meeting. Sent three days later, it gets ignored or reopens the debate. Ask people to reply within 24 hours if anything is wrong.

Template: Follow-up email after a leadership meeting

Subject: Leadership meeting [date]: decisions and actions

Hi all,

Decisions from today. Reply by [time tomorrow] if anything here doesn't match what you heard.

Decisions
1. [Decision in one sentence]. Owner: [name]. By: [date].
2. [Decision in one sentence]. Owner: [name]. By: [date].

Actions
- [Name]: [action], by [date]
- [Name]: [action], by [date]

Still open
- [Topic]: back on the agenda [date]. [Name] brings a one-page pre-read.

Telling the company
- [Name] sends [message] to [audience] by [date].

Full notes and pre-reads: [link]

[Your name]

Keep a single action list for the leadership team, in whatever tool the team already opens every day, with an owner and a date on every line. Decisions go in a separate log that records what was decided and why; our guide to managing context has a template for it. Then open each meeting with late and blocked actions only, because reading the whole list teaches people it's a formality.

The risk for you is becoming the team's nag. Once your name is on every reminder, leaders treat a late action as a disagreement with you. Ask your CEO to own the consequence: when an action is late twice, the CEO asks about it in the meeting. If your CEO won't, report the on-time rate monthly in your weekly update and let the number raise it.

A worked example: one decision over three weeks

Back to the 140-person company. On Tuesday the team decides to pause two engineering roles. The read-back says: "Pause the two backend roles until October 1. Owner: VP Engineering. Recruiting and both hiring managers told by Wednesday."

By noon you send the follow-up. By 2pm the VP Finance replies that she heard "pause for the rest of the year", and her forecast assumes that. The VP Engineering confirms October 1, and you correct the log before anyone acts.

At the next Tuesday meeting, the action is on the late list: recruiting hasn't been told. You ask the VP Engineering one to one afterward and learn he was waiting for the CEO to call a candidate with a final interview booked, a dependency nobody wrote down. You add a line for the CEO, dated Thursday, and both actions close by Friday. In week three the item does not reach the late list.

When an action is late, find out why first

A late action usually means one of three things. Ask the owner one question: "What would done look like, and when can you get there?"

If they answer quickly with a new date, it's capacity. Re-date it once, and if it slips again, take it to the CEO to reassign or drop something else. If they hesitate or argue about the action itself, they never agreed with the decision; put it back on the agenda as a decision, with their objection in the pre-read. If they can't describe done, the action was badly written, so rewrite it with them as a verb, an outcome and a date.

One question for a late action: what would done look like, and when can you get there? A quick new date means capacity: re-date once. Hesitation means disagreement: back on the agenda as a decision. No description of done means it was badly written.

I'd watch hardest for treating disagreement like capacity. Chasing someone who disagrees produces a late action every week and a worse relationship with you, while the disagreement never gets discussed.

Once a month, close or re-date anything older than six weeks, because old lines teach people the list isn't real. In a larger company, tag the actions each leader needs to cascade so their teams hear decisions from their own leader first; our post on strategic communication covers writing those messages.

How do you turn a meeting transcript into decisions and actions?

Have the approved tool draft the decisions and actions, then check the draft against your own notes before anything is sent. The tool is fast at finding who said they'd do what and unreliable at telling a decision from a suggestion, so the prompt makes it say when it isn't sure. Use it only on meetings where everyone agreed to the transcript.

Our guide to AI for Chiefs of Staff covers which tools to approve and what data can go into them.

Prompt: Turn this meeting transcript into decisions and actions

You are helping a Chief of Staff write up a leadership team meeting.

Below is the transcript of the meeting and my own notes. Produce:

1. Decisions: only items the group clearly agreed. For each: the decision in one sentence, the owner, the date, and the transcript line that shows agreement. If agreement is unclear, list it under "Needs confirming" instead.
2. Actions: verb + outcome, owner, due date. If no owner or date was said, write "owner not stated" or "date not stated". Don't guess.
3. Still open: topics raised with no decision, and any next step mentioned.
4. Messages for the company: anything the group said should be communicated, and who said they'd send it.

Rules: don't attribute opinions or quotes to people. Skip any section marked as notes-off. Keep it under 300 words. Use plain sentences.

My notes: [paste]
Transcript: [paste]

Read the "Needs confirming" list first. Those are the places where the room thought it agreed and didn't, and each is worth a quick message to the owner before the follow-up goes out.

The second prompt drafts next week's agenda from what's already in your system. Take the draft into your 1:1 with your principal and agree it there, so the agenda goes out with both your names behind it.

Prompt: Draft next week's leadership meeting agenda

Draft next week's leadership team meeting agenda (75 minutes) using the format below.

Inputs:
- Decision queue (item, owner, date needed, pre-read ready?): [paste]
- Late or blocked actions: [paste]
- Agenda requests received: [paste]
- Metrics that are red or moved more than [x]%: [paste]

Rules:
- Include 2 decisions and 1 issue, chosen by date needed, then by impact. Only schedule items with a pre-read ready; list the rest under "Not ready" with what's missing.
- Inform-only requests go under "Move to written update".
- Allocate minutes. Leave 5 minutes for the read-back and 5 for what we tell the company.
- Output: the run-of-show table, then "Not ready", then "Move to written update".

How do you fix a leadership meeting that isn't working?

Find out what's broken before you change anything. Ask each leader one to one what the meeting is for, what they'd cut and what they'd keep, then compare their answers with what last month's agendas actually spent time on. The gap between the two lists shows you which fix to make.

Run one test before you touch the format: ask each leader to name the company's top three priorities. If the answers differ, you have a strategy problem that no agenda will fix. Take the gap to your CEO first.

Leadership meeting diagnostic

SymptomUsual causeFix
Most of the time goes to updatesNo written update before the meetingMove updates to writing 24 hours ahead; open with exceptions only
Decisions keep slipping to next weekDecisions arrive without a pre-read or an ownerNo pre-read, no slot; one owner proposes an answer
Leaders agree in the room and object afterwardObjections were never heard before the meetingTalk to each affected leader one to one before the item comes up
Same topics come back every weekNothing records what was decidedKeep a decision log and a rule for reopening a decision
The CEO takes over the agendaThe CEO wasn't part of setting itAgree the agenda with the CEO in your 1:1 before it goes out
Pre-reads arrive but nobody reads themThey run long or arrive lateOne page, 24 hours ahead; open each decision with 5 minutes of silent reading
People multitask through itToo many people, or items that don't need themCut attendance to those who decide; invite others per item

The fix that works best is usually the smallest one the team will accept. Changing everything at once, like Ryan Kelly's first attempt, puts every leader's habits on the line together. Change one thing, run it for four weeks, then ask the group whether it helped.

When leaders agree in the room and object afterward

This symptom does the most damage, because the meeting looks like it worked. With the CEO present, objecting in public costs a leader more than nodding, so the objection moves somewhere cheaper: a private word with the CEO, a complaint to their team, or slow execution.

The meeting looks like it worked: with the CEO present, objecting in public costs a leader more than nodding. So one leader’s objection leaves the room three ways: a private word with the CEO, a complaint to their team, or slow execution.

Alyssa Palomba, then Chief of Staff at SportsRecruits, said that when she first joined the leadership team, she felt she had to react all the time, because the decision would be made in that meeting. She built a written culture around it: pre-reads first, then the conversation, then a wrap-up. Introverted and extroverted leaders can then talk it through, because everyone has prepared.

Dara Chen, then Chief of Staff at Rad AI, watched how engaged leaders were in the meeting, then called them afterward to say she sensed they disagreed and ask why. A change to planning or recruiting only works, she said, with buy-in from the stakeholders.

To tell which situation you're in, ask the leader who objected one question: "Did you get a chance to say this before the decision?"

  • If they weren't consulted, the fix is upstream. Before any contested item, talk to each affected leader one to one and put their objection in the pre-read, in their words.
  • If they were heard and overruled, the problem is commitment. Add one line to the read-back: "Is anyone not able to commit to this?" Asked out loud, it gives a leader a last chance to object, and it makes the objection later much harder to justify.
  • If they say the decision wasn't what they thought, the decision was vague. Tighten the read-back until each decision is one sentence with an owner and a date.

Talking to each leader before the meeting has a cost. If every outcome is settled in your one-to-ones, leaders learn the meeting is theater and start lobbying you, so use those conversations to surface objections and leave the outcome to the room. Remote teams can add a written round in the meeting chat: "one line each: commit, or what's stopping you?"

If you need to cut attendance, ask the CEO to tell each person dropped one to one before the invite changes, and say which items they'll still join for. Timing helps too. A reorganization, a new CEO or a new quarter lets you reset a meeting without it reading as criticism. When Kroll reorganized, Alexis Summit used the change to reset its whole operating rhythm, adding quarterly deep-dive reviews of each business that roll up into a review with the CEO. In your first 90 days, listen in month one and bring your first fix in month two.

Track three numbers for a month before and after the change: minutes on decisions versus updates, decisions made per meeting, and actions closed on time. Show your principal the before and after, and keep the numbers for when you discuss your own role and level.

This week, book 20 minutes with each member of the leadership team and ask: "If you could change one thing about our leadership meeting, what would it be?" By Friday you'll know which fix to try first.

New to running the leadership meeting? Our Fundamentals email course has lessons on setting your operating rhythm, leading without authority and building relationships across the leadership team.

Start the course

Take this guide with you

The full guide as a PDF: every section, template and chart, ready to print or share with your team.

Your PDF is ready.

Download the PDF
Oops! Something went wrong while submitting the form.

Free. We may email you new guides; unsubscribe anytime.

Frequently asked questions

How long should a weekly leadership team meeting be?

About 75 minutes for most companies of 50 to 500 people. Shorter works if status updates are written and the team has few decisions in a week. Longer usually means updates are being read aloud. If you regularly run out of time for decisions, cut updates first, then attendance, before adding time.

Who should attend a leadership team meeting?

The CEO's direct reports who make company-level decisions, plus the Chief of Staff. Invite others for specific items and let them leave afterward. Every extra person adds time and makes candid disagreement less likely, so keep the core group to people whose agreement the decisions need.

Should we record leadership meetings or use an AI notetaker?

Record decisions, owners and dates every time. Use a recording or AI notetaker only by group agreement, with one approved tool, consent from everyone present, topics that are never recorded, limited access to transcripts and a deletion date. Recording consent laws vary by state and country, so check with your legal team before the first meeting is recorded.

Should a leadership meeting start with a check-in or wins?

Open with a check-in only for a new team, a remote team that rarely meets in person, or a hard week, because you learn who is stretched before the decisions start. Ten leaders at 30 seconds each take 5 minutes, about 7% of a 75-minute meeting. Take those 5 minutes from the metrics slot, so the decisions keep their time. For any other team, wins belong in the written update.

What's the difference between a senior leadership team meeting and an executive team meeting?

The executive team is usually the CEO's direct reports and makes company-level decisions. A senior leadership team adds the department heads below them, so its meeting is larger and does more sharing than deciding. Rico Ashab, then Chief of Staff at Destination DC, described a senior staff of 20 that includes an executive team of 8. Names vary by company, so write down who belongs to each group and which one decides.

How do you get leaders to submit agenda items and pre-reads on time?

Make the deadlines fixed and public, agree with the CEO that items without a pre-read don't get a slot, and enforce it the first time it happens. Most leaders adjust after one of their items waits a week. Keep the pre-read to one page so the bar is easy to meet.

Sources and methodology
  • Pathways Report 2026, Chief of Staff Network, 2026. 1,819 job postings, June to early October 2026.
  • Chief of AI Report, Chief of Staff Network, 2025.
  • Chief of Staff Network podcast episodes: Alexis Summit, Ryan Kelly, Maria Mejia, Dora Nagy, Alyssa Palomba, Dara Chen, Rico Ashab.
  • Chief of Staff Network member resources (members only): an operating-rhythm plan a Chief of Staff shared, an operating-rhythm toolkit, and a member discussion of senior leadership team meetings.
  • EOS (the Entrepreneurial Operating System), for L10, Level 10 Meeting and IDS. Level 10 Meeting is an EOS trademark.
  • The 140-person company is an illustration. Meeting lengths, the meeting-types table and the 75-minute agenda are our recommendations.

Learn the job with people who do it

Membership gets you the Power Skills program, member events and a private community of working Chiefs of Staff.

Land your first Chief of Staff role

Launchpad helps you prepare, position yourself and interview for the role.

Starting out in the role?

The Fundamentals email course walks you through scoping the mandate, setting the cadence and earning trust.

Lead AI adoption from the Chief of Staff seat

The Chief of AI Fellowship is for operators turning AI into how the company runs.

Hiring a Chief of Staff?

Post the role on the Chief of Staff job board, or browse open roles.

Get your resume ready for the role

Get feedback on your Chief of Staff resume before you apply.

Let the right roles find you

Join the talent network and hear about Chief of Staff roles first.

The Chief of Staff newsletter

What Chiefs of Staff are reading, hiring for and building.

Get the full report

Every chart and cut from our latest salary research, sent to your inbox.

Using AI with sensitive data?

Learn the legal side of using AI at work.

More series