Weekly Leadership Meeting Agenda: The Momentum Meeting

For years my weekly meetings were the same thing everyone’s are. Each person gave an update. The updates ran long. Someone raised a problem, we talked about it for twenty minutes, agreed it was a problem, and moved on. The meeting ended late. Nobody was sure who was doing what.

That meeting cost us an hour of every leader’s week and produced almost nothing.

What changed it wasn’t more discipline from me. It was a fixed agenda that forces the meeting to do its real job: find the problems early and solve them. In my companies we call it the Momentum Meeting, and it’s the heartbeat of the BOSS framework.

The Momentum Meeting agenda

Same day. Same time. Same agenda. Starts on time, ends on time.

The first five segments are fast on purpose. They’re for spotting problems, not discussing them. Every discussion goes to segment six, where the team gives it real attention.

Segment by segment

1. Check-in

Each person shares one personal and one business win. It sounds soft. It isn’t. It shifts people from their inbox to the room, and it reminds a leadership team that they’re humans who like each other.

2. Scoreboard

The weekly scoreboard of five to fifteen leading numbers, each with an owner and a goal. The owner says “on track” or “off track.” That’s it. Off-track numbers go to the issues list. See business scorecard.

3. Quarterly Goals

Each goal owner reports “on track” or “off track.” Again, no discussion. See quarterly business goals.

4. Headlines

Brief news the team should know: a big customer win or complaint, a team member’s milestone, a vendor change. One or two sentences each. If it needs a conversation, it goes on the list.

5. Last week’s to-dos

Each to-do from last week: done or not done. Healthy teams finish the large majority. A to-do that slips twice becomes an issue.

6. Solve issues

This is the meeting. Look at the issues list, pick the three most important, and solve them one at a time, starting with number one. For each issue:

1. Find the real issue. The stated problem is often a symptom. Ask “why” until you hit the root.
2. Discuss it once. Everyone speaks; nobody repeats.
3. Decide. Make a decision, even if it’s imperfect.
4. Assign the to-do. Owner and date.

If you solve three issues well, the meeting was a success — even if twenty remain. Read how to solve problems in team meetings for the full method.

7. Conclude

Read back the new to-dos with owners and dates. Decide what needs to be communicated to the rest of the company and who will do it. Then each person rates the meeting on a simple scale. Anything less than great gets a quick “what would make it better?”

Rules that keep it working

• Same day and time every week. Monday or Tuesday morning works for most teams.
• Never cancel. If someone’s out, run it anyway. If the day doesn’t work, move it within the week.
• Start on time, end on time. Respect builds trust.
• Phones away. It’s one hour.
• One facilitator. Usually the integrator. Not necessarily the owner.
• Everyone brings issues. Leaders who never raise issues are hiding them.
• Decisions stick. Once solved, don’t re-litigate it in the hallway.

The prep that makes it fast

The meeting only runs smoothly if the inputs are ready:

• Scoreboard numbers entered by the day before.
• Quarterly Goal status updated.
• Issues list kept current all week.
• To-dos tracked in one place.

In my companies, an AI chief of staff does most of this prep — pulling the scoreboard, updating goal status, flagging overdue to-dos and organizing the issues list — so the meeting starts with everything on the screen. See AI for KPIs and meetings.

Common weekly meeting mistakes

• Status updates instead of solving. If everyone reports for forty minutes, there’s no time left to fix anything.
• Discussing every off-track number in the moment. It derails the agenda.
• Solving symptoms. “Sales are down” isn’t an issue. “Nobody is calling web leads within a day” is.
• No owners and dates. A decision without a to-do is a wish.
• The owner dominates. The facilitator’s job is to make sure every voice gets heard.
• Skipping weeks. The habit dies faster than you’d believe.

How this compares to other systems

If you’ve run EOS, you’ll recognize the shape — EOS’s Level 10 Meeting follows a similar structure and is one of its best-known tools. Scaling Up adds a daily huddle and monthly meetings. Agile teams run sprint ceremonies. The common thread is a fixed agenda, numbers reviewed often and most time spent solving problems. See EOS tools explained and daily huddle.

The bigger meeting rhythm

The weekly meeting is one part of a rhythm:

• Daily: an optional short huddle for teams that need it. See daily huddle.
• Weekly: the Momentum Meeting.
• Quarterly: a planning session to review the quarter and set new goals. See quarterly planning meeting.
• Annually: a two-day planning session to revisit the Blueprint and set the year. See annual planning meeting.

Start this week

Put the meeting on the calendar for the same time every week. Build a rough scoreboard. Start an issues list. Run the agenda exactly as written for thirteen weeks before you change anything. Most teams feel the difference within a month — fewer surprises, faster decisions, and an owner who isn’t solving everything in the hallway.

If you’d like help installing the rhythm with your leadership team, request a strategy call. It’s usually the first thing I set up with a new client.

What changes after a quarter

Teams that run this agenda for thirteen straight weeks almost always report the same shifts. Problems surface while they’re still small. Leaders start bringing issues instead of hiding them. The owner gets interrupted less during the week because people know there’s a reliable place to raise things. And the meeting itself gets shorter on the reporting side and deeper on the solving side. That’s when the business starts to feel like it has momentum — which is exactly why we named it that.