How Should a Weekly Leadership Meeting Actually Work?

Reporting belongs before the meeting

This is one of the most important distinctions I make with leadership teams. Reporting belongs before the meeting. Thinking, deciding and committing belong inside the meeting.

If somebody can tell you something in writing beforehand, they shouldn't spend ten minutes reading it aloud to a room full of people. That is an extraordinarily expensive way of distributing information.

Everyone attending the weekly leadership meeting should submit a short written progress report beforehand. Not War and Peace. Not a bureaucratic essay. Just the useful information everybody else genuinely needs to know. For example:

• What progress did I make against my commitments?
• What did I complete?
• What is not on track?
• What challenges or choke points am I facing?
• What support or decision do I need?
• What am I proposing should happen next?

Then everybody attending the meeting reads the material before they arrive. No exceptions. That changes the meeting completely. Instead of spending an hour discovering what everybody has been doing, you can use the hour to work out: What now?

Writing forces people to think

There is another reason I insist on written preparation. Writing clarifies. It is very easy to arrive in a meeting and talk vaguely for ten minutes. It is much harder to write: This is what I committed to. This is what happened. This is the evidence. This is what is getting in the way.

And this is what I recommend we do. Writing makes people organise their thinking before everybody else's time is involved. It also reveals something useful. If someone repeatedly cannot produce a meaningful progress report, you may need to ask whether they really need to attend that meeting at all.

Same day, same time, every week

The weekly meeting should become part of the operating rhythm of the business. Same day. Same time. Every week. Usually somewhere around 60 to 90 minutes, depending on the team and the business. Protect it fiercely.

If the meeting is constantly moved, cancelled or treated as optional, you are sending a message: This matters — but not really. It matters unless something else comes up. And something else will always come up. The meeting should become a heartbeat of the business. Not a special event.

Not something you hold only when there is a crisis. Not something you squeeze in when nobody can think of anything better to do. It is part of how the business operates. Of course, consistency alone is not enough. You can consistently run a terrible meeting. The meeting also has to do the right job.

1. Start with the score

Begin with the few numbers that tell you whether the business is moving in the right direction. Not 27 pages of data. Not every measure anybody has ever thought might be interesting. The measures that matter. Ask: Where are we winning? Where are we off track? What do the numbers actually tell us?

Not: What story would we like to tell ourselves about the numbers? What do they actually say? A visible score creates a shared understanding of the current position. Everybody is looking at the same evidence.

That matters because businesses can otherwise become dominated by whoever speaks most confidently, whoever has the strongest opinion or whoever can tell the most convincing story. Evidence creates a much better conversation.

2. Celebrate the wins

Accountability should not become a weekly search for what went wrong. Ask: What went well? Who deserves a shout-out? What improved? Who followed through? What impact did that have? Notice the manager who stepped up. Notice the difficult conversation that finally happened.

Notice the customer problem that got resolved. Notice the process that improved. Notice the result that moved. Notice the person who did what they said they were going to do. Because what leaders notice gets repeated. Celebrating wins creates momentum.

It also reminds everybody that accountability is not punishment. It is ownership.

3. Discuss the misses

Then look honestly at what is not on track. What result was missed? What commitment didn't happen? What is behind? Ask: What happened? What got in the way? What can we learn? But don't turn the meeting into a courtroom. And don't let it become an excuse festival either.

The objective is to understand the issue well enough to do something useful about it. Was the commitment unclear? Did nobody genuinely own it? Did priorities change? Was there a skill gap? Was somebody waiting for a decision? Was the action avoided because it was uncomfortable?

Or did somebody simply choose to do something else? Be curious. But don't allow curiosity to become endless tolerance. If the same commitment is missed repeatedly, the conversation has to go deeper.

You cannot simply move the date every week until everybody forgets why the action mattered in the first place.

4. Resolve the choke points

This is often where a good weekly meeting creates the most value. Ask: What is getting in our way? What decision needs to be made? What do we need to remove, clarify or change? A choke point might be:

• a decision nobody has made;
• a policy managers are applying differently;
• a customer issue that keeps circulating;
• a process that no longer works;
• somebody who doesn't have the authority they need;
• a resource gap;
• or an issue everybody has been politely walking around.

The purpose is not to admire the choke point. It is to resolve it. Make the decision where possible. Remove the barrier. Clarify the standard. Give the authority. Or determine exactly what has to happen next to get the decision made.

