How to Run a Weekly Leadership Team Meeting

Most weekly leadership meetings run in the same order: each department head gives an update, the updates run long, and the one hard problem that needed the whole team gets fifteen rushed minutes at the end. Everyone leaves informed, and that problem waits another week.

The fix is mostly the order of the agenda. Open on the numbers, spend the biggest block of time on a ranked list of issues, and put an owner and a date on every decision before anyone stands up. Below is the 60-minute agenda we recommend, how to build the scorecard it opens on, and how to keep the issues list from turning into a debate club.

Who should attend

The weekly leadership meeting exists to make company-level decisions: where to move money, people and attention this week because a number moved. Status updates belong in writing, sent before the meeting. If a department’s week needs no decision from anyone else, one sentence about it is plenty.

That purpose settles the invite list. Invite the people accountable for a number on the company scorecard, which for most companies means five to eight department heads and the CEO. Anyone who attends only to report or to listen is better served by the written update and the notes afterward. Each extra person in the room adds a voice to every discussion on the issues list, and adds an hour of senior payroll to a meeting that happens fifty times a year.

The 60-minute agenda

Here is the Leadership Team Meeting agenda from our free templates, with what each slot is for.

1. Scorecard review (10 min): every number against its target. On-target numbers get a glance. Off-target numbers get zero discussion here: each one goes straight onto the issues list.
2. Departmental headlines (10 min): one sentence per function, such as a customer win, a resignation or a vendor problem. Anything that needs more than a sentence becomes an issue instead of a speech.
3. Priorities on track or off (10 min): the handful of goals the team committed to this quarter. Each owner says “on track” or “off track.” An off-track priority goes to the issues list, with the plan to fix it rather than the story of how it slipped.
4. Issues list (20 min): most of the meeting’s work happens here. The next section covers how to run it.
5. Decisions and owners (7 min): read back every decision and every new action item, with its owner and due date, so nobody leaves with a different version.
6. Who needs to hear what (3 min): decide what gets passed down to teams, and who says it.

The first three slots take 30 minutes and build the issues list. The last three work through it and record what was decided. If the reporting half keeps running over, the written update isn’t going out, or people are presenting it anyway.

If your team runs EOS

The Level 10 Meeting from EOS® (the Entrepreneurial Operating System) has the same shape at 90 minutes: segue, scorecard, rock review, customer and employee headlines, to-do list, 60 minutes of issues, and a conclude. If you run EOS, keep its names and its 90 minutes. The 60-minute version above is for teams that want the structure without adopting the whole system. The main difference is less time on issues, which works when the list is ranked before the meeting and the team expects to finish two issues properly rather than touch five.

Building the scorecard

A leadership scorecard is a short list of weekly numbers, each with a target and one owner. Five to ten is enough. That’s more than the three to seven we suggest for most meetings that review KPIs, and the leadership meeting can carry the extra because on-target numbers take a second each.

Three rules keep it useful:

• One owner per number: a person, never a department. When the number goes red, that person brings it to the issues list.
• Weekly numbers only: a metric that only updates monthly shows the same value three weeks running. Pick a weekly proxy (qualified pipeline added this week, rather than monthly revenue) or leave it for the monthly review.
• Targets agreed in advance: if the team argues about whether a number is good while it’s on screen, the target was never set.

Here is what that looks like for a made-up 40-person software company:

Number	Owner	Target	This week
New bookings	Ana (Sales)	$40K	🔴 $31K
Qualified pipeline added	Ana (Sales)	$150K	🟢 $162K
Customers lost, month to date	Ben (Customer Success)	2 or fewer	🟢 1
Support tickets open 48+ hours	Ben (Customer Success)	10 or fewer	🔴 23
Release shipped on schedule	Chris (Engineering)	Yes	🟢 Yes
Cash runway (months)	Dee (Finance)	18+	🟢 19
Offers accepted, quarter to date	Dee (Finance)	4	🔴 1

Three numbers are red, so three items go on the issues list before anyone argues for their own topic.

A scorecard also works better as a trend than as a single week. Twenty-three stale tickets is a bad week. Twenty-three after 12, 15 and 19 is a staffing problem, and the chart says so before Ben has to. In Less Meeting you attach each number to the recurring meeting as a KPI chart with its thresholds, and every week’s value adds to the same trend line, so the scorecard review is a glance at colors and slopes. See the leadership team setup for how that looks.

Working the issues list

The issues list gets the biggest block of time. Two habits let a team solve one problem in it instead of circling five.

