Ask an operations lead which workflow costs them the most and they will name the one with a document. Sit with the team for a week and it is almost always something else: a task that fell between two roles and got absorbed by whoever noticed first.
Unowned work hides from measurement
If a task has no owner it has no ticket, no queue, and no number in anyone’s report. It shows up as three people being vaguely busy on a Monday, which no dashboard has ever flagged.
That is precisely why it survives. Work that is measured gets optimised or cut. Work that is invisible just accumulates.
How we find it
Two questions, asked separately of everyone in the room:
- What did you do yesterday that you would not put on a job description?
- What would break next week if you took a holiday?
The overlap between those two answers is the shortlist. On the warehouse account it was a person reconciling a carrier spreadsheet against the order system every morning, a job that had never been assigned to anyone.
Why it automates well
Unowned work is usually mechanical, which is how it ended up unowned. It has clear inputs, a repeatable decision, and no politics attached, because nobody is defending a job description that never mentioned it.
One caution
Sometimes the task is unowned because it should not exist. We have removed two of these outright rather than automate them, which is cheaper for the client and takes a conversation rather than a build.
002
/ Keep reading
From the journal