This is also why the right decision-makers — and only the right decision-makers — need to be in the room. If every discussion ends with: "We'll have to ask someone else." then you may not have the right people in the meeting.

5. Turn every useful discussion into an action

A meaningful discussion should eventually land somewhere. Ask: What action will close the gap? Who owns it? By when? What will success look like? And please don't say: "We'll all own it." When everybody owns an action, usually nobody does. Other people may contribute.

But one person should be responsible for making sure it happens. Then put a real date on it. Not: "As soon as possible." Not: "Over the next few weeks." Not: "When things calm down." By when? And make sure everybody understands what completion looks like.

"I started it" is not the same as "It's done." "I spoke to them" is not necessarily the same as "We reached the agreed outcome." Clarity matters.

Write the action down

This is where the Action Register becomes important. The register should capture things such as:

• the commitment; the owner; the priority; the due date; the status;
• what success looks like;
• and any blocker requiring attention.

Why? Because memory is not an execution system. An agreement that isn't captured becomes vulnerable to interpretation. "I thought you were doing it." "I didn't realise it was due this week." "I thought we'd agreed something different." No. Write down what was agreed. If the commitment matters, recording it should not be controversial.

6. Confirm the focus for the next week

Before everybody leaves, ask: What matters most now? What should we start doing? What should we stop doing? What should we continue doing but improve? What must be different by the next meeting? Everybody should leave knowing where the focus sits. Then finish on time.

The quality of a meeting is not measured by how long it ran. It is measured by: What became clearer? What was decided? What will now happen?

The next meeting starts with the previous commitments

This is where most businesses lose the value of the whole process. At the next meeting, do not begin with an entirely fresh collection of interesting topics. Come back to what was agreed last time. Ask: What did you commit to? By when? What happened? If it is complete, acknowledge it and close it.

If it is genuinely at risk, understand what support or decision is needed. If circumstances changed, renegotiate it consciously. If somebody else should own it, reassign it clearly. If it is no longer important, remove it.

But do not allow actions to roll over week after week without a proper conversation. Otherwise you're teaching everybody that the original date never mattered. And eventually the action itself stops mattering too. I've seen action lists where the same item survives for months. Sometimes years.

The wording changes slightly, but the action remains. At that point it is not really an action. It's wallpaper.

The chair protects the process

The chair of the meeting has an important job. They are not there to dominate. They are not there to solve every problem. They are not there to be the only person doing any thinking. The chair protects the process. They keep the conversation focused. They stop long verbal updates.

They challenge vagueness. They make sure discussions eventually land somewhere. Useful questions for the chair include: What do you need from this meeting? What decision are you asking us to make? What do you recommend? Who owns the next step? By when? How will we know it's done?

That is how the meeting moves from talk to action.

Don't rescue people who haven't done the preparation

If written preparation is a requirement, treat it like one. If somebody repeatedly arrives without submitting their progress report, address it. Do not rescue them by saying: "Never mind, just give us your update now."

If you do that every week, the written preparation isn't actually mandatory. It's a suggestion. And suggestions don't survive for long in busy businesses. The same principle applies throughout the meeting. If somebody is meant to bring evidence, expect the evidence.

If they own an action, expect them to report on the action. If the meeting needs a recommendation, ask for their recommendation rather than solving the issue for them. A leadership meeting should build managerial capability, not reinforce dependency.

A weekly meeting is part of the execution system

A business can have: a terrific annual plan; a clear 90-day theme; a beautifully designed scoreboard; a list of KPIs; a leadership team full of good intentions. And still achieve very little. Because plans do not execute themselves. There needs to be a regular rhythm that asks:

What is actually happening? What is working? What isn't? What is getting in the way? What decision needs to be made? Who will do what next? That is why I see the weekly accountability meeting as one of the places where a Leadership Execution System actually comes alive. Direction matters.

Measures matter. Plans matter. But eventually somebody has to do something. And then somebody has to come back and ask what happened.

A simple weekly leadership meeting structure

The meeting can be remarkably straightforward.

Before the meeting

Every attendee submits a short written progress report at least 24 hours beforehand. Everybody reads everybody else's report.

In the meeting

1. Review the score

Where are we winning? Where are we off track? What does the evidence tell us?

2. Celebrate the wins

What moved? Who stepped up? What should we recognise?

3. Discuss the misses

What didn't happen? What did we learn? What needs a deeper conversation?

4. Resolve the choke points

What is stopping progress? What decision is needed? What barrier can we remove now?

5. Agree the actions

What will happen? Who owns it? By when? What does success look like?