tyler-smith.com · Questions & Answers

Once we get into IDS, our debates constantly branch off into three different rabbit holes, and we end up arguing about secondary problems. How do we stop tangent traps and force the team to identify the true root cause first?

Tangent traps happen when your team rushes to solve a problem before everyone agrees on what the actual problem is. In the EOS framework, IDS stands for Identify, Discuss, and Solve. Teams that wander into rabbit holes spend ninety percent of their time discussing symptoms and zero percent of their time identifying the root cause.

The facilitator must anchor the team in the Identify step. When an issue is selected, the person who raised it must state the issue clearly in one or two sentences. If they take three minutes to explain it, they do not know what the issue is yet. The facilitator must stop them and ask: What is the core issue here? State it as a single sentence.

Once stated, do not jump into brainstorming solutions. Ask the room: Is that the real problem, or is that just a symptom of a deeper defect?

If someone launches into a tangent about a separate operational frustration, call it out immediately: That sounds like a valid issue, but it is not what we are solving right now. Do we need to add that to the bottom of the list, or keep focus on the topic in front of us?

Keep the team focused on digging down to the root cause. When you accurately identify the root issue, the discussion is short and the solution is obvious.

Category: Level 10 Meetings

← All questions