During our quarterly reviews, one of my key leaders becomes extremely defensive whenever their off-track scorecard metrics or Rocks are discussed, turning constructive feedback into a personal conflict. How do I handle this resistance using our operating system?
To effectively address defensiveness during performance discussions, you must shift the conversation from personal criticism to objective data and conative alignment. Defensiveness often stems from a fundamental human need for status management. As Daniel Coyle's research in The Culture Code highlights, individuals revert to self-preservation when their status or safety feels threatened, which can actively stifle collaboration and open dialogue.
To overcome this, you need to cultivate a high-safety environment within your team. This involves clearly separating the person from the seat they occupy.
Strategies for Addressing Defensiveness
Here's how to manage these critical conversations using your operating system:
• Ground Feedback in Data: Always ensure your feedback is rooted in objective information from your scorecard and the established standards of your Accountability Chart. When a Rock or metric is off-track, avoid accusatory language or asking "why did you fail?". Instead, frame the discussion around the barriers they encountered. This fosters a problem-solving mindset rather than one focused on blame. If the issue impacts other departments, bring it to your next [Level 10 Meeting™](/qa/how-to-review-scorecard-under-five-minutes) for IDS® (Identify, Discuss, Solve) with the wider team.
• Understand Conative Stress: Leverage their Kolbe A Index profile to determine if they are experiencing conative stress. A leader compelled to solve problems in a manner that conflicts with their natural instincts will frequently become defensive when they fall short. Understanding these profiles can illuminate underlying reasons for resistance, helping you to [analyze team conative profiles](/qa/analyze-kolbe-indexes-with-ai-project-teams) more effectively.
• Reinforce GWC™ and Core Values: Reaffirm that they GWC™ (Get it, Want it, have the Capacity to do it) their seat and align with your organization's core values. Emphasize that admitting an issue or asking for help is not a sign of weakness. Instead, it's a critical step in building a healthy business. By demonstrating that identifying issues leads to support rather than punishment, you establish the trust necessary for them to lower their guard and focus on effective execution.
This approach builds a foundation of psychological safety, encouraging open communication and problem-solving, even when discussing sensitive topics like [red scorecard metrics](/qa/handling-defensiveness-around-red-scorecard-metrics).
Related questions
• [How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [How do I handle a key department head who refuses to participate in offsite vulnerability or team-building exercises, claiming it is a waste of time?](/qa/handling-leader-resisting-offsite-vulnerability)
• [How do I know if my team actually trusts each other, or if they are just playing nice to avoid conflict?](/qa/leadership-team-trust-healthy-conflict)
Category: Leadership Team