During our Level 10 Meeting, the team immediately jumps to brainstorming solutions before everyone actually agrees on what problem we are solving. What tactical rule keeps us in the Identify step of IDS until the real issue is exposed?

Question

Tyler Smith · Accepted Answer

Most leadership teams waste half of their Level 10 Meeting™ arguing about competing solutions because they never actually agreed on the problem. Someone raises an issue about missed shipping deadlines, and within thirty seconds three leaders are debating software upgrades, warehouse overtime, and carrier contracts. That is premature solving, and it guarantees the root issue survives.

To break this habit, the Integrator must install a strict procedural rule: no solutions are permitted until the issue is stated in one sentence and agreed upon by the room. The moment someone starts pitching an idea, the Integrator stops them and asks: what is the specific root issue behind the issue?

The person who placed the item on the Issues List must dig past the symptom. Missed shipping deadlines is not an issue; it is a symptom. The real issue is that the order entry process lacks quality control, allowing incomplete orders onto the warehouse floor. Once the owner articulates that single sentence, the Integrator polls the leadership team: do we all agree that order entry errors are the root issue?

Only when every head nods does the meeting transition from Identify to Discuss. In Discuss, team members state their perspective once without repeating themselves. In Solve, the team decides on an action step, assigns it to a single seat on the Accountability Chart, and logs a seven-day To-Do. If you police the transition between Identify and Discuss with ruthless discipline, your IDS® sessions will move three times faster and solve problems forever.