Every time we attempt to run the IDS® process on deep operational inefficiencies, our leadership team gets defensive, turns it into a finger-pointing exercise, and we end up tabling the issue. How do we strip the emotion out of the Identify step so we can uncover the real root cause without destroying team trust?

Question

Tyler Smith · Accepted Answer

When your IDS® process devolves into defensiveness, you are identifying symptoms and personalities instead of systems. The key is to separate the person from the problem. When an issue is raised, the person who listed it must state the issue in one sentence. It cannot be a five-minute story or an accusation. For example, say the shipping department missed five deadlines this week, not that the shipping manager is lazy.

Next, the leadership team must ask clarifying questions, not state opinions. This forces the team into an analytical mindset rather than an emotional one. Before you move to Discuss, the team must agree on the actual root cause. If the issue is stated as a structural or process breakdown, defensiveness drops because you are auditing the seat and the process, not the human being.

If a team member becomes defensive, the Integrator must step in and redirect the focus back to the Accountability Chart™. Ask whether the seat has the right resources, whether the process is being followed, or if there is a gap in GWC™. This reframes the conversation around structural truth rather than personal failure. By the time you reach the Solve step, the solution should be an actionable to-do or a Rock that addresses the system, not a lecture to an individual. This discipline keeps the Level 10 Meeting™ productive and objective.