In the spring of 2026, Gallup published the results of a survey in which leaders rated their own performance across seven core competencies. Managers were asked to rate the same leaders. The pattern was consistent with what Gallup has found before: managers tend to think less of their leaders than leaders think of themselves, often by 20 percentage points or more across six categories. On accountability, something different happened. The gap closed. Leaders said they were bad at it. Managers agreed. Both groups, independently, named it the lowest-rated competency.

What followed in most organizations was more infrastructure. New OKR templates. A revised performance review cycle. Behavioral anchors on every competency descriptor. All of it designed to produce accountability through structure, built on an assumption that rarely gets examined: that people fail to be accountable because the system has not asked them clearly enough.

What the Infrastructure Response Actually Produces

When organizations add accountability infrastructure, they produce compliance. Someone hits the metric. Someone files the update. Someone shows up to the review with the right numbers and the right framing. The visible behavior looks like accountability, the scorecard improves, and the underlying problem stays exactly where it was.

This keeps happening because the feedback loop is slow. You install the system in Q1. Behavior changes visibly by Q2. The cultural problem, now somewhat hidden, resurfaces 18 months later in a different shape. By then, the system has been credited for the improvement.

Accountability infrastructure answers the question: did people do the required thing? Accountability culture answers a different question entirely: did people do the right thing when no one was checking?

The Three Rungs, and Why Most Organizations Live on the First

The Enos Progression, which I work through in detail in Agile Sucks! (When You Do It Wrong), maps three distinct points: compliance, commitment, and ownership. Compliance means doing the thing because the system requires it. Commitment means caring about the outcome. Ownership means holding the result regardless of what the system specifies, even when the outcome reflects badly on you, even when no one is watching.

Most accountability infrastructure is designed to produce compliance. That is fine as a floor. It has nothing to do with the ceiling. Organizations that confuse the two keep building more sophisticated compliance environments and wondering why ownership remains elusive. People in those organizations learn to manage the appearance of accountability. They hit the metric. They frame the miss. They file the update with the language that keeps everyone comfortable. The system reads this as accountability and scores it accordingly.

What Makes Accountability Worth Choosing

People choose accountability when a specific set of cultural conditions is present. Surfacing a problem has to cost less than hiding it. The person who raised the bad news last quarter has to still be in the room and still taken seriously. The post-mortem, if there is one, has to actually examine what happened, not distribute blame efficiently.

These conditions do not appear in a policy. They are the accumulated effect of a thousand smaller decisions: what got reinforced when someone said they did not know the answer, whether the leader who admitted the miss got a fair hearing or got managed out, what the senior team's response communicated the last time someone said the thing no one wanted to hear.

The Gallup data makes the cost of getting this wrong visible. Managers whose leaders were rated exceptional at creating accountability were three times as likely to be engaged as those whose leaders were not: 51% versus 17%. That is not a marginal difference. It is the distance between an organization where accountability is real and one where the energy has been diverted into performing it. Employee engagement has been declining in recent years, and Gallup notes that the element that has dropped most is clarity of expectations, which is directly tied to whether accountability is actually present in the culture.

The Question That Does Not Get Asked

Most senior leaders who encounter low accountability scores ask how they can hold people accountable more effectively. Kendra Okposo's piece in HBR this April, "Accountability Must Be Chosen, Not Mandated", makes the harder point: tightening controls when performance slips is the instinct, and it is also precisely what produces more compliance and less ownership. You cannot require someone to choose a thing. You can only change whether choosing it makes sense from where they are standing.

In a culture that equates admitting uncertainty with weakness, accountability is career-limiting. In a culture that promoted the person who hit the number regardless of how, the incentive to own a complicated outcome is low. More process in that environment produces more elaborate performances. The scorecard looks better. The underlying culture deepens.

The question senior leaders rarely ask is whether their culture has made accountability worth choosing at all. Whether the people in their organization would be rational to step forward and own something. The clarity of the ask is the easy part. What determines whether someone steps forward is the response they would get if they did, and whether it would make them glad they tried.

When something goes wrong in your organization, what does the first conversation look like? Who speaks first, and what do they say?