A VP of operations I coached a few years back could stand in front of her board and walk them through a three year plan without a single note. She read a P&L the way most people read a menu, and she knew to the decimal which of her people were carrying the number and which were not. The one thing she would not do, the task that slid across her calendar from Tuesday to Thursday to sometime next week, was sit down with a struggling senior analyst and act on what she already knew. She had the knowing down cold. It was the doing she kept setting aside, as though it belonged to someone else.
That gap is the whole subject. Accountability gets used as a synonym for responsibility, for owning an outcome and answering when it slips, and that is genuinely half of it. The half that goes missing is authority, the power to act on the thing you are answerable for. Real accountability is both at once, the responsibility to know a problem and the authority to do something about it sitting in the same pair of hands. Keep the two apart and you still have something you can call accountability. You just do not have the thing itself.
The failure rarely looks like a leader refusing to hold anyone responsible. It looks like the opposite. Responsibility gets pushed down with enthusiasm. Own your numbers, own your outcomes, the whole vocabulary of ownership travels downward without friction. What does not travel with it is the authority to act. People are made answerable for results they were never given the power to control, and then the word accountability gets stretched over the gap to make it look intentional.
You can see the split most clearly in what organizations do with the accountability conversation itself. Leadership IQ, a firm that sells leadership assessment and training and so has its own reasons to find managers wanting, surveyed 689 HR directors and executives in January and asked them to estimate what they see. The share of managers they would trust to handle a hard performance conversation with a genuinely difficult employee, without someone from HR in the room, came back at 35 percent.1 These are estimates rather than audited counts, and they carry the slant of a function built partly to manage this exact risk, so take them as the considered read of the people whose job is to watch managers manage. Their read is that two of every three managers hold the responsibility for a team they are not trusted to act on alone. The responsibility to know sits at the manager’s desk. The authority to act is kept one level up, in the room with HR.
The same firm put the share of managers who avoid or delay critical feedback at 67 percent,1 and it is tempting to read that as plain cowardice, a failure of nerve. Some of it is. But a manager who has been told, in a hundred small ways, that the authority to enforce a standard does not really sit with them will put the conversation off for a reason closer to logic than to fear. There is little point delivering a verdict you have not been authorized to act on. The avoidance is what responsibility without authority looks like from the inside.
Give a person the responsibility to know and withhold the authority to act, and you have not made them accountable. You have made them the one the failure can be pinned on.
The half nobody wants to hand over
This is also why, when Gallup asked more than twenty three thousand working adults to grade leaders across the seven competencies its research says define the job, creating accountability finished last of the seven.2 Fewer than half of leaders called themselves outstanding or exceptional at it, and their own managers put the figure at 30 percent.2 The six that scored higher, building relationships, developing people, leading change, inspiring others, thinking critically, and communicating clearly, can all be done while holding on to control. Accountability is the only one that asks a leader to give some away. To make a person genuinely accountable, you have to hand them the authority to act, which means handing over the outcome, which means it can now fail in someone else’s hands. That is the uncomfortable half, and it is the half that gets dropped.
I watched this for years as an agile coach. Teams would build elaborate machinery for visibility, the burndown charts and the status colors and the standups, and executives would point to all of it as proof that accountability was everywhere. It was not. Every one of those instruments tracked responsibility, who owed what by when, and not one of them moved a single decision downward. The team was fully answerable and almost entirely unauthorized, and the machinery made the arrangement look like rigor.
The cost shows up where you would expect. In the Gallup data, managers who rated their own leaders clearly strong on accountability were three times as likely to be engaged in their work, 51 percent against 17 percent.2 What moved the number was exactness, leaders who said plainly what good looked like and then let people own reaching it. Clarity of expectations, Gallup notes, is one of the engagement measures that has slipped the most in recent years,2 which is what you get from a generation of leaders fluent in assigning responsibility and reluctant to part with the authority that would make it real.
How to find out where it actually sits
If you want to know whether accountability lives in your organization or only in its language, pick a capable person a level or two down and ask them two questions. What are you responsible for. And what can you decide on your own in order to deliver it. When the first answer runs long and the second runs short, you have found the gap, and you have found the reason the person on the hook for the outcome keeps waiting on someone else to move.
The VP eventually did the thing she had been deferring, though not the way she had pictured it. She sat down with the analyst, told him plainly where he stood, and then did the part that actually mattered. She handed him a decision that had been hers, along with the standard it had to meet, and let him own reaching it. He got better fast. The missing piece had never really been the hard sentence. His responsibility for the work had been clear the whole time. The authority to shape it was what had stayed on her side of the desk.
So here is the question I would put to a senior team. Almost everyone in the room already believes they hold people accountable, so set that one aside. Ask instead where the authority stayed put while the responsibility moved down, and what the arrangement has been called in the years since. If you handed the outcome and the power to reach it to the same person tomorrow, whose control would you be giving up, and why does that feel like the risk rather than the fix?
If this hit a nerve, the book spends a good deal of time on the difference between people complying with a standard and people owning it, and why the second one cannot be installed through a tool or a ceremony. James and I lay out what we call the REAL framework, along with a progression that moves a team from doing what they are told toward genuinely owning the result, using the messy real examples of where it broke and what finally worked. If you want the longer version of the argument you just read, the link to Agile Sucks! (When You Do It Wrong) is right below.
Read Agile Sucks! (When You Do It Wrong) →References
- Murphy, M. (2026, January 16). The manager effectiveness crisis. Leadership IQ. (Survey of 689 HR directors and executives, January 2026, asked to estimate percentages based on their organizational experience; figures are HR perceptions, not audited counts. Leadership IQ sells leadership assessment and training.) https://www.leadershipiq.com/blogs/leadershipiq/the-manager-effectiveness-crisis ↩
- Harter, J., & Tatel, C. (2026, March 20). Accountability is leadership's greatest weakness. Gallup. (Survey of 23,068 U.S. working adults.) https://www.gallup.com/workplace/703379/accountability-leadership-greatest-weakness.aspx ↩