Leadership That Works

No platitudes. No theater. Just practical, bullsh*t-free insights on work, life, and leadership.

Subscribe Leadership Without the Bullsh*t cover image

Accountability is Kryptonite: Why Leaders and ICs Alike Try to Resist

Accountability feels like kryptonite not because it destroys, but because it exposes. It turns intentions into commitments, making results visible and fixed—revealing whether decisions, promises, and deliveries truly align.

Accountability is Kryptonite: Why Leaders and ICs Alike Try to Resist
Photo by Patrik Bloudek / Unsplash

Accountability is something leaders and individual contributors alike resist. Accountability is turning ideas and good intentions into explicit commitments, making both successes and failures visible to all. This avoidance isn't rooted in incompetence, but in the discomfort of two defining traits of true accountability: exposure and finality.

Exposure is the primary driver of this aversion. When accountability is formalized—written down, time-bound, and tied to specific names—it creates public, documented visibility into whether you decided, committed to, and delivered. There’s nowhere to hide. Once you sign your name to a decision or deliverable, everyone knows what you promised. The secondary driver is finality: once the outcome is measured, the result is fixed. And if you have to change course after the fact, even for good reasons, there’s the added reputational hazard of looking indecisive or incompetent.

The fear is symmetrical: the public record makes it harder to spin a narrative, shift the goalposts, or deflect responsibility when things go sideways.

This aversion crosses titles and pay grades. Leaders don’t want their own misses to be on record any more than their teams do. The fear is symmetrical: the public record makes it harder to spin a narrative, shift the goalposts, or deflect responsibility when things go sideways.

The difference comes in how people try to avoid it—and this is where the contrast between consultants and in-house operators is revealing. Consultants live in an environment where exposure is the norm. Their work is scoped, priced, and delivered against explicit commitments. They’re used to putting things in writing, defining success criteria, and having clients evaluate them against the contract. When they avoid accountability, it’s often to protect scope flexibility or margin—delaying specifics, keeping options open, or negotiating changes midstream to protect profitability.

Effort gets emphasized over outcomes because, in many internal cultures, hard work still counts for something even if the numbers don’t add up.

In-house staff, on the other hand, often work in a softer accountability climate. Commitments may be verbal, success criteria vague, and performance reviews as much about relationships as results. When they dodge accountability, it’s less about margin protection and more about political survivability—keeping deliverables informal, spreading responsibility across teams, or citing shifting priorities to reframe a miss as a strategic pivot. Effort gets emphasized over outcomes because, in many internal cultures, hard work still counts for something even if the numbers don’t add up.

Whether you’re in the boardroom or the build room, the patterns are familiar. Before commitment, the resistance shows up as calls for flexibility, arguments against “process overhead,” or cultural appeals to agility and trust. After commitment, the defenses shift—reinterpreting goals, blaming dependencies, or claiming partial credit. The intent is the same: to dull the sting of exposure and sidestep the permanence of the record.

The truth is, accountability isn’t kryptonite because it’s fatal—it’s kryptonite because it’s revealing. It shows, without filter or excuse, whether decisions, commitments, and deliveries match up. And for people unaccustomed to that level of clarity—especially those who’ve spent a career working in its absence—it can feel radioactive.

Al Newkirk profile image Al Newkirk
I'm an engineering leader and mentor who scales teams and systems in high-growth technology companies. I write about leadership and execution, in work and in life, with practical, bullsh*t-free insights for leaders and operators.