Ownership Without Authority

We’ve all heard it:

“You’re accountable for the service.”

Great. Now explain how that works when you don’t control:

• the infrastructure it runs on
• the team that builds it
• the budget that funds it
• the decisions that shape it

This is the accountability trap: responsibility without power.

We’ve encountered this before - it’s organisational theatre.

The rituals, titles, and frameworks that look like meaningful action but achieve very little. In this case, handing someone accountability without enablement, then wondering why they can’t deliver. It’s the organisational equivalent of giving someone a steering wheel with no connection to the wheels.

And it’s everywhere.

The RACI Delusion

RACI matrices promise clarity: Responsible, Accountable, Consulted, Informed.

In theory, beautiful.
In practice, a game of organisational hot potato.

Because when something goes wrong, everyone points to their box:

• “I’m just consulted - not my call.”
• “I’m informed - I didn’t know I was supposed to act.”
• “I’m responsible, but I don’t have authority to change anything.”

And the person marked accountable?
They’re holding the bag for a system they don’t control.

RACI doesn’t create ownership. It creates plausible deniability.

It maps reporting lines, not influence.
It shows structure, not flow.

Real ownership can’t be assigned in a spreadsheet.
It has to be enabled.

Authority Is Not Control

Here’s the uncomfortable truth: most services cross multiple boundaries.

They span:

• technology stacks
• business units
• vendor contracts
• geographic regions
• governance frameworks

No single person controls all the moving parts.

So when we say someone “owns” a service, we’re usually lying.

What we mean is: “You’re the person we’ll look too to fix it when it fails.”

Or more simply - who we can blame.

That’s not ownership. That’s a scapegoat with a job title.

Real ownership is about influence, not control.

It’s the ability to:

• see what’s happening across boundaries
• coordinate the people who do have authority
• make informed decisions even when you don’t hold all the levers
• create accountability through visibility, not hierarchy

You don’t need to control everything to own the outcome.
But you do need to see everything.

And that’s where most organisations fail.

The Accountability Trap

Let’s talk about what happens when we create accountability without enablement.

A “service owner” gets handed:

• a title
• maybe a budget (if they’re lucky)
• responsibility for uptime, performance, user satisfaction

But they don’t get:

• access to the teams that fix issues
• authority to prioritise changes
• visibility into dependencies
• influence over architectural decisions

They’re expected to answer questions like:

• “Why is this service slow?”
• “When will that feature be ready?”
• “What’s the risk if we deprecate this component?”

And the honest answer is: “I don’t know - because I can’t see it, and I can’t change it.”

That’s the trap.

We’ve given them accountability for an outcome they have no power to shape.

So what do they do?

They spend their time in meetings.
Negotiating. Escalating. Pleading.
Trying to create influence through sheer force of personality.

Exhausting. Ineffective. Unsustainable.

What Real Service Ownership Looks Like

Real service ownership isn’t about control.
It’s about coherence.

An owner doesn’t need to make every decision.
But they do need to:

1. See the whole service - not just their part, but the entire flow from request to outcome
2. Know the dependencies - what influences the service, and what the service influences
3. Coordinate across boundaries - bring the right people together at the right time
4. Make trade-offs visible - when priorities conflict, expose the choice clearly
5. Own the narrative - be the authoritative voice on service health, direction, and risk

Notice what’s missing: direct authority over people, budget, or infrastructure.

Because ownership is a relationship with the service, not a position in the hierarchy.

When the service is visible, ownership becomes possible.
When it’s fragmented across silos, ownership becomes fiction.

OSM: Making Ownership Real

This is where Organisational Service Management (OSM) changes the game.

OSM doesn’t pretend services can be owned by one person with total control.

Instead, it creates the conditions for ownership by making services visible, connected, and navigable.

The Service Intelligence Base (SIB)

The SIB is OSM’s answer to the visibility problem.

It’s a living model that shows:

