During the IDS portion of our Level 10 Meeting, team members frequently hijack the discussion with long-winded personal anecdotes and hypothetical rabbit holes. How does the facilitator keep the team laser-focused on the root cause?

Question

Tyler Smith · Accepted Answer

When IDS discussions devolve into war stories and theoretical scenarios, it is almost always because the team rushed past the Identify step and began debating symptoms instead of uncovering the root cause. Real problem-solving requires surgical precision, not open-ended storytelling.

The facilitator must anchor the team in the first letter of IDS: Identify. Before anyone is allowed to suggest solutions or debate opinions, the facilitator must ask the issue owner: what is the specific problem, and what does a successful resolution look like? Keep pushing until the issue can be stated in one clear, unambiguous sentence. If the issue cannot be summarized in a single sentence, the team does not yet understand the root problem.

Once the discussion begins, the facilitator must act as a ruthless guardian against tangents. When a team member starts a sentence with that reminds me of three years ago or what if this hypothetical scenario happens next summer, the facilitator must step in immediately. Ask one direct question: how does that specific point help us solve the root cause on the whiteboard?

If the tangent represents a genuine separate issue, write it down at the bottom of the Issues List and pull the conversation back to the active priority. If it is merely conversational noise, shut it down. Keep the discussion focused strictly on the facts, the underlying operational failure, and the single decisive action needed to make the issue go away forever.