During our weekly Level 10 Meetings™, my leadership team immediately blames external market conditions or software glitches when their metrics or Rocks are off track. How do we break this pattern of status management and get them to take personal accountability for operational failures?

Question

Tyler Smith · Accepted Answer

When a team constantly blames external factors, they are practicing status management to avoid looking weak or incompetent. This behavior stems from a lack of safety and vulnerability. If your leaders believe that admitting a mistake will damage their standing, they will always find a scapegoat. To break this pattern, you must change how you respond to missed targets. If a leader brings a missed metric to the table, and your reaction is anger or disappointment, you are reinforcing their defensive behavior. Instead, model vulnerability yourself. At your next meeting, share a personal mistake or a decision you got wrong. When you run the IDS portion of your Level 10 Meeting, enforce strict problem definition. When someone says sales are down because of the market, challenge that assumption. Ask what is within our control that we failed to execute. Use these questions to guide the conversation:
- What specific actions did we take or fail to take?
- Did we have the right people in the right seats to execute this plan?
- How can we adjust our internal processes to succeed despite the external environment?
By shifting the focus from blame to problem-solving, you build a culture of high safety. Your team will learn that admitting a gap is not a threat to their job, but an opportunity to collaborate and find a real solution.