Rank the list before the meeting. Whoever runs the meeting orders it by impact the day before, with the scorecard’s off-target numbers at or near the top. The team can reorder it in the first minute, but it doesn’t start from a blank page.

Then work from the top and finish each issue before starting the next. For each one:

1. Name the real problem: “Bookings are down” is a symptom. “Two of our four reps lost deals to the same competitor on price” is a problem someone can act on. Expect this step to take the longest.
2. Discuss it once: everyone says their piece a single time. Repeating a point louder doesn’t count as a second contribution.
3. Decide and assign: the discussion ends with a decision, an owner and a date, even when the decision is “Dee gathers the numbers and it comes back next week.”

Expect to get through two issues in twenty minutes. Whatever’s left stays on the list, ranked, for next week. A list that carries over is normal. A top issue that carries over three weeks running usually means nobody wants to make the call, and the person running the meeting should say so.

Watch for the Meeting Hijacker here: the executive who turns issue three into a referendum on their own department. The ranked list is your answer to that: the team agreed on the order before the meeting, and it’s in writing.

Assigning owners

Before the meeting ends, read back each decision with the person responsible and the due date, and write it down where you’ll see it at next week’s meeting.

Commitments from a weekly meeting routinely outlast the week they were made in. In Less Meeting’s data, over half of recurring meetings (53.7%) open with at least one action item still unfinished from an earlier week. A leadership meeting that starts from a clean notepad each Monday loses track of those, and the open item becomes nobody’s.

So open each meeting’s decisions slot with last week’s open items: closed, still open, or dropped, and anything dropped gets said out loud. Completion rates differ too. Action items raised in recurring meetings were completed 90% of the time, against 81% for items from one-off meetings, and closed in a median of 18 days rather than 25. Part of that gap is likely the kind of team that sets up a recurring series in the first place. A recurring meeting also gives an unfinished item somewhere to reappear, which a one-off meeting can’t.

In Less Meeting, open action items carry forward to the next occurrence on their own, and owners get reminders until they close them. How to carry action items forward across recurring meetings covers the same habit with a spreadsheet or a doc.

Who needs to hear what

In the last three minutes, settle how the rest of the company hears about this week’s decisions: from their manager, or from the rumor that got there first. For each decision, ask two questions: which teams does this change something for, and who tells them by when? Usually it’s each department head telling their own team, with the same one-line version, before Wednesday.

Measuring the meeting

A leadership meeting is the most expensive recurring hour on most calendars. Eight senior people for an hour a week comes to about 400 person-hours a year, so check whether it pays for itself. Run it through the meeting cost calculator once and you’ll look at the invite list differently.

Beyond the cost, watch three signals:

• It starts and ends on time: across meetings run with a timed agenda in Less Meeting, 72% finish on time or early. When a leadership meeting routinely overruns, it usually means someone is presenting the written update live. See how to start and end meetings on time.
• Issues leave the list: count issues resolved per meeting over a month. Two a week is healthy. Zero for three weeks means the ranking or the deciding has broken down.
• The team rates it: a quick efficiency rating after each meeting tells you when it’s sliding, well before anyone says so in a skip-level.

Frequently asked questions

How long should a leadership team meeting be?

Sixty minutes for most teams using the agenda above, or 90 if you run EOS and its Level 10 format. If yours regularly needs more, look at the reporting half first: status that should have gone out in writing is the usual cause.

How often should the leadership team meet?

Weekly, at the same time every week. Early in the week works best, since the scorecard reflects a finished week and the decisions have the rest of the week to take effect. Monthly or quarterly strategy sessions are separate meetings with their own agendas.

Who should attend the weekly leadership meeting?

The people accountable for a number on the company scorecard, usually the CEO and five to eight department heads. Keep it to people who own a number or make the decisions. Others can read the notes.

What goes on a leadership team scorecard?

Five to ten weekly numbers, each with a target and one owner. Typically bookings or revenue, pipeline, customer retention, a support or service health number, delivery against plan, cash, and hiring. Pick numbers that update weekly and that someone in the room can change.

What’s the difference between a leadership meeting and an L10 meeting?

An L10 (Level 10 Meeting) is the specific 90-minute weekly leadership meeting format from EOS. The agenda above follows the same shape (scorecard first, a ranked issues list, owners on every decision) in 60 minutes, for teams that don’t run the full EOS system.

Should the CEO run the leadership meeting?

Not necessarily. Many teams have a COO, chief of staff or rotating member run the agenda and the clock, so the CEO can take part in the discussion instead of refereeing it. Whoever runs it needs the authority to cut off a speech and move to the next issue.