When our leadership team executes weekly Level 10 Meetings between our quarterly sessions, how do we prevent our IDS time from devolving into status updates and venting?

Question

Tyler Smith · Accepted Answer

Most leadership teams struggle with IDS because they treat it as an open forum to discuss personal feelings or give tactical status updates. That is why meetings feel sluggish and run past ninety minutes. The first seventeen minutes of your Level 10 Meeting are strictly operational reporting: Good News, Scorecard review, Rock review, Customer and Employee Headlines, and To-Do list follow-up. Zero storytelling is allowed during these segments. If a metric or Rock is off track, drop it directly to the Issues List with a short descriptor. Do not discuss it yet.

When you transition into your sixty-minute IDS block, prioritize ruthlessly. Never start at the top of the list simply because an item was logged first. Identify the top three issues that create the biggest operational drag on the business right now.

Spend the vast majority of your time on the Identify phase. Dig relentlessly until you uncover the root cause. Most stated problems are merely surface symptoms of a vague process, the wrong person in an Accountability Chart seat, or missing data. Once you articulate the real root cause, Discussing it should take only a couple of minutes. Everyone shares their view once without repeating points. The Solve phase must conclude with a clear, binary To-Do assigned to one person with a seven-day deadline. If an issue does not produce an actionable To-Do, you did not solve it; you simply talked about it.