During IDS, our team constantly gets trapped treating surface symptoms like interpersonal friction or communication gaps rather than digging into the root problem. What specific probing questions should the Integrator ask to uncover the true issue behind the issue?

Question

Tyler Smith · Accepted Answer

Most leadership teams burn valuable time in IDS debating symptoms because symptoms are loud, emotional, and visible. When someone brings an issue like customer service is not communicating with sales, that is rarely the real problem. If you jump into brainstorm mode immediately, you will create a band-aid policy that frustrates everyone and fails within a month.

The Integrator must halt discussion and probe until the root cause is exposed:

- Ask what the actual breakdown is: Demand a specific, recent example with facts rather than generalizations.
- Drill down with repeated whys: Ask why the communication failed, why the expectation was unclear, and why the team did not follow the standard workflow.
- Isolate person versus process: Determine whether this is a people issue or a process issue. If it is a process issue, ask which Core Process was skipped, broken, or undocumented. If it is a people issue, evaluate the seat holder against Core Values and GWC™ (Gets It, Wants It, Capacity to do it).
- Name the true issue in one sentence: Before discussing solutions, require the team to agree on a single sentence defining the core problem.

Once the true issue is identified, the discussion becomes short and the solution becomes obvious. You can only solve what you are willing to name clearly.