tyler-smith.com · Questions & Answers

Our leadership team gets bogged down in reporting status updates during the first thirty minutes of our Level 10 Meeting™, which leaves us with almost no time for actual IDS®. How do we aggressively streamline the check-in, Scorecard, Rock review, and To-Do list review so we can spend a full sixty minutes solving issues?

The first thirty minutes of your Level 10 Meeting™ are designed for reporting, not for solving. If you are discussing the story behind a red number on your Scorecard or explaining why a Rock is off track, you are breaking the meeting structure.

To fix this, enforce a strict rule of no storytelling during the first three sections. When reviewing the Scorecard, the owner of a red number simply says "drop it." That number goes straight to the Issues List. No explanations, no excuses. The same rule applies to the Rock review. If a Rock is off track, the owner says "off track," and it is placed on the Issues List.

During the To-Do list review, each item is either done, not done, or in progress. If it is not done, drop it to the Issues List if it is blocking progress, or carry it over one time.

By keeping these reporting sections completely binary, you can easily breeze through them in fifteen minutes. This preserves a full sixty minutes for IDS®. The magic of the Level 10 Meeting™ is not in the reporting; it is in your ability to solve your biggest problems as a team. Streamline the administration so you can focus on the hard work of solving.

Category: EOS Implementation

← All questions