During the first fifteen minutes of our Level 10 Meeting, our leaders consistently give long, contextual stories explaining their Scorecard metrics and Rock updates instead of keeping them binary. How do we eliminate this storytelling bloat?

Question

Tyler Smith · Accepted Answer

The first three sections of the Level 10 Meeting (Segue, Scorecard, and Rocks) are designed to be administrative and fast. They are meant to take less than fifteen minutes combined. When leaders start sharing stories, explaining why a number is red, or detailing the history of a Rock, they are committing meeting waste and eating into your critical problem solving time. To eliminate this bloat, the facilitator must enforce a strict, binary communication standard. When reviewing the Scorecard, the only acceptable responses are On track or Off track. When reviewing Rocks, the only acceptable responses are On track or Off track. Do not allow explanations, excuses, or updates. If a metric is red or a Rock is off track, the facilitator must immediately direct the owner to drop it to the Issues List. Say, That is an issue, let us drop it, and move to the next item. Explain to your team that the time for context and discussion is during the IDS portion of the meeting, not during the review. By cutting off storytelling early, you protect your sixty minute IDS block. This structure forces your leaders to be concise and ensures you spend your time actually solving problems rather than talking about them.