The weekly leadership meeting: agenda, structure and best practices

A weekly leadership meeting is the hour or so each week in which the leadership team checks the business against its numbers and priorities and resolves the issues that block progress. It works when it follows the same agenda every week, keeps updates short, spends most of its time solving a short list of issues, and ends with written decisions and actions that have owners and dates. Most of what goes wrong in these meetings comes from treating them as a round of reports.

The cost of getting it wrong is easy to underestimate. Research by Leslie Perlow and colleagues, published in Harvard Business Review, found executives spending nearly 23 hours a week in meetings, up from under 10 in the 1960s. A weekly leadership meeting that runs badly is not just one wasted hour. It pushes decisions into corridors and side messages, which is where alignment quietly breaks.

What the meeting is for

The weekly meeting has three jobs. It shows the team, quickly, whether the week is on track. It moves the company priorities forward by catching problems while they are still small. And it takes the decisions that need more than one function in the room. Detailed project reviews, strategy debates and individual performance belong somewhere else.

Coaching and individual feedback need a separate setting. People by Design’s guide to useful one-to-ones covers how to prepare and run that conversation.

Michael Mankins, writing in Harvard Business Review, argued that senior teams lose much of their time in diffuse discussions that were never meant to reach a decision, and recommended dealing with operations and strategy in separate meetings. The weekly meeting is the operational one. Keeping it that way is what protects it.

Who attends

The CEO or managing director and the direct reports who own a function or a company priority. In a company of fifty to two hundred people that is usually five to eight people. Above eight, discussion slows and people start attending to listen rather than to contribute.

• Attendance is part of the role, not an invitation. Someone who cannot attend sends their numbers and priority status in advance, not a deputy who cannot decide.
• Guests join for a specific issue and leave when it is resolved.
• If the founder is the only one who decides, the meeting becomes a briefing. Read how to reduce founder dependency if that sounds familiar.

The agenda: 75 minutes, same order every week

The agenda below fits in 75 minutes. Teams that need 90 give the extra time to issues. Teams that need 60 shorten issues, never the close. The order matters: numbers and priorities come first, so the issues list is built from facts rather than from whoever speaks loudest.

Metrics: ten minutes, exceptions only

The metrics block uses a short weekly scorecard: the five to ten numbers that move weekly and predict the month. Each owner answers one question per number: on track or off track? Explanations wait for the issues block. The weekly scorecard should be a subset of the executive KPI dashboard, with the same definitions, so the weekly and monthly conversations never argue about different numbers.

Priorities: one sentence per owner

The priorities check covers the three to seven company priorities for the quarter. Each owner says whether theirs is on track for the quarter. If not, it goes to the issues list. Detailed progress updates do not belong here; if the team needs more depth, it schedules a separate review with the people involved.

The issues list: solve, don't report

This is where the meeting earns its time. The issues list collects everything raised in the earlier blocks, plus anything owners added beforehand. The team ranks it, picks the top three and works through them one at a time:

1. Name the real issue. What gets raised is often a symptom. Ask what is causing it before discussing solutions.
2. Discuss once. Everyone says what they think. The chair cuts repetition and side debates.
3. Decide. Agree who decides, if it is not obvious, and close it. A good decision this week usually beats a perfect one next month.
4. Record the action. One owner, one action, one date. Not a team, not “we”.

An issue that cannot be solved because information is missing becomes an action to get that information, with a date. Issues not reached this week roll to next week's list. If the same issue keeps rolling, it is either not important or not owned. Either way, it needs a decision.

The decisions and actions log

Without a written log, people leave with different memories of what was agreed. The log is simple and lives in one shared place, not in personal notebooks:

• Decisions: what was decided, by whom, on what date, and who needs to be told.
• Actions: what will be done, the single owner, the due date and the status.
• Open issues: what was raised and not reached, carried to next week.

The scribe sends it the same day, and next week's meeting opens by reading its actions. That loop, more than any agenda, is what builds accountability across a leadership team.

Three roles

The chair does not have to be the CEO. It often works better when someone else chairs and the CEO takes part in the substance. Rotating timekeeper and scribe every quarter spreads the discipline.

Behaviours that make it work

• Start and end on time, every week. A meeting that starts late teaches people to arrive late.
• Prepare before, not during. Numbers and priority status are updated before the meeting starts.
• Disagree in the room. Say it before the decision, not afterwards in a side conversation.
• Speak for the company, not your function. The question is what is best for the business.
• Leave with one message. Agree what is communicated to the wider company, and by whom.
• Review the meeting. Once a month, spend two minutes on what to keep and what to change.

What to move to other forums

Much of what drags a weekly meeting down is legitimate business discussed in the wrong place.

Seeing these forums side by side is the point of an operating cadence: each meeting has one job, so none has to do all of them.

A one-week example

Ribeira Distribuição is a fictional 90-person food distributor. Its leadership team of six meets every Monday at 9:00 for 75 minutes. This is one illustrative week.

• Friday before. Owners update the weekly scorecard and their priority status. Two issues are added in advance: a delayed warehouse system rollout and a key customer asking to renegotiate terms.
• Monday, actions and metrics. Six of seven actions from last week are done; the missed one gets a new date. Complete, on-time deliveries are off track for the second week running, so they go to issues.
• Monday, priorities and headlines. Four of five priorities are on track; the warehouse rollout is not. The commercial director mentions a competitor's price change, which is added to issues.
• Monday, issues. Delivery performance is ranked first. The real cause is not the drivers but late order cut-offs from two large customers. Decision: the commercial director agrees new cut-off times with both by Thursday. Next, the go-live of the warehouse system moves by two weeks, and the operations director tells the affected teams today. The price change rolls to next week, with an action to bring data.
• Monday afternoon. The scribe sends the log: three decisions, five actions, one rolled issue.
• The following Monday. The meeting opens by reading out those five actions.

Nothing in that week is dramatic, and that is the point. Problems are named early, decided quickly and followed up without anyone having to chase.

Our weekly leadership meeting agenda gives you this structure ready to use, with the decisions and actions log included. If you want help designing the full set of leadership routines and making them stick, that is part of our leadership operating system work. A good place to start is an Operating Assessment, where we look at how your leadership team meets, decides and follows through today.