The short version
- Work with no name against it does not get done.
- A temporary state with no expiry date is a permanent decision nobody made on purpose.
- Ownership is a reporting duty, not an admission of fault. The owner is whoever reports on it, not whoever broke it.
- One name per item, visible to the client, is the part that makes it real.
A blog we ran for a client went down and stayed down for weeks, and the restore was never the hard part of it. The line sat on the status list, the wording did not change from one week to the next, and no single person had said out loud that getting it back was theirs. That one was ours to run and we did not run it.
Why does unowned work stall when everybody agrees it matters?
Everybody on the call can rank an item as important and leave without one person having committed to move it. So the item survives on the list indefinitely.
The same task, with a name on it and without:
| Signal | One named owner | Owned by the team |
|---|---|---|
| Who answers in the status call | The owner, with a date | Whoever feels most responsible that week |
| When that person is away | Handover is explicit | Nothing happens and nobody notices |
| How the line reads week to week | It changes | Word for word identical |
| When priorities collide | The owner escalates | It loses to anything with an owner |
What makes temporary the most expensive word on a status list?
A temporary state carries no end date, so it never becomes late, and late is the mechanism that makes anybody act. A line saying a blog is temporarily down stays accurate for exactly as long as nobody restores it. Accuracy is what made ours safe to leave alone week after week.
Give every temporary state an expiry the moment you create it. On that date it either ends or it gets recognised as the permanent decision it already is, and both of those outcomes beat the one where nobody ever chose.
How do you assign an owner without turning it into blame?
Separate the two questions. Who broke it is a question for later and usually has no useful answer. Who reports on it next week is the one that changes anything.
Ownership is a reporting duty. The owner does not have to do the work and frequently should not. They have to know its state and say it out loud on the same cadence every week. When it is stuck, they are the person who escalates.
Which work goes unowned most often?
The seams. Work that sits between two vendors, or between the person who left and whoever inherited their logins. Rebuilds and migrations manufacture seams by design, because they retire systems faster than anybody reassigns them.
A publishing surface everybody can see is a seam once the restore behind it belongs to nobody, which is the gap ours fell into. So is a redirect map, a form endpoint, a DNS record, a scheduled report nobody notices until it stops arriving. Each of them had an owner under the previous arrangement and none of them inherit one automatically.
A status line that reads word for word the same as last week’s has no owner, whatever the owner column says.
How do you find unowned work before a customer does?
Keep an inventory of every live surface with an owner name and a last-verified date against it. Walk it quarterly. The rows with old dates are the ones nobody is watching.
The faster read costs nothing. Scan the status list for lines whose wording has not changed since the month started, then put a name and a date against each one in front of the client. Naming an owner where the client can see it is the part that makes the ownership real, because the next status call arrives whether the work moved or not.
The two habits that keep items from going quiet are why we ship weekly and naming every gate in week one.
Frequently asked questions
What does it mean for a task to have an owner?
One named person who reports its state on a fixed cadence and escalates when it is stuck. The owner does not have to do the work. They have to know where it stands and say so, which is what makes a stalled item visible to everybody else.
Why do temporary fixes become permanent?
Because a temporary state has no end date, so it never becomes late, and lateness is what makes people act. Attach an expiry date at the moment you create the workaround. On that date it either ends or gets recognised as a decision somebody should make deliberately.
Can a team own a task instead of a person?
No. A team-owned task belongs to whoever feels most responsible that week, which changes and eventually lands on nobody. A team can hold an area of responsibility, but every item inside it still needs one individual named against it.
How do you assign ownership without blaming someone?
Ask who reports on this next week rather than who broke it. Ownership is a reporting duty, so naming an owner is a scheduling decision. Keeping it separate from fault is what stops people avoiding the role.
How do you find work that nobody owns?
Keep an inventory of every live surface with an owner and a last-verified date, and walk it quarterly. For a faster read, scan the status list for lines whose wording has not changed in weeks. Static wording means static work.
What should a status update say about a stalled item?
The item, the owner, what it is waiting on, and the date it gets looked at again. A stalled item reported plainly is information the client can act on. The same item repeated in the same words is a signal that nobody has touched it.
Sources
- Chua Network delivery data across 8 client accounts (internal fact bank)
- Chua Network engagement records, anonymized (internal experience bank)