• what the service actually is (not what we hoped it would be)
• who consumes it, who depends on it, who supports it
• what components enable it, and what risks threaten it
• where changes are happening, and what their impact might be

This isn’t a static diagram.
It’s a dynamic, federated view - constantly updated by events, signals, and real operational data.

When a service owner can see the service - truly see it - they don’t need authority over every component.

They can:

• spot issues before they escalate
• coordinate responses across teams
• make informed trade-offs
• communicate credibly with stakeholders

Visibility creates influence.
Influence enables ownership.

Ownership by Experience, Not by Org Chart

OSM flips the traditional model.

Instead of asking “Who reports to whom?”, it asks “Who experiences this service?”

Ownership follows the service boundary, not the reporting line.

That means:

• the owner is accountable for the outcome, not the components
• teams contribute to the service, but don’t own fragments of it
• decisions are made in the context of service flow, not departmental priorities

This is a fundamental shift.

It requires organisations to stop treating services as collections of tickets, projects, or infrastructure - and start treating them as living systems with identifiable outcomes.

When we do that, ownership becomes coherent.

The Influence Model

So how does ownership without authority actually work?

Through structured influence.

An effective service owner in the OSM model:

Creates Sightlines

They ensure the service is visible to everyone who needs to see it.
Not buried in tribal knowledge or scattered across systems - but represented in a shared, credible model.

Facilitates Coordination

They bring the right people into the conversation - not through endless meetings, but through service-centric rituals that focus on flow, health, and outcomes.

Exposes Trade-Offs

When priorities conflict (and they always do), the owner makes the choice explicit:
“We can have speed or stability - which matters more right now?”

Owns the Story

They are the authoritative source on service state.
Not because they control everything, but because they see everything.

Builds Trust Through Transparency

They admit uncertainty.
They share what’s known, what’s assumed, and what needs to be learned.
That credibility earns influence.

This is ownership as stewardship, not dominion.

What This Means in Practice

Let’s ground this with an example.

Imagine a “Customer Onboarding” service.

It involves:

• a CRM system (owned by Sales)
• an identity platform (owned by Security)
• a provisioning workflow (owned by IT)
• training content (owned by Learning & Development)
• a billing integration (owned by Finance)

No single person controls all those pieces.

In a traditional model, the “service owner” spends their life chasing updates:

• emailing teams for status
• sitting in five different governance meetings
• trying to predict impact when something changes

In an OSM model with a SIB:

• The service is modelled as a single entity with visible dependencies
• Each component team updates their part in real-time (via automation or lightweight input)
• The service owner sees the whole picture in a single, living view
• When a change is proposed (e.g., Security wants to upgrade the identity platform), the SIB immediately shows:
  • which services are affected
  • who needs to be involved
  • what the downstream impact might be

The owner doesn’t need authority over Security.
They just need to see the dependency and coordinate the conversation.

That’s influence.
That’s ownership.

The Hard Truth About Accountability

Here’s what organisations don’t want to hear:

If you give someone accountability without visibility and influence, you’re setting them up to fail.

And when they fail, it’s not because they weren’t capable.
It’s because the system was designed to obscure truth and fragment responsibility.

That’s not poor performance.
That’s poor design.

OSM doesn’t magically solve every organisational dysfunction.

But it does make one thing clear:

If you can’t see the service, you can’t own it.

And if you can see it - really see it - then ownership becomes possible, even without authority.

The Path Forward

Ownership without authority is not a paradox.
It’s a choice.

It requires:

• making services visible
• designing for influence, not control
• measuring coherence, not compliance
• building trust through transparency

OSM provides the model, the language, and the tools to make it real.

But it also requires something harder:

The willingness to stop pretending hierarchical authority equals service ownership.

Because it doesn’t.
And it never did.

If this resonates, follow along for more on Organisational Service Management, service flow, and human-centred transformation.

And if you’re navigating the accountability trap in your own organisation - I’d love to hear your story.