Some of our newer leadership team members want to reorganize our Level 10 Meeting™ agenda, suggesting we move the IDS® portion to the beginning of the meeting while our minds are fresh, or skip the reporting segments entirely when we have heavy issues. How do we defend the integrity of the standard EOS® agenda sequence against this drift?

Question

Tyler Smith · Accepted Answer

The sequence of the Level 10 Meeting™ is not arbitrary, and letting your team edit or rearrange it is a recipe for operational chaos. The agenda is specifically engineered to transition your mind from the daily grind to high-level strategic alignment. Changing the order undercuts the psychology of the meeting.

Starting with the segue forces the team to clear their heads and transition into the room. The reporting review, which includes the Scorecard, Rock progress, and Headlines, gives you an objective snapshot of the business. This sequence is critical because you cannot solve issues effectively in IDS® without first looking at the data. If you jump straight into problem-solving, you will end up solving the wrong issues based on emotion rather than objective facts.

Skipping the reporting segments to save time for a heavy Issues List is another common trap. This creates blind spots, as critical metrics or failing Rocks might go unnoticed for another week. The reporting section must remain a non-negotiable weekly check.

If a team member pushes to modify the agenda, remind them that the Level 10 Meeting™ structure has been proven across thousands of companies. Keep the reporting section to its tight twenty-minute limit by shutting down any discussion. If a number or Rock is off, drop it to the list. This discipline preserves the full fifty minutes for IDS® without compromising your visibility into the operational health of the business.