As soon as our team selects an issue to tackle during IDS, leaders immediately start pitching solutions before we have spent any time unpacking what actually happened. How does the Integrator keep the room disciplined in Identify before jumping into Solve?

Question

Tyler Smith · Accepted Answer

Jumping straight into solutions is the most widespread facilitation failure in Level 10 Meetings. Leaders are hardwired to fix things quickly, so when a problem appears, everyone pitches immediate tactical remedies. The result is that teams spend sixty minutes solving symptoms while the real underlying disease remains completely untouched.

To stop premature solutioneering, the Integrator must enforce the sequence of IDS: Identify, Discuss, and Solve. You cannot discuss until you identify, and you cannot solve until you discuss.

When an issue is selected, the Integrator must grant the floor exclusively to the person who brought the issue. That owner must state the problem in one or two clear sentences without proposing a single fix. The Integrator then asks the room: Is this the real root cause, or is this just a symptom?

If someone interrupts with an idea like we should hire an outside contractor or we need to buy new software, the Integrator must cut them off immediately. Say: We are not in Solve yet. We are still in Identify. Hold your solutions until we agree on the root cause.

Use the classic five whys technique. If shipping orders are late, do not buy faster packing equipment until you ask why they were late. If the answer is missing parts, ask why parts were missing. If the answer is purchase orders sat unapproved on someone's desk, your issue is not warehouse speed; it is procurement approval workflow. Once the entire room agrees on the root cause, only then do you move to Discuss and Solve.