During the Identify step of IDS, how does the Integrator stop the leadership team from debating surface symptoms so they can isolate the true systemic breakdown?

Question

Tyler Smith · Accepted Answer

Most leadership teams waste ninety percent of their meeting time arguing about secondary consequences rather than identifying root causes. If revenue is dropping in a key territory, the team instinctively debates marketing spend, salesperson motivation, or economic headwinds. Those are symptoms. If you try to solve symptoms, the issue will inevitably return to your Issues List three weeks later.

To locate the issue behind the issue during the Identify step, the Integrator must force radical brevity before anyone is allowed to discuss anything. Start by requiring the person who raised the issue to state the core problem in one or two sentences without telling a story. If they need two minutes of narrative context, they do not understand the problem yet.

Next, run the stated problem through three diagnostic filters:
- Is this an Accountability Chart flaw where roles and seats are vague or overlapping?
- Is this a Core Process flaw where a documented, simplified system was bypassed or missing?
- Is this a people issue where an individual fails the Core Values or does not GWC their seat?

Keep asking what caused that until the room traces the breakdown to one of those three categories. Do not allow the room to transition to Discuss until every leader nods and agrees on a single, clean root-cause sentence written on the whiteboard. When you identify the real structural break, the Discuss and Solve steps rarely take more than five minutes.