Questions we answerProcess and ownership
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.
Free · a few minutes · starts from “Something in the team isn't working”
The short answer
Quality usually slips at the joins rather than in anyone's ability. Look first at where work is handed over, where it waits, and whether anyone owns the outcome as opposed to a step. Overload and unclear standards are the next two causes. Hiring is the right answer only once you have established that the work is well understood, properly owned, and simply exceeds the hours available — otherwise you add a person to the same joins and the same standards.
When errors creep in, the instinct is to look at who made them. The more useful question is what the work looks like: how repeatable it is, how much judgement it needs, and whether anyone owns the whole of it.
The diagnostic asks about the work, not the people, and points at the change most likely to hold.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- The mistakes are spread across people rather than concentrated in one.
- They cluster at the busiest times, or at the same hand-off every time.
- There is no check anywhere in the flow, so errors reach the customer first.
Signs it's something else
- One person accounts for most of them while others in the same role are fine.
- The standard has never been written down, so slipping is a matter of opinion.
- Something changed recently — a system, a supplier, a customer — and the work has not caught up.
What's usually behind it
- A process that depends on people remembering steps.
- Shared ownership with no one accountable for the outcome.
- Volume that has quietly crossed the point where care is possible.
What people usually get wrong
- Adding a review step to everything to catch a problem that lives in one part of it.
- Looking for who to blame before looking at where the errors cluster.
- Raising the standard without reducing the volume, and getting the same result more slowly.
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.
Fix the flow where errors cluster
The mistakes have a pattern and the pattern points at a step or a hand-off.
Name an owner for the outcome
Several people touch the work and none is accountable for how it lands.
Reduce the load
Care has become impossible at the current volume and everyone knows it.
Develop the skill
The work is well shaped and a specific capability is missing.
When doing nothing is the right call
If the standard has never been written down, the first move is to agree it rather than to change anything. It costs a conversation, and it is the only way to know afterwards whether anything improved.
What the diagnostic asks
- How long it has been like this and who owns the work.
- How repeatable it is and how much judgement it needs.
- What happens when it goes wrong.
“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.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
Develop
Build the capability in someone already in the team, with time and support.
What changes the answer
- High stakes with high judgement keep a person in charge and point at development or ownership.
- Repeatable work with errors points at process design, sometimes with AI checking alongside a person.
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
- 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.
- My team is overloaded. What should I do?Start by finding out whether the overload is volume, design or ownership. Each has a different fix, and only one of them is more people.
- 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.
- 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.