Our leadership team frequently wants to bypass the Scorecard, Rock review, and Headlines to jump straight into IDS because an urgent issue feels too critical to wait. Why must the Level 10 Meeting agenda sequence remain non-negotiable?

Question

Tyler Smith · Accepted Answer

Skipping the reporting section to attack an urgent issue is a rookie facilitation error. The first twenty-five minutes of the Level 10 Meeting are engineered to provide an objective, panoramic view of the business before a single issue is discussed. When you jump straight into solving a fire, you allow emotions and recency bias to dictate team priorities.

The agenda sequence serves three vital functions.

First, the Good News segue transitions the room from operational chaos to focused team alignment. It forces leaders to clear mental distractions and arrive present.

Second, reviewing the Scorecard, Rock progress, and Headlines takes only twenty minutes, but it systematically surfaces every broken metric and off-track priority across the entire company. An urgent issue that feels all-consuming might actually be minor compared to a core revenue driver that just went red on the Scorecard. If you skip reporting, those red metrics remain hidden, and you end up spending sixty minutes solving the loudest problem rather than the most critical problem.

Third, the reporting section is where the Issues List gets populated. You do not solve issues during Scorecard or Rock reviews; you simply drop off-track items down to the bottom of the agenda. Once you reach IDS, you prioritize the top three issues across the entire company, not just the one problem someone was stressed about at 8:55 AM.

If a true five-alarm disaster hits the company, handle it outside the meeting. But if you are sitting down for your weekly Level 10 Meeting, respect the pulse. Run the reporting sections strictly on time, build the comprehensive list, rank the top three, and then attack them with full context.