Our executives get defensive and take it personally whenever a peer points out an issue originating in their department, which kills honest debate. How do we train our leadership team to welcome cross-functional scrutiny during IDS without sparking personal feuds?

Question

Tyler Smith · Accepted Answer

Defensiveness occurs when leadership team members view themselves as protective heads of personal fiefdoms rather than members of a single executive unit. When an operations leader points out that sales is closing bad-fit clients, a defensive sales leader hears an attack on their competence rather than an objective issue affecting the health of the business.

You must re-establish the first principle of any healthy leadership team: the leadership team is your first team. Your loyalty is to the enterprise and the V/TO, not your departmental staff. Break this defensiveness by enforcing strict discipline during the IDS process in your Level 10 Meeting.

First, insist that every issue added to the list is stated as an objective fact about a system, a process, or a metric, never an accusation against a person. Second, require the person presenting the issue to identify the root cause before opening the floor to discussion. If an executive responds defensively, the Integrator must immediately intervene and reset the boundary by asking: what is best for the company here, regardless of department pride?

Building vulnerability-based trust takes time and deliberate practice. Start your quarterly meetings with vulnerability exercises where leaders openly share their biggest business mistakes and areas where they need peer help. When leaders see that admitting a breakdown leads to peer support rather than punishment, defensiveness disappears and true functional collaboration begins.