Responsibility and authority are not the same thing

Earlier this week I wrote about how ownership often looks clear on paper but becomes ambiguous at the moment of interaction. Responsibility and authority are not the same thing. A team may be accountable for an outcome, yet lack the authority to change the conditions required to achieve it. They are asked to improve speed, but another group controls the pipeline. They are measured on customer experience, but priorities are set elsewhere. They are expected to reduce incidents, but key technical decisions sit outside their remit. So responsibility sits in one place, decision rights sit in another.

When that happens, organisations compensate with coordination; more meetings, escalations, status chasing, dependency management and therefore slower decisions.

Clear ownership is not about centralising every decision. It is about coherence between three things:

1. Who is expected to deliver the outcome
2. Who can make meaningful decisions
3. Who carries the consequences of those decisions

When those align, teams move with confidence. When they do not, motion increases while progress slows. A useful exercise: take one recurring frustrating decision and ask:

- Who proposes it?
- Who must approve it?
- Who is impacted if it fails?
- Who can delay it indefinitely?

If the answers point to four different places, you may have found a constraint hiding in plain sight. Telling teams to “take ownership” rarely solves this. Designing ownership properly often does.