During IDS in our weekly Level 10 Meeting, our discussions constantly get derailed by minor operational tangents and rabbit holes that burn thirty minutes without solving the real problem. How does the facilitator kill these distractions?

Question

Tyler Smith · Accepted Answer

Tangents happen during IDS because identifying the real root cause of a problem is uncomfortable, while discussing surface-level symptoms is easy. Teams will gladly waste thirty minutes arguing about a broken software setting rather than confronting the fact that a department head is failing to train their people.

The facilitator must act as a ruthless guardian of the topic. The moment someone introduces a secondary issue, historical grievance, or unrelated procedural detail, the facilitator must interrupt. Use a simple framework: "Is this point directly solving the root cause of the issue we prioritized, or is this a separate issue?"

If it is a separate issue, write it at the bottom of the Issues List and pull the conversation back immediately. Do not worry about being overly polite; prioritize being effective for the business.

Another powerful tactic is demanding a clear definition of the issue before anyone proposes solutions. Spend the majority of your time identifying the root cause. When the team agrees on the exact problem, the discussion stays focused and the solution takes five minutes.