Questions we answerProcess and ownership
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.
Free · a few minutes · starts from “Something in the team isn't working”
The short answer
Unowned work is a structural problem and adding a person rarely fixes it. If nobody owns it today, nobody can brief a new person on it either, and the ambiguity survives the hire. Name one accountable person first, even provisionally, and give them the authority to decide rather than just the task. What remains after that is a real question about capacity or capability — and it is a much easier question to answer, because someone can now describe it.
Work without a clear owner drifts. It surfaces as missed follow-ups, duplicated effort and the quiet assumption that someone else has it.
The fix is usually a decision, not a hire. The diagnostic checks whether anything more is needed once the decision is made.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Ask three people who owns it and you get three answers.
- It only surfaces once it has already gone wrong.
- It lives in a shared inbox, folder or channel and nowhere else.
Signs it's something else
- It has an owner who does not have the time, which is a capacity problem.
- It has an owner who does not have the authority, which is a permission problem.
- Everyone knows who owns it and it still does not get done.
What's usually behind it
- Work that appeared after roles were set and never got assigned.
- Shared responsibility that has become nobody's.
What people usually get wrong
- Assigning it to a team rather than to a person.
- Giving it to whoever raised it, which teaches people not to raise things.
- Recruiting for work that has never been defined, so the new person inherits the ambiguity.
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 one owner
The work matters, somebody has room, and the decision is the whole fix.
Fold it into an existing role
It sits naturally next to work someone already owns.
Write the steps down first
Nobody can own it because nobody can say what it involves.
Stop doing it
It drifted in without a reason and nobody would notice if it stopped.
When doing nothing is the right call
If the work genuinely does not matter, deciding to stop it outright is a better answer than finding it an owner. Say so explicitly rather than letting it drift, so nobody spends another month half-doing it.
What the diagnostic asks
- How long it has been like this.
- Who owns the work today and how many people could do it.
- How much of it is written down, and the size of the team.
“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.
What changes the answer
- A very small team may have nobody to give the work to, which changes the picture.
- Hiring into unowned work usually reproduces the problem with one more person in it.
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
- Everything comes back to me — what do I do?Decide which decisions genuinely need you, hand the rest over with the authority to go with them, and write down what only lives in your head. Most founders are the bottleneck because nobody has been told where the line is.
- 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.
- How should I structure my small team?Most structure problems in small teams are ownership problems. Decide who owns what before you draw a chart or add a layer.
- 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.
- 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.