How to Run a Weekly Leadership Huddle That Doesn't Waste Everyone's Time

Ask most leadership teams what their weekly meeting is for, and you'll get a shrug. It becomes whatever the loudest topic that week wants it to be — a status round-robin, a fire drill, a debate that eats the whole hour. The fix isn't willpower. It's a fixed agenda that the team runs the same way every single week, so nobody has to decide what the meeting is about in real time.

Why a fixed structure beats a flexible one

A flexible agenda sounds more responsive, but in practice it means every meeting is negotiated from scratch, and whoever talks first or loudest sets the direction. A fixed structure removes that negotiation. Everyone already knows what's coming, which means less time spent figuring out what to discuss and more time actually discussing it.

A weekly huddle agenda that works

This is close to the structure EOS calls an L10 meeting, and it holds up regardless of what framework you're running:

1. Segue (5 min). One good personal and one good professional update per person. This is the only unstructured part of the meeting, and it's on purpose — it's what makes the rest of the hour feel human instead of mechanical.

2. Scorecard (5 min). Go through the shared weekly numbers fast. The goal here isn't to discuss anything — it's to notice what's off track and send it to the issues list. A scorecard review that turns into a 20-minute debate has already broken the meeting.

3. Rock/goal review (5 min). Quick on-track / off-track status on this quarter's priorities. Same rule as the scorecard: flag it, don't solve it here.

4. Headlines (5 min). Customer and employee news the room needs to know about — a lost deal, a resignation, a big win. Information only, not discussion.

5. To-do list (5 min). Quick review of what was committed to last week. This is where accountability either happens or quietly stops happening.

6. IDS — Identify, Discuss, Solve (60 min). This is the actual meeting. Everything flagged in the first five sections, plus anything already on the issues list, gets tackled here — in priority order, one at a time, until it's actually solved, not just discussed.

7. Conclude (5 min). Recap new to-dos, rate the meeting, make sure anything that needs to go outside the room actually gets communicated.

The part everyone skips: rating the meeting

Ending with a quick 1-to-10 rating of the meeting itself sounds unnecessary until you actually try it. It surfaces the meetings that quietly went off the rails before that becomes the norm, and it gives the person running the meeting real-time feedback instead of finding out three months later that the team has stopped taking it seriously.

What to watch for

The two failure modes are almost always the same: letting the first five sections turn into discussion (they're status only — send problems to IDS instead), or letting IDS run out of time on the first issue raised instead of working the list in priority order. Both are fixable by whoever's running the meeting simply enforcing the agenda out loud: "let's capture that and get to it in IDS."

None of this requires software. A whiteboard and a timer will get you most of the way there. What software adds is a shared scoreboard everyone can see before the meeting starts, and an issues list that persists between meetings instead of living in someone's notebook.