Accountability

Strengths

• Identifies “root causes” in the system rather than just blaming individuals
• Prevents the leader from burning out by carrying the “weight of the world”
• Effective at analysing complex failures involving multiple departments
• Provides a realistic view of market or environmental constraints

Liabilities

• Can be perceived as “making excuses” or avoiding responsibility
• May foster a “victim culture” where the team feels powerless to change
• Reduces trust if stakeholders feel the leader is shifting the blame
• Might delay necessary personal growth by ignoring self-correction

Development tips if you lean left

• Use “I” statements more frequently: “I missed this,” rather than “The data was late.”
• Ask, “What is the one thing I could have done to change this outcome?”
• Practice the “extreme ownership” mindset: everything on your watch is yours.
• Apologise early and clearly when a commitment is missed.
• Focus on the “solution” you can control rather than the “problem” others caused.
• Identify your “blind spots” by asking for feedback after a failure.
• Accept that “explaining” a failure often sounds like “excusing” it to others.
• Model accountability by owning a small mistake publicly to build team trust.

Strengths

• Builds immense trust and loyalty within the team and with stakeholders
• Accelerates personal and organisational learning through self-reflection
• Empowers the team by demonstrating that they have agency over results
• Creates a high-performance culture where “excuses” are not the default

Liabilities

• May overlook genuine systemic issues by taking too much on personally
• Risk of “Hero Complex” where the leader tries to save every failing project
• Can lead to significant stress or burnout from carrying excessive guilt
• Might shield the team so much that they don’t learn from their own errors

Development tips if you lean right

• Distinguish between “My Fault” and “My Responsibility.”
• Ask the team to perform a “Post-Mortem” to identify systemic gaps.
• Practice delegating the *accountability* for a task, not just the task itself.
• Recognise when a failure was truly due to external “Black Swan” events.
• Allow team members to own their own mistakes so they can grow.
• Schedule “system checks” to ensure processes are supporting the people.
• Learn to say, “I am responsible for the result, but the system failed us here.”
• Balance self-critique with a focus on your team’s collective resilience.

If you lean toward externalising, you may:

• Begin a status update by explaining why the “market” or “IT” was the hurdle
• Focus on the “reasons” for a delay rather than the “result” of the delay
• Expect others to understand the “context” of your performance gaps
• Feel that you are often at the mercy of factors beyond your control

If you lean toward owning, you may:

• Say “The buck stops with me” and mean it
• Focus on “How do we fix this?” before “How did this happen?”
• Take public responsibility for the team’s misses and give them the credit for wins
• Hold yourself to a higher standard of discipline than you expect of others

Accountability helps when:

• Building a culture of integrity and high trust from scratch
• Leading through a public crisis or a major operational failure
• The organisation has become “lazy” or prone to finger-pointing
• Personal growth and “learning agility” are the primary goals

Accountability hurts when:

• A leader takes so much blame that they lose their professional “standing”
• Systemic flaws (like lack of budget) are ignored because the leader “muscles through”
• The leader becomes a “bottleneck” because they feel they must control every outcome
• High stress leads to “self-flagellation” instead of productive problem-solving