We consistently spend forty-five to fifty minutes on the Scorecard, Rock review, Headlines, and To-Dos, leaving barely half an hour for IDS. How do we ruthlessly compress the reporting section into twenty-five minutes?

Question

Tyler Smith · Accepted Answer

Spending forty-five minutes on reporting turns your Level 10 Meeting into a status update rather than a problem-solving engine. The first twenty-five minutes exist purely to spot issues, not to discuss them.

To hit the twenty-five minute mark, enforce the strict binary language of EOS:
- Scorecard: Read the measure and the number. If it missed the goal, the owner says drop it or leave it. No explanations, no excuses, no context. It takes five minutes.
- Rock Review: The owner says on track or off track. If it is off track, it drops to the Issues List. No stories about why it stalled. It takes five minutes.
- Customer and Employee Headlines: Share quick news. If an item requires action, drop it to the list. This takes five minutes.
- To-Do List: Read the task. The owner answers done or not done. If it is not done, it either rolls over one week or drops to the Issues List. It takes five minutes.

Notice that every section is just a reporting filter designed to populate the Issues List. The facilitator must cut off anyone who begins a sentence with because or the reason is. When you cut out storytelling, reporting takes exactly twenty minutes, leaving seventy full minutes to prioritize and solve your most critical business issues.