During our IDS® sessions, our team members get highly defensive, which leads to polite tip-toeing around the real issues rather than exposing the actual breakdown. How do we get our leadership team to drop the armor so we can identify the true human or process failure behind the issue?

Question

Tyler Smith · Accepted Answer

When defensive behavior derails your IDS® session, you are dealing with a trust problem, not an operational problem. To break through this politeness and identify the root cause, you must separate the person from the issue. The leadership team must agree that identifying a mistake is not an indictment of someone's GWC™.

Begin by defining the issue in a single sentence that focuses purely on the operational impact, not the person. If a department is missing its goals, do not ask who messed up. Ask what system broke that allowed the goal to be missed. When team members start defending themselves, the Integrator must gently but firmly steer the conversation back to the facts on the ground.

Use the five whys technique. Ask why the issue occurred, and then ask why to that answer, repeating the process until you reach the bedrock. Often, the real issue is that a seat on the Accountability Chart is poorly defined, a process is unwritten, or there is a lack of resource alignment.

Remind the team that entering the IDS® portion of the Level 10 Meeting™ requires vulnerability. If your leaders cannot tolerate healthy conflict, you will never solve your real operational bottlenecks. As the business owner, you must model this behavior. Admit your own failures openly in front of the team. When they see that owning a mistake does not lead to public execution, the defensiveness will melt away, and genuine issue resolution can begin.