Whenever we drop an issue on the Level 10 Meeting Issues List that involves operational errors, the responsible leader becomes defensive and takes it personally. How do we depersonalize issues during IDS?

Question

Tyler Smith · Accepted Answer

When operational mistakes hit the Issues List, insecure or defensive leaders often treat it as a personal attack. If defensiveness is tolerated, your Level 10 Meeting will devolve into political posturing, and your team will stop raising critical problems.

The remedy begins with language and framing. In EOS, issues do not belong to people; they belong to the company. The facilitator must ensure that issues are named neutrally on the board. For example, instead of writing Marketing failed to deliver leads, write Lead generation pacing behind target. Depersonalizing the headline allows the team to attack the problem collaboratively rather than attacking a colleague.

Next, reinforce that the goal of IDS is root-cause discovery, not assigning blame. If a leader starts justifying or making excuses, the facilitator should step in: We are not here to litigate the past. We are here to fix the process so this cannot happen again. What part of our system failed?

If the defensiveness continues, address it outside the meeting. The Integrator or Visionary must hold a direct conversation with that leader. Remind them of the company Core Values and the need for open, honest vulnerability. A leader on the Accountability Chart must have the maturity to admit when their seat is struggling.

If an executive cannot separate their ego from operational performance, they lack the emotional capacity for high-growth execution and may be in the wrong seat.