When our leadership team runs IDS, we constantly debate surface-level complaints instead of solving the real problem. How do we drill down to the issue behind the issue?

Question

Tyler Smith · Accepted Answer

Most leadership teams waste forty-five minutes treating symptoms because peeling back the layers exposes uncomfortable truths about performance, capability, or unclear accountability. When a team argues about why a client deliverable was three days late, the late deliverable is almost never the issue. It is merely the smoke. The fire is that the account manager does not understand their seat, the handoff process between sales and delivery is broken, or someone lacks GWC.

To find the issue behind the issue, the Integrator must enforce ruthless discipline during the Identify phase. Never move into Discuss until the issue is stated in one clear, objective sentence. The person raising the issue must state it plainly without five minutes of backstory. Once stated, the team must ask why four or five times before discussion starts. Why was the deliverable late? Because engineering did not receive the specs. Why were specs late? Because the client onboarding form was incomplete. Why was it incomplete? Because sales never required the client to fill it out before signing. Now you have the root issue: sales handoff protocols are not Followed by All.

Solving the root cause is often uncomfortable because it points directly to process failure or seat mismatch. If your IDS sessions end with vague action items like communicate better, you never identified the real issue. Real IDS ends with clear, singular accountability: one owner, one specific deadline, and a structural fix so the problem never returns.