Process and ownership
Is the work failing because of how it flows, not who is doing it? Slipping projects, hand-off failures, quality problems and work nobody owns — the decisions where the answer is usually to change how the work moves rather than to add someone to it.
Free · usually only a few minutes · no account
When work goes wrong repeatedly it is tempting to look at the people doing it. Usually the more productive place to look is the joins: where work is handed over, where it waits, and where two people each believe the other one has it.
These questions have a common shape. Something is visibly not working, the symptom looks like effort or ability, and the cause is that nobody decided who owns the outcome or what "done" means.
This family also contains the cheapest wins in the product. Writing down a process and giving it an owner costs a week, not a salary — and it is the one thing that has to happen before automating anything, because automating an undocumented process automates the mess.
Worth settling before any of these
- Whether anyone can name the single person accountable for the outcome.
- How much of the process is written down, and how much lives in someone's head.
- Where the work waits, and who it waits for.
- Whether the same failure keeps happening in the same place.
The questions in this family
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.
Read the answerNobody 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.
Read the answerQuality 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.
Read the answerIs 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.
Read the answerShould 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.
Read the answerWho 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.
Read the answerProjects 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.
Read the answerHow 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.
Read the answerShould I document the process before automating it?
Yes, and not because documentation is virtuous. Writing it down is how you find the steps that should not exist — which is most of the value automation ever delivers.
Read the answer
Nearby decisions
These families overlap with this one often enough to be worth a look — most team decisions turn out to belong to more than one of them.