Why Your Level 10 Meeting Isn't Working (It's Usually Not the Agenda)

Symptom: everyone just reads updates

Cause: the scorecard is full of activity measures instead of numbers that force a decision. When nothing on the scorecard can go red in a way that matters, people fill the time with narration about what they did this week.

Quick test: for each line on the scorecard, ask what the team would actually do if it went off-track next week. If the honest answer is “nothing,” it isn't a measurable — it's a report.

Symptom: the same issues come back every week

Cause: issues are being discussed, not solved. A good IDS ends with a to-do and a named owner. A bad one ends with “let's keep an eye on that.”

Count how many items have been on the Issues List for three weeks or more. Those aren't meeting problems — they usually point to a seat on the accountability chart that's either empty or shared by two people, so nobody can actually decide.

Symptom: to-dos don't get done

• To-dos are vague (“look into pricing”) instead of finishable in seven days — anything that takes a month was a project, not a to-do
• To-dos have no single owner, so they belong to the room and therefore to nobody
• To-dos live in a tool nobody opens between meetings, so they're only remembered once a week, in the meeting where they're already late

Symptom: the founder does most of the talking

Cause: unclear roles. When the Visionary is also running the meeting, the room defers, and the meeting becomes a briefing with a fancy agenda. Running the L10 is an Integrator responsibility for a reason — the person who facilitates should be the person accountable for execution, not the person with the biggest opinions in the room.

Who actually owns the meeting

Name one person as responsible for the quality of the L10, not just for keeping time. They own scorecard hygiene, keep the Issues List honest, and chase to-dos between meetings. If that person is also the one avoiding hard conversations, the meeting will reflect it — and no agenda change will fix that.

A four-week diagnostic before you change anything

For the next four meetings, track four things: how many scorecard lines were off-track and actually acted on, how many issues were solved versus re-listed, what share of to-dos were closed within seven days, and who spoke the most.

The pattern usually points clearly to one of the symptoms above. Fix that input first. Changing the meeting format before you know which input is broken just gives you a new meeting with the same problem.

What a good L10 feels like

A meeting that is working tends to feel short on reporting and long on solving. Scorecard and Rock updates move quickly because people come prepared and only off-track items get discussion. Most of the time goes to the Issues List, and the team leaves with a handful of clear to-dos, each with one owner. People disagree openly in the room rather than afterwards in the hallway. And the same issues do not keep coming back, because they were actually solved the first time.

Preparing for the meeting

• Scorecard numbers updated before the meeting starts, not during it
• Rock status set to on-track or off-track ahead of time by each owner
• Issues added to the list during the week as they come up, not saved for the meeting
• Last week's to-dos marked done or not done before the meeting, so review takes a minute

Related reading