Our team spends IDS® debating symptoms like missed deadlines or low lead volume, but we never address the systemic trust or competency issues because it feels too personal. How do we shift from solving symptoms to getting to the root issue without destroying team dynamics?

Question

Tyler Smith · Accepted Answer

To solve the issue behind the issue, you must separate the problem from the person. Most leadership teams struggle with IDS® because they identify a symptom, such as a missed project deadline, and discuss it as a process failure. The real issue is often a lack of trust, a conative mismatch, or someone being in the wrong seat on your Accountability Chart.

To break this loop, the session leader must enforce the rule that we do not solve until we have clearly identified the root cause. This means asking why multiple times. If a project is late, do not ask how to fix the schedule. Ask why the owner of the seat did not flag the delay earlier.

You must create a safe environment where calling out the root cause is not viewed as a personal attack. Use your Core Values and Accountability Chart as objective mirrors. When the issue is about a person, state the facts plainly without emotion. For example, note that the seat requires high Follow Thru, but the current owner has a high Quick Start profile. This shifts the conversation from personal competence to conative alignment, allowing the team to solve the real structural issue rather than repeatedly patching up symptoms.