OWNERSHIP AMBIGUITY

When everyone is involved, but no one is clearly responsible for driving something to resolution.

What this pattern is

A task, decision, deliverable, or problem has multiple people involved.

Everyone has a role.

Everyone is participating.

But no one is clearly responsible for driving it to completion.

One person thinks they’re providing input.

Another thinks they’re waiting for a decision.

Someone else assumes the PM is coordinating it.

The work has plenty of people around it, but no clear center of ownership.

What this usually looks like

“I thought they were handling that.”

“I was waiting for their input.”

“Who’s actually responsible for this?”

Actions get assigned to teams instead of one clear owner.

Issues move between people without being resolved.

The PM becomes the default owner because they keep following up.

Everyone can explain their part, but no one owns the outcome.

Why this happens

Ownership gets confused with participation.

Someone is involved, so we assume they own it.

Someone has expertise, so we assume they’ll drive it.

The PM is coordinating the project, so people assume the PM owns whatever falls between functions.

But participation, expertise, coordination, authority, and ownership are different things.

When those distinctions aren’t explicit, everyone can be involved while no one is actually accountable for moving the work forward.

What this causes

Decisions stall.

Actions remain open longer than expected.

Issues bounce between teams.

The PM spends more time chasing work they don’t control.

Problems surface late because everyone assumed someone else was handling them.

Eventually, what looked like a follow-up problem becomes a schedule, escalation, or trust problem.

First move to stabilize it

Don’t start with another reminder.

Ask:

“Who is responsible for driving this to resolution?”

Then make the distinction explicit.

Who owns the outcome?

Who provides input?

Who has the authority to make the decision?

What tells everyone the work is complete?

The goal isn’t to assign more responsibility.

It’s to make the existing responsibility unmistakable.

[Join PM Clarity here]

People may appear aligned while holding different assumptions about who owns the next move.
See
False Alignment

Ownership discussed but never explicitly captured can later be remembered as an assignment.
→ See Undocumented Agreement

Changes create new actions and decisions that can fall into the gaps between existing areas of ownership.
See The Ripple Effect

Work can quietly expand when nobody is clearly responsible for deciding whether new requests belong inside the project.
See Scope Drift