Questions we answerProcess and ownership
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.
Free · a few minutes · starts from “Something in the team isn't working”
The short answer
It is a process problem if the same failure recurs in the same place regardless of who is doing the work, if nobody owns the outcome, or if the work waits at a predictable point. It is a people problem if one person is struggling with work others handle, or if a genuine skill is missing. Most situations are some of each, and the useful order is to establish the process question first — because a people answer applied to a process problem is expensive and does not work.
The distinction matters because the two have opposite fixes. A process problem gets worse when you replace the person; a people problem gets worse when you add another procedure.
There is a straightforward test. Picture your most capable person in that seat, with the same information, the same tools and the same interruptions. If they would also struggle, the work is the problem. If they would be fine, something specific to this person is in the way — which may be skill, clarity, motivation, or something happening outside work entirely.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- More than one person has struggled in the same seat.
- The work depends on people remembering steps that are written down nowhere.
- Good people are producing uneven results, and the unevenness tracks the workload rather than the person.
- Nobody can say who decides, so decisions sit and wait.
Signs it's something else
- One person is struggling where others in the same role are not.
- The expectations are written down, understood and agreed, and are still not being met.
- The work is well defined and the gap is a specific skill that could be taught.
- Something has changed for the person recently, which is a conversation rather than a redesign.
What's usually behind it
- A role that has accumulated tasks from three different jobs and was never redefined.
- Expectations that were never made explicit, so nobody can say whether they are being met.
- Information that arrives late or incomplete, which a person is then held responsible for.
- A genuine skill or fit problem that has been avoided because the conversation is uncomfortable.
What people usually get wrong
- Adding a procedure to manage one person, which slows everyone else down and does not address the person.
- Treating the direct conversation as a last resort, so it arrives too late to help anyone.
- Deciding it is a people problem because that is easier to name than to redesign the work.
- Reshaping the team around one individual, which leaves the wrong shape behind when they go.
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.
Redesign the work
More than one person has struggled in the seat, or the role mixes jobs that should be separate.
Make ownership explicit
Work is falling between people and nobody is accountable for the outcome.
Have the direct conversation
Expectations are clear and agreed, and one person is not meeting them.
Develop the missing skill
The role is right, the person is right, and a specific capability is absent.
When doing nothing is the right call
If you genuinely cannot tell yet, say so and gather evidence for a short, fixed period: write down what should happen, what actually happens, and where it breaks. A fortnight of notes usually settles the question, and it is far cheaper than acting on the wrong theory.
What the diagnostic asks
- How long it has been like this, and who owns the work today.
- How repeatable the work is, how much judgement it needs, and how much of it is written down.
- How many people could do it, and whether someone could grow into it.
“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.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Develop
Build the capability in someone already in the team, with time and support.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
What changes the answer
- A pattern across more than one person points at the work rather than the individual.
- Clear, agreed expectations that are still not met point at a conversation, not a redesign.
- Work nobody owns is an ownership problem before it is either of these.
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
- 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.
- Quality is slipping in my team. Is it people, process or workload?More often process than people. Slipping quality is usually a sign that the work has outgrown the way it is done, not that anyone has stopped trying.
- 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.
- 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.
- 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.