How to Run an Effective Leadership Team Meeting: A Chief of Staff's Guide

Feb 8

Takeaway: Give the meeting one clear job, move routine reporting into a pre-read, and close every decision with an owner, a date, and a written record.

A leadership meeting concentrates several of the company's most senior people in one room. The chief of staff's job is to make that time produce decisions, shared understanding, and clear commitments.

The familiar failure mode is a long tour of status updates followed by a rushed discussion of the one issue that needed the whole team. The fix starts before the meeting. Decide which conversations belong in the room, prepare the team to have them, and design the follow-through at the same time as the agenda.

Decide what the meeting is for

Status, weekly tactics, and long-range strategy need different kinds of attention. When they share one agenda, the urgent items usually crowd out the important ones.

Patrick Lencioni's Death by Meeting separates the daily check-in, weekly tactical meeting, monthly strategic meeting, and quarterly off-site, each with its own cadence and rules (The Table Group). You don't need to copy that structure. You do need a sentence that explains the purpose of each recurring meeting.

For a weekly leadership meeting, a workable purpose might be:

Review the few signals that show whether the business is on track, resolve cross-functional issues that can't be handled elsewhere, and confirm this week's commitments.

That statement gives you an editing rule. A detailed departmental update can move to the pre-read. A decision about next year's operating model belongs in a longer strategic session. A cross-functional issue blocking this month's priority belongs here.

Build the agenda around the decisions

Start with the issues that need the group, then add only the reporting required to frame them. A 60- to 75-minute weekly agenda might look like this:

Open commitments, 5 minutes. Review last week's outstanding actions and resolve exceptions.
Metrics and priorities, 15 minutes. Flag movement, variance, and blockers. Don't narrate every line.
Priority issues, 35 to 50 minutes. Work the ranked list of decisions and cross-functional problems.
Recap, 5 minutes. Read back decisions, owners, due dates, and parked items.

The EOS Level 10 Meeting uses a related structure and reserves roughly 60 minutes of a 90-minute meeting for identifying, discussing, and solving issues (EOS Worldwide). The useful principle is the allocation: most live time should go to work the team can't complete asynchronously.

Rank the issues before the meeting

If the issues list contains fifteen items, the agenda is pretending the team can resolve more than it can. Rank the list and work from the top. Three completed decisions are more valuable than ten partially opened conversations.

For each proposed issue, ask:

What exactly needs to be decided?
Who has the decision right?
What information does the team need beforehand?
What happens if the item waits a week?

Those questions expose topics that aren't ready, aren't important, or don't require the leadership team.

Prepare a pre-read people can use

A pre-read should reduce the amount of orientation required in the room. For a real decision, one or two pages are often enough:

The decision requested
The relevant context and constraints
The viable options
The owner's recommendation
The tradeoffs or risks the group should test

Amazon's narrative-memo practice is a useful reference because it treats writing as part of the thinking. In the company's 2017 shareholder letter, Jeff Bezos described memos written and revised in full sentences, with silent reading built into the meeting itself (Amazon 2017 Letter to Shareholders). The transferable point isn't the six-page format. It's that the decision should be legible before the debate begins.

If the team won't reliably read in advance, reserve the first few minutes for silent reading. That is still more disciplined than a presenter walking through material while everyone else tries to catch up.

The chief of staff may write or edit the decision brief, but the issue owner should remain accountable for the recommendation. Editing the logic is support. Taking ownership away from the responsible leader creates a different problem.

Facilitate the decision, not the performance

During the meeting, listen for where the conversation loses its object.

Restate the decision. When discussion spreads, ask: "What decision are we trying to make before we leave?"

Clarify the mode. Tell the room whether it is exploring, advising, or deciding. Participants behave differently when they know which kind of contribution is needed.

Bring in the closest knowledge. Seniority doesn't always track with relevant information. Ask the person closest to the work for the facts before the room settles on a view.

Test disagreement. If the room goes quiet too quickly, ask what risk the current recommendation understates. If it loops, summarize the competing assumptions and identify which one the decision owner accepts.

Manage airtime. Invite people who haven't spoken and interrupt repetition without embarrassment: "I have that point. I want to hear from the team closest to implementation before we close."

Capture the result visibly. Write the decision and next actions where participants can see them. If the language isn't clear enough to record, the agreement probably isn't clear enough to execute.

Close the loop before anyone leaves

A decision with no owner is a suggestion. Before the meeting ends, read back:

The decision in one or two sentences
The single accountable owner
Any action items and due dates
The people who need to be informed
Any condition that would reopen the decision

Publish a short recap the same day. Put durable decisions in the decision log, and link any relevant memo rather than reproducing it in several places.

At the next meeting, start with the open commitments. The point isn't to shame anyone. It is to surface delays early, renegotiate dates when facts change, and keep commitments visible.

Review the meeting as an operating system

Don't wait for general frustration to accumulate. Once a month, use five minutes to ask:

Which agenda section helped us decide?
Which section could have been a document?
Did the right people attend for the decisions we made?
Which topics keep returning without resolution?
Are owners and due dates being closed reliably?

Patterns matter more than one awkward session. A recurring lack of pre-reads is a preparation problem. Repeatedly reopened decisions point to unclear authority or weak documentation. Too many parked items may mean the group is avoiding tradeoffs or bringing low-priority topics into the room.

Frequently asked questions

How long should a weekly leadership team meeting be?

Choose the length after defining the job and the issue load. Sixty to ninety minutes can work for a weekly tactical meeting, but a shorter meeting with prepared decisions is better than filling a standard block with updates.

Who owns the meeting, the CEO or the chief of staff?

The principal sets the meeting's purpose. Designated decision owners make calls within their authority, and the chief of staff often owns the process: agenda design, pre-reads, facilitation, decision capture, and follow-through.

What belongs in the notes?

Keep the durable record short: decisions, actions with one owner and a date, parked items, and links to supporting material. A transcript makes the important parts harder to find.

What if leaders don't read the pre-read?

Shorten it, send it on a reliable schedule, and make the decision requested obvious at the top. If advance reading still doesn't happen, add silent reading time at the start and protect the rest of the session from a live presentation.

Use the free Leadership Team Meeting Agenda and Run Sheet to adapt the timing, pre-read prompts, and decision-capture format for your own team.

Adrienne Gaughan