How to Run an Effective Leadership Team Meeting: A Chief of Staff's Guide
Takeaway: A leadership team meeting works when the agenda is built around decisions rather than updates, the reading happens before the room fills, and every commitment leaves with a named owner and a date.
The leadership team meeting is the most expensive recurring event on a company's calendar, and the chief of staff usually owns it. Get it right and the executive team leaves aligned, with clear commitments and fewer side conversations. Get it wrong and you have paid a room full of senior people to listen to status updates they could have read in five minutes.
The problem is well documented. In a Harvard Business Review study, executives reported spending nearly 23 hours a week in meetings, up from under 10 hours in the 1960s. When the same researchers surveyed 182 senior managers, 71 percent said meetings were unproductive and inefficient, and 65 percent said meetings kept them from completing their own work (Perlow, Hadley & Eun, HBR). Researcher Steven Rogelberg estimates that a 5,000-person organization can waste on the order of $100 million a year on unproductive meeting time (The Surprising Science of Meetings). The leadership meeting sets the tone for all of it. If the top team runs a tight meeting, the rest of the company tends to follow.
Here is how a chief of staff designs and runs one that earns its cost.
Start With the Job the Meeting Is For
Most leadership meetings fail because they try to do everything at once. Status, tactics, and long-term strategy all get crammed into a single weekly hour, and none of them get the attention they deserve.
Patrick Lencioni made this the central argument of Death by Meeting: the fix isn't fewer meetings, it's different meetings for different purposes. He separates the daily check-in, the weekly tactical meeting, the monthly strategic meeting, and the quarterly off-site, each with its own cadence and rules (The Table Group). You don't need to adopt his model exactly, but you do need to decide what any given meeting is for before you build the agenda.
For a weekly leadership meeting, the job is almost always tactical: review the numbers, surface what is off track, and resolve the issues that need cross-functional agreement this week. Strategy belongs in a longer, less frequent session where people have room to think. Mixing the two is how you end up debating next year's org design while a shipping deadline slips.
Build the Agenda Around Decisions, Not Updates
The single highest-leverage change a chief of staff can make is to strip status reporting out of the live meeting. Updates are asynchronous by nature. They can be written down and read. Decisions and debate are what actually need the room.
A durable weekly structure looks like this:
- Metrics scan (10 minutes). Walk the handful of numbers that tell you whether the business is on track. Flag anything off target. Don't solve it yet.
- Priorities check (10 minutes). Confirm the small number of things that must move this quarter are moving, and name any that are stuck.
- Issues, decided (30 to 45 minutes). The heart of the meeting. Work a prioritized list of issues, and for each one identify it clearly, discuss it, and land on a decision or a next action with an owner.
- Commitments recap (5 minutes). Read back every decision and action item with its owner and date before anyone leaves.
The EOS Level 10 Meeting popularized a similar shape, giving roughly 60 of its 90 minutes to solving issues and reserving the rest for reporting and accountability, using a simple Identify, Discuss, Solve sequence (EOS Worldwide). The exact framework matters less than the principle: protect the majority of the time for the conversations only this group can have.
Prioritize the issues list ruthlessly
A leadership meeting can only genuinely resolve a few things well. If the issues list has fifteen items, rank them and work from the top. Getting through three issues completely beats touching ten and resolving none. Whatever doesn't get reached rolls to next week or gets handled offline.
Move the Reading Out of the Room
The most effective structural change to a decision meeting is to stop presenting and start reading.
Amazon is the well-known example. Instead of slide decks, teams write a narrative memo, and the meeting opens with everyone reading it in silence before any discussion begins. In his 2017 letter to shareholders, Jeff Bezos explained the logic: writing in full sentences forces clearer thinking than bullet points, and a great memo is written, rewritten, and shared with colleagues to improve before it's ever presented. He also noted that people often underestimate the work involved, and that a strong six-page memo can take a week or more (Amazon 2017 Letter to Shareholders).
You don't have to mandate six pages. The transferable practices are:
- Require a pre-read for any real decision. A one or two page brief stating the issue, the options, the recommendation, and what is being asked of the group.
- If people won't read in advance, read together. Ten minutes of silent reading at the top of the meeting still beats a live walkthrough, and it puts everyone on the same page before debate.
- Send the agenda before the meeting, not during. People should arrive knowing what will be decided.
As the chief of staff, you're often the one who writes or edits these briefs, or who coaches owners on writing them. That editing isn't busywork. A brief that can't clearly state the decision on the table is a sign the issue isn't ready for the room.
Run the Room Well
Structure gets you most of the way. The rest is facilitation, and this is where the chief of staff earns trust.
Protect the decision. When a discussion circles, name it. Ask what specifically is being decided, who owns the call, and what is blocking it. A useful phrase: "What would we need to know to decide this today?"
Manage airtime. The most senior voice isn't always the most informed one. Draw out the person closest to the work, and gently interrupt the person who is repeating themselves. This is easier for a chief of staff than for a peer, which is part of why the role owns the meeting.
Separate discussion from decision. Make it explicit when the group is exploring versus committing. People argue harder when they're unsure which mode they're in.
Capture in real time. Keep a running list of decisions and action items visible on screen as they happen. If it's not written down as it's agreed, half of it will be remembered differently by Friday.
The Meeting Ends When the Follow-Through Starts
A decision with no owner is a suggestion. Before anyone leaves, read the commitments back: each action item, the single person accountable, and the date. One owner per item, not a committee.
Within a few hours, publish the notes. Keep them short. A good format is the decisions made, the action items with owners and dates, and anything explicitly parked for later. Send it to attendees and to anyone downstream who needs to act. This record is also the start of your decision log, the single source of truth that keeps the team from relitigating settled questions.
Then close the loop at the start of the next meeting by reviewing last week's action items first. Nothing enforces follow-through like knowing your name and your commitment will be read aloud again in seven days.
A Simple Test for Whether It Is Working
After the meeting, ask yourself three questions. Did we decide the things that needed deciding? Does everyone know who owns what next? Could any part of this have been an email or a document instead? If the answer to the last question is "most of it," you're running an update meeting, not a leadership meeting, and it's time to rebuild the agenda.
FAQ
How long should a weekly leadership team meeting be? Sixty to ninety minutes is a common and workable range for a weekly tactical meeting. What matters more than the length is the ratio: the majority of the time should go to resolving issues, not to reporting status that could have been read in advance.
Who should own the leadership team meeting, the CEO or the chief of staff? The CEO owns the outcomes and makes the final calls. The chief of staff typically owns the process: setting the agenda, collecting pre-reads, facilitating, capturing decisions, and driving follow-up. Separating the two roles keeps the meeting disciplined without putting the principal in the position of policing the clock.
What is the difference between a tactical and a strategic leadership meeting? A tactical meeting handles the issues that affect the team this week and runs on a weekly cadence. A strategic meeting makes fewer, larger decisions that shape the coming quarters and needs more time and a slower pace. Keeping them separate stops urgent tactical noise from crowding out long-term thinking.
What should the meeting notes include? Keep them to three things: decisions made, action items with a single owner and a due date, and anything explicitly parked for later. Publish them the same day and review the open action items at the start of the next meeting.
How do I run an effective leadership team meeting? Decide what the meeting is for, then build the agenda around decisions rather than status updates. Move reporting into a written pre-read or dashboard people review beforehand, and protect the majority of the live time for the issues only this group can resolve. The EOS Level 10 Meeting gives roughly two-thirds of its time to solving issues (EOS Worldwide). Facilitate actively, capture decisions in real time, and let every commitment leave with one named owner and a date.
If you want a ready-to-use structure, our Leadership Team Meeting Agenda and Run Sheet template lays out the agenda blocks, timing, pre-read prompts, and a decision-capture format you can adapt in an afternoon. Join the email list to grab it, and we will send new operator playbooks as they publish.
