tyler-smith.com · Questions & Answers

Our Level 10 Meeting always derails during the sixty-minute IDS section because our team chases rabbit trails instead of staying on the prioritized issue. How does the Integrator strictly hold the room to one issue at a time without cutting off vital context?

The sixty-minute IDS® portion of the Level 10 Meeting™ falls apart when team members confuse context with opinion. Someone presents a genuine operational bottleneck, and within two minutes, three other leaders chime in with unrelated complaints, historical grievances, or premature solutions. It is the Integrator's job to protect the agenda and enforce ruthless conversational discipline.

The fix requires three practical rules from the meeting leader:

- Stop solutioning during the Identify step. Do not let anyone propose a fix until the team has stated the root problem in a single sentence that everyone agrees with.
- Intervene at the first tangent. The moment a leader begins a sentence with this reminds me of another problem, the Integrator must cut in and say that sounds like a separate issue; let us put it at the bottom of the list and finish this one first.
- Require the owner of the issue to speak first. The person who placed the item on the list must state the issue clearly, name who is involved, and state what outcome they need from the team.

Context should take ninety seconds, not fifteen minutes. If an issue requires extensive data analysis or a complex technical demo, the solution is not to debate it blindly for forty minutes. The solution is an action item assigning one or two leaders to research the facts and bring a clear proposal back to next week's meeting. Run IDS® like an operational surgery, not an open-mic brainstorming session.

Category: EOS Implementation

← All questions