We prioritized our top issue during the Level 10 Meeting, but ten minutes into discussing it, our operations head brought up a secondary logistics issue. The team naturally followed that thread, and before we knew it, we solved a minor delivery problem but completely ran out of time to solve our top strategic bottleneck. How do we stop this IDS agenda drift?

Question

Tyler Smith · Accepted Answer

This is a classic failure of facilitation discipline. When you enter the Identify, Discuss, and Solve phase, you must focus exclusively on one issue at a time. The root cause is a lack of boundary control by your meeting facilitator, usually the Integrator.

To fix this, you need to implement a strict rule: only the owner of the prioritized issue is allowed to steer the conversation, and the facilitator must act as a hard guardrail. If another team member brings up a secondary topic or a related but distinct issue, the facilitator must immediately call a halt. They must state clearly that the secondary topic is a new issue and must be added to the bottom of the Issues List. Do not discuss it, do not debate it, just write it down and return to the primary issue.

Additionally, the facilitator needs to keep the team laser-focused on the Identify phase. Teams often drift because they jump to the Solve phase before truly agreeing on the core problem. If you spend five minutes ensuring you are all solving the exact same root problem, you will not drift into tangential issues. Keep your hands on the wheel, call out the drift the second it happens, and log those side issues for later.