During IDS, two department heads immediately get defensive and point fingers at each other's teams. How does the Integrator run IDS to strip out personal emotion and isolate the real operational breakdown?

Question

Tyler Smith · Accepted Answer

When department heads get defensive during IDS, it usually means the issue was framed around blame instead of structural friction. Defensive posturing happens when someone brings a personal grievance to the table disguised as an operational topic. The Integrator must step in immediately and stop the ping-pong debate before it drains the room.

First, isolate the Identify step. Do not allow anyone to discuss solutions or defend their department until the team agrees on a single, neutral sentence that defines the problem. Ask the person who raised the issue to restate it without using anyone's name or department title. If they cannot state the root cause in one sentence, they do not understand the issue yet.

Second, filter the problem through the Accountability Chart. Every operational breakdown belongs to a seat, not a personality. Look at the five major roles defined for each seat. Did someone step outside their lane, did someone drop an agreed-upon responsibility, or is the Accountability Chart missing a clear handoff between two functions?

Third, check the process. Most interdepartmental fights are caused by broken handoffs, not bad intent. If marketing generates leads that sales cannot close, the friction is usually an undefined qualification metric, not a lazy sales rep. When the Integrator anchors IDS to structural seats and core processes, personal defensiveness evaporates because the room is working on the system, not attacking a colleague.