I have sat through a version of the same meeting more times than I can count. A leader stands up, puts the word accountability on a slide in large type, and announces the fix. There will be weekly scorecards now. Every deliverable gets a status color. Once a month, each director walks the executive team through what slipped and what they are doing about it. The room nods. People take notes. Six weeks later the dashboards are green, the reviews start on time, and the thing that was actually broken is exactly as broken as it was before.
What the leader wanted was for people to care about the result the way he did. The system he actually built rewarded something narrower, which was managing how the result looked. Those are two different products, and the second is what you get when you order the first.
The competency leaders rate themselves worst at
Gallup ran its quarterly workforce study last August and asked leaders to rate themselves across seven core competencies, then asked a separate sample of managers to rate the leaders above them.1 Creating accountability came in last for both groups. Less than half of leaders called themselves exceptional or outstanding at holding people responsible for strong performance. The managers who report to them put the figure at 30 percent. Accountability landed at the bottom of all seven competencies, and it was the one place where the two groups came closest to agreeing, which means every other competency showed an even wider gap between how leaders rate themselves and how their people rate them.1
Sit with that gap for a second. The leaders doing the holding already think they are mediocre at it, and the managers on the receiving end think it is worse. This is also the one competency that tracks most closely with whether anyone is engaged at all. Among managers who say their leader is genuinely good at accountability, 51 percent are engaged in their work, against 17 percent of everyone else.1 Three times the engagement, riding on the skill leaders are least sure they have.
So the urge to do something about it is sound. The trouble is what the something usually turns out to be.
Why the mandate produces the opposite of what it asks for
When results slip, the reflex is to tighten. More monitoring and firmer targets, with a harder edge in the review when something misses. The reflex backfires in a specific way, and the mechanism is worth stating plainly. The moment you install a structure whose purpose is to make someone accountable, you have told them something about how you see them. The message underneath it is that you did not believe they would carry the weight on their own. People hear that. A person who has just learned they are not trusted will give you exactly what the structure measures and not one inch past it.
Compliance stops the moment the pressure does. Ownership outlasts the pressure, because somewhere along the way the person decided the result was theirs to carry, and that decision is not one you can issue down a reporting line.
This is why the green dashboard lies. The status colors are real in the sense that someone updated them. What they do not tell you is whether anyone has decided the outcome belongs to them. A team busy protecting itself will hit every number you named while the number you forgot to name rots out of sight. That is not because the people are cynical. You built a game, and they are playing it correctly.
What moves a person from doing the task to owning the result
The shift I have watched work is slower and far less satisfying to announce. It starts with letting people set the commitment instead of receiving it, because a person will defend what they helped design and merely tolerate what they were handed. It needs enough safety that someone can come in and say the thing missed, here is why, here is what I am changing, without the conversation hardening into a hunt for who to blame. A workplace where the only safe move is to look accountable will hand you people who are very good at looking accountable. And it asks the leader to do the part that never fits on a scorecard, which is making sure each person can see how their piece reaches something a customer actually feels.
None of that shows up green by Friday. That is the catch, and it is the reason most leaders reach for the cadence instead. The cadence is visible the same afternoon. Ownership shows up a quarter later, in the problem someone surfaced before it caught fire, in the call a manager made without escalating because they understood it was theirs to make.
There is a progression worth keeping in front of you, one that runs from compliance to commitment to ownership. The reason it helps to name three stops instead of two is that nobody leaps straight to the last one. Compliance is where the mandate leaves you, and there is nothing wrong with having it as a floor. The trouble starts when a leader treats the floor as the finished building. The climb from there is the actual work, and it gets done by changing what the environment rewards, not by saying the word accountability in a larger font.
The leaders I have watched climb out of this did not do it with a better scorecard. What changed their teams was the week they stopped asking why a number slipped and started asking each person what they believed they actually owned, then sat through the uncomfortable quiet while people worked out that they were not sure. That silence is the real diagnostic. What do your people believe is theirs to carry, and would their answer match yours?
Zac Parker and James Wright work through that climb in Agile Sucks! (When You Do It Wrong), where the move from compliance to commitment to ownership is one of the ideas leaders most often try to shortcut. If the gap between a green dashboard and a team that actually owns its results is one you recognize, the book lays out how the better operators close it. https://a.co/d/bdUxZLw
Read Agile Sucks! (When You Do It Wrong) →References
- Harter, J., & Tatel, C. (2026, March 20). Accountability is leadership's greatest weakness. Gallup. https://www.gallup.com/workplace/703379/accountability-leadership-greatest-weakness.aspx ↩