Ownership Without Authority Fails

Category: Organisations and systems Responsibility without power guarantees frustration.

A new role was created to fix a recurring problem. Orders were going out late, and nobody could say exactly why. The work crossed three departments — sales took the order, operations built it, logistics shipped it — and each one was certain the delay belonged to one of the others. So someone senior had a sensible-sounding idea. They appointed a coordinator. One person, accountable end to end, whose job was to own the delivery date and make sure it was hit.

It was, on paper, exactly the right move. Give the orphaned outcome an owner. Make one throat available to choke. Everyone nodded.

The coordinator took it seriously. She mapped the whole flow, found the bottleneck quickly, and worked out what needed to change. Operations needed to reserve capacity for the awkward orders instead of leaving them to the end of the day. Sales needed to stop promising dates that the floor had never agreed to. Logistics needed to be told earlier when something fragile was coming. None of it was complicated. All of it was correct.

And none of it happened.

Because when she went to operations and asked them to reserve capacity, the operations manager — who did not report to her, whose own numbers were judged on throughput, not on her delivery date — listened politely and carried on as before. When she asked sales to stop over-promising, the sales director pointed out, not unreasonably, that hitting his targets was rather the point of his existence, and that her job was to make the dates work, not to make his harder. She could ask. She could escalate. She could send increasingly careful emails with increasingly senior people copied in. What she could not do was decide. She owned the outcome completely and controlled none of the inputs to it.

So the dates kept slipping, and now there was a difference. Before, the failure had belonged to no one and everyone. Now it had a name. Hers. She was the one accountable for a number she had never been given the power to move, and when it moved the wrong way, the question that came down was always the same: what was she doing about it? She was doing everything she could. Everything she could was asking people who could say no, and watching them say it.

A year later she left, and was quietly regarded, on her way out, as someone who hadn’t quite been up to the job.

The Principle

When you make someone responsible for an outcome but withhold the authority to shape it, you have not delegated the problem — you have relocated the blame. Accountability and authority are two halves of the same instrument. Separate them, and neither works. The person with the responsibility cannot act; the people who can act have no responsibility. The outcome falls into the gap between them, exactly where it was before, except now there is someone standing over it whose name is attached to its failure.

Ownership is the right to decide as much as it is the duty to deliver. Strip out the deciding and what is left is not ownership at all. It is exposure.

Why It Is Inevitable

This pattern is not a mistake people make once and learn from. It is the default, and it recurs because the move that creates it feels like good management.

When a cross-cutting problem appears, the instinct to give it an owner is correct. The instinct is so correct that it tends to stop there. Naming the owner feels like the hard part — it is visible, it is decisive, it can be announced — and so the harder, quieter part gets skipped. Granting the owner real authority means taking authority away from someone else. It means telling the operations manager that, on this matter, the coordinator’s call overrides his. It means giving the new role budget, or hiring rights, or a veto, or a seat where decisions are actually made. Every one of those is a transfer of power away from people who currently hold it and would rather keep it.

So the easy half gets done and the hard half gets deferred. The responsibility is handed over in a meeting; the authority is supposed to “come with the role” or “develop over time” or be earned through influence. Influence is offered as a substitute for power, which is a polite way of telling someone to achieve through persuasion what they have not been given the standing to require.

It is inevitable for a second reason, too. Authority is concrete and accountability is cheap. You can hand someone accountability for free — it costs the organisation nothing to write “owns the delivery date” next to a name. Authority has a price, paid by whoever loses it. Of course the free thing gets distributed liberally and the expensive thing gets hoarded. That is not malice. It is gravity.

How It Shows Up

• A role exists “to drive” or “to coordinate” or “to be the single point of accountability” for something, with no decision rights attached to it.
• The owner of an outcome spends most of their time escalating, persuading, and copying senior people in — because asking is the only lever they have.
• Responsibility crosses departmental lines; authority stops at them.
• “You own this” arrives without “and here is what you can now decide.”
• When the outcome fails, the question is what the owner did about it — never whether the owner was ever in a position to do anything about it.
• The people who can actually change the inputs face no consequence when the outcome misses, because the miss belongs to someone else.
• Job titles contain words like lead, champion, or owner for people who cannot direct a single resource.

Why It Causes Damage

The first damage is the obvious one: the outcome still fails. Giving a problem an owner who cannot act does not solve the problem; it just gives the failure a face. The underlying causes — the unreserved capacity, the over-promised dates, the late warnings — sit exactly where they were, untouched, because the only person now motivated to fix them is the one person without the power to.

The second damage is quieter and worse. You burn good people. The role of responsible-but-powerless is genuinely one of the most demoralising positions an organisation can put someone in. They can see what needs to happen. They are judged on whether it happens. And they are denied the means to make it happen. That is not a stretch assignment; it is a treadmill wired to a scoreboard. The capable people who take these roles do not fail quietly and move on — they exhaust themselves first, learn that effort and outcome have been deliberately decoupled, and then either leave or stop trying. Either way the organisation concludes that the person wasn’t strong enough, and reaches for another one, and does the same thing again.

The third damage is that the real lesson gets mislearned. The failure is read as a failure of the individual, not of the structure. So the structure survives. The next coordinator inherits the same impossible shape, and the organisation slowly accumulates evidence that “this kind of role never works” — when what never works is the specific cruelty of holding someone to account for a result they were never permitted to control.

And there is a fourth, subtler cost. Once people watch a colleague get held responsible for something they couldn’t influence, they learn to refuse that kind of ownership. The capable ones start declining the orphaned outcomes, because they have seen what accepting one does to you. The problems that most need an owner become the ones nobody sensible will touch.

How To Counter It

• Hand authority and accountability together, in the same breath, or hand neither. When you say “you own this,” the very next sentence must be “and here is what you can now decide, spend, and overrule.” If you cannot finish that sentence, you are not delegating — stop.
• Name the specific powers, not the vague mandate. “Drive alignment” is not authority. “Your call on sequencing overrides the floor’s, you control this budget line, you can hold the ship date and require sales to renegotiate” is authority. Be concrete enough that the people who must now defer to the owner understand that they must.
• Take the power visibly from where it currently sits. Authority that is granted privately to the owner but never communicated to the people who hold it changes nothing. The operations manager has to be told, by someone he answers to, that this call is now hers. Otherwise she has a title and he has the actual control.
• Match the consequence to the lever. If the outcome can only be moved by people other than the owner, then those people must carry part of the accountability too. A miss should land on whoever could have prevented it, not only on whoever was made to watch it.
• When you can’t grant the authority, don’t grant the responsibility either — fix the problem at the level that holds the power. Sometimes the honest answer is that the only person who can own this outcome is the executive over all three departments, because they are the only one who can direct all three. Then it is their job, not a coordinator’s. Pushing it down to someone without the reach is just laundering a decision you don’t want to make.
• Audit your existing roles for the gap. Look at anyone in your organisation whose title says owner or lead. Ask, for each, what they can actually decide without asking permission. The ones whose honest answer is “nothing” are the ones you are quietly setting up to fail.

What Good Looks Like

Good looks like a role where, the moment you describe what someone is accountable for, you can immediately and specifically describe what they are now empowered to do about it — and the two descriptions match. Where the power to act and the duty to deliver sit in the same pair of hands. Where the people whose work feeds the outcome know, clearly and from above, that on this matter the owner’s call carries.

It looks like an organisation that, faced with a cross-cutting problem, asks the uncomfortable second question instead of stopping at the comfortable first one. Not just who should own this? but what would they need the authority to do, and am I actually willing to take that authority from where it currently lives and give it to them? If the answer to the second question is no, good looks like having the honesty to keep the problem at the level where the power already is, rather than handing the name of a failure to someone junior and calling it delegation.

And it looks like a place where, when one of these roles does fail, the first instinct is to examine the shape of the role before blaming the person who stood in it. Where someone asks whether the job was ever winnable, and is willing to hear that it wasn’t.

The outcome still has an owner. The difference is that the owner can actually own it.

A Reflective Question

Think of something you have made someone accountable for. If they came to you tomorrow and said I cannot make this happen because I need to change something I have no power to change — would they be making an excuse, or would they be telling you the exact truth about the role you gave them?