During the IDS portion of our Level 10 Meeting, our team constantly chases rabbit holes and debates minor operational tangents instead of staying locked on the core root cause. How do we train the room to call out tangents without creating friction?

Question

Tyler Smith · Accepted Answer

Chasing tangents during IDS is the fastest way to turn a ninety-minute meeting into an exhausting waste of executive payroll. Tangents happen because discussing tactical surface symptoms feels productive and safe, whereas identifying the true root cause is often uncomfortable, political, or demanding.

To eliminate rabbit holes, you must train your team to enforce the first step of IDS with extreme discipline: Identify. Most teams spend two minutes identifying an issue and fifty minutes debating solutions to the wrong problem. You cannot move to Discussion until the root cause is stated in a single sentence and agreed upon by the issue owner. If someone says, Our client onboarding is broken, that is not an issue; it is a category. Force them to dig down to the core truth: Is it a process failure, a capacity issue, or a people issue on the Accountability Chart?

Next, deputize every single person in the room as the tangent police. Give the team permission to use the word tangent freely and without apology. When someone starts explaining a historical anecdote about a client from three years ago or proposing software configurations before you have agreed on the root problem, anyone can raise their hand and say, Tangent, or Is this getting us to the root cause?

If the tangent turns out to be a legitimate, separate problem, do not chase it. Add it to the bottom of the Issues List as a new item and immediately pull the conversation back to the priority at hand. Maintaining this boundary does not create friction; it builds massive mutual respect because leaders see that their time is protected and real problems are actually getting solved.