Our Integrator struggles to keep our leadership team from going down rabbit holes during IDS, and we frequently burn thirty minutes debating minor technical details that do not solve the root cause. How does a facilitator kill tangents without shutting down necessary debate?

Question

Tyler Smith · Accepted Answer

Rabbit holes happen when a leadership team skips the Identify step of IDS and jumps straight into Discuss and Solve. The moment a symptom is named, team members start throwing out opinions and debating implementation details without agreeing on what problem they are actually trying to fix.

The facilitator must police the three letters of IDS ruthlessly:

- Identify: Do not allow discussion to begin until the issue owner states the problem in one or two clear sentences and the root cause is agreed upon by the room. If someone starts debating solutions during the Identify stage, the facilitator must cut them off: We are not solving yet. What is the core issue?
- Discuss: Discussion should only focus on the identified root cause. If someone brings up a related operational annoyance or a separate technical nuance, the facilitator must use the rabbit hole rule: Is this relevant to the root cause on the table, or is this a new issue? If it is a new issue, write it at the bottom of the list and pull the room back.
- Solve: Once the options are discussed, push for a decision. A solution is simply an agreed-upon plan that produces one or more binary To-Dos assigned to specific owners.

Good facilitation is not polite or passive. The team should agree in advance that the facilitator has total authority to call out tangents immediately. Cutting off a rabbit hole is not silencing debate; it is protecting the team's time so you can solve the problems that actually threaten the business.