Questions we answerProcess and ownership
Who should own this work?
Ownership is accountability for an outcome plus the authority to decide. Anything less is a task list with someone's name on it, and it will not hold.
Free · a few minutes · starts from “Something in the team isn't working”
The short answer
Ownership means one named person accountable for an outcome, with the authority to make ordinary decisions about it without asking. Choose whoever is closest to the consequences of it going wrong, and give them the decisions to match — an owner who has to seek approval for everything is a coordinator, and the work will still queue. Shared ownership between two people reliably becomes ownership by neither. If nobody can own it because it spans several teams, the real problem is the way the work is split, not the naming.
Work without an owner is one of the most common and least dramatic failures in a team. Nothing breaks visibly; things are just consistently late, and each person involved is reasonably sure it was somebody else's turn.
The naming part is easy and often skipped. The part that makes it stick is the authority: an owner who cannot decide anything is a name on a list, and the work will wait exactly as long as it did before.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Asked who owns it, two people each name the other.
- The work is consistently late but no individual step is slow.
- Decisions about it get made in meetings, by whoever is in the room.
Signs it's something else
- There is a clear owner and they simply do not have the hours.
- The owner is clear but lacks a skill the work requires.
- Everyone knows who owns it and it is going wrong anyway, which is a different problem.
What's usually behind it
- Work that spans two teams and was never explicitly assigned to either.
- A process where several people each do a step and nobody holds the outcome.
- A deliberate decision to share ownership, which usually means nobody has it.
What people usually get wrong
- Assigning ownership without authority, so the work still routes through someone else.
- Splitting ownership between two people to be fair, and getting neither.
- Naming an owner for the task rather than the outcome, so the gaps between tasks stay unowned.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Name a single owner
Someone is close enough to the outcome to be accountable for it.
Give the owner the decisions
There is a named owner and the work still waits on someone else.
Change how the work is split
No one team can own the outcome as the work is currently divided.
When doing nothing is the right call
If the work is genuinely occasional and genuinely gets done, formal ownership may be more overhead than it is worth. The test is whether it fails repeatedly — recurring failure in the same place is what turns this from tidiness into a real problem.
What the diagnostic asks
- Who owns the work today and whether that is clear.
- Whether the problem is too much work, a missing skill or unclear ownership.
- How much of the process is written down.
- How big the team is and how it is arranged.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Develop
Build the capability in someone already in the team, with time and support.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
What changes the answer
- Work nobody owns is an ownership problem first, whatever else is also true.
- An owner who cannot make decisions is not an owner, and naming another one will not help.
- Work spanning several teams may need the split changing rather than the name.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Nobody owns this work. What do I do?Give it an owner. That is almost always the first move, and it is faster and cheaper than anything else on the list.
- How do I fix handoff problems?Work fails at the joins more often than in anyone's hands. Fixing it means agreeing what "ready" means at each boundary — and having someone own the outcome across it.
- Projects keep slipping — what should I do?Repeated slippage is information. What matters is where it slips: consistently in the same place is a process problem, everywhere at once is usually over-commitment.
- Is this a process problem or a people problem?More often process than managers expect. If your most capable person would struggle in the same seat, the work is badly shaped. If one person struggles where others do not, the answer is about that person.
- Should I fix the process before hiring?Usually yes, at least far enough to know what the new person would own. It is cheap and quick, and it either removes the need or tells you exactly what to recruit for. It stops being sensible once it becomes a reason never to decide.
- Do I need a new hire or a better process?Usually the process first, because it is cheap to try and tells you how much of the load is design rather than volume. Sometimes both.