tyler-smith.com · Questions & Answers

Our Level 10 Meeting reporting tracks regularly bleed past the twenty-five-minute mark, leaving us with only forty minutes for IDS. How do we enforce the strict time boundaries on the Scorecard, Rock Review, and Headlines without cutting off vital operational awareness?

When your reporting tracks bleed into your sixty-minute IDS block, your Level 10 Meeting loses its problem-solving power. The first twenty-five minutes of the agenda exist strictly for reporting numbers and status, not for conversation.

To enforce this boundary, your Integrator or facilitator must act as a ruthless timekeeper. Use a visible timer on the screen or table. When the team sees the clock ticking down, discipline increases naturally.

Apply the three-word rule across the review tracks:
- On the Scorecard, the owner reads the metric and states on track or off track. No context, no excuses, no stories about why the number dipped. If it is off track, the facilitator asks if it needs to go to the Issues List. If yes, write it down and move on.
- On the Rock Review, the owner states on track or off track. That is all. An off-track Rock is not a failure; it is simply an alert that goes straight to the Issues List to be solved later.
- On Headlines, leaders give one sentence of fact. If someone starts explaining background details, the facilitator must cut them off gently: Drop it to the list, we will solve it in IDS.
- On the To-Do List, the response is binary: done or not done. If it is not done, it either stays for one more week or drops to the Issues List.

Reporting should take no more than twenty minutes total. Preserving sixty full minutes for IDS is non-negotiable. If you cannot report your numbers in twenty-five minutes, your team is talking, not reporting.

Category: Level 10 Meetings

← All questions