7 min read
Most advice about overload starts with the person carrying it. This one starts with the work, because the work behaves in ways that are consistent, predictable and almost entirely independent of who happens to be standing nearby.
Every organization produces a steady stream of items that belong to nobody. Not unassigned in the sense of sitting in a queue waiting for allocation — genuinely ownerless, with no role that covers them, no team whose remit includes them, and no process that would ever produce a decision about who should have them. They are not rare and they are not a sign of a badly run place. They are a by-product of having a structure at all, because structures are written in advance and the work arrives afterwards.
Where ownerless work comes from
Four sources account for most of it, and knowing which one you are looking at changes what is available to do.
The seam. Two functions that meet along an edge, with a strip between them that neither definition reaches. Procurement and legal, sales and delivery, support and engineering. The strip is narrow and it is never empty for long.
The exception. Any process defines the standard case and is silent on the rest. The moment a case arrives that the process did not anticipate, it has no owner by construction, because the owner named in the document is the owner of the standard case.
The residue. What a reorganization leaves behind. A team is split, a function is merged, a layer is removed, and a handful of duties that lived in the old shape have nowhere to sit in the new one. Nobody notices at the time because the duties are small and the reorganization is large.
The new thing. A regulation, a tool, a channel, a customer segment that did not exist when the roles were drawn. It generates work immediately and acquires an owner much later, if at all.
Notice that none of the four is anybody’s fault, and none of them can be prevented. An organization that eliminated all four would be one that never changed, never reorganized, never encountered an unusual case and never adopted anything. The supply is permanent. The only real question is what happens to each item once it appears.
It does not wait, and that is the whole problem
If ownerless work simply sat still until somebody allocated it, none of this would matter. It would accumulate visibly, somebody would eventually schedule a session to deal with the pile, and the pile would be dealt with.
It does not sit still, because almost all of it has a clock attached. The customer is waiting. The regulation has a date. The supplier needs an answer today. So the item is not resolved in a design conversation about who should hold it; it is resolved in the moment, by whoever is present, under time pressure, in the only way available — somebody just does it.
That single act is where ownership is actually determined in most organizations. Not in the org chart, not in the role definitions, but in the small urgent moments when something with a deadline turns out to belong to nobody. The org chart describes the work that was anticipated. The routing of everything else is decided by proximity and reflex, case by case, and it is never reviewed, because as far as anyone can tell nothing happened.
Why it lands where it lands
Ownerless work is not distributed evenly, and it is not distributed randomly. It goes to the person for whom the cost of giving it is lowest, and that calculation is made unconsciously by everyone in the vicinity, all the time.
Handing an ambiguous item to someone carries costs: explaining it, checking on it, and the risk of it coming back wrong. A person who has previously absorbed ambiguity well removes all three. So they are, in the most literal sense, the cheapest destination in the room, and every individual decision to send it their way is locally correct. That is why the accumulation is so hard to object to — there is no single instance of it that anybody did wrong.
Do that for long enough and the routing stops being a series of decisions and becomes an expectation. This is what we call The Default Position™: the structural role a capable person occupies through the slow conversion of willingness into obligation. Nobody appointed anyone. The work simply found the path of least resistance often enough that the path became the answer.
Asking who owns this, without sounding like a refusal
The obvious intervention is to ask the ownership question out loud. It is the right intervention and it goes wrong constantly, for a reason worth understanding before you try it.
Asked in the middle of something urgent, “who owns this?” is heard as “not me”, and it is heard that way even when it is not meant that way. The room is under time pressure and reads the question as an obstacle rather than a query. You get a slightly cold answer, the item lands on you anyway, and you have paid a social cost for nothing.
Three adjustments make it work, and all three are about separating the question from the moment.
Take the item and ask about the class. Handle the thing in front of you — the deadline is real — and raise the question afterwards about the category rather than the instance. “I have done the one for Tuesday. Where should these sit generally?” Nobody can hear that as a refusal, because you already did it.
Bring a count, not a feeling. “This keeps landing on me” invites a discussion of your capacity and your attitude. “This is the fifth one this quarter, here are the dates” invites a conversation about a rate. The second describes the organization; only the first describes you.
Propose an owner. An open question hands a manager a problem. A proposal hands them a decision, which is a much smaller thing to give you. Being wrong about who should own it costs nothing at all — a wrong proposal is corrected in one sentence, and the correction is itself the ruling you were after.
The register nobody keeps
Everything above depends on being able to say how often this happens, and almost nobody can, because the events are individually forgettable by design. Four minutes here, a message there, an afternoon that went somewhere. Ask yourself at the end of a quarter how many ownerless items you absorbed and you will produce a number that is both a guess and an underestimate.
So keep the register. One line per item: what it was, the date, and which of the four sources it came from — seam, exception, residue or new thing. Two minutes a week. After a quarter you have something no conversation about workload has ever had, which is a distribution: not “I am overloaded” but “eleven items, seven of them from the same seam between two teams, none of which has an owner”.
That reframing is what makes the problem addressable by someone other than you. A workload is yours to manage. A seam producing seven unowned items a quarter is a design question, and design questions belong to the level that drew the design.
What to do about the ones already on your desk
The register works forward. It does nothing about what has already accumulated, which for most people reading this is the larger half, and the accumulated pile has a particular difficulty: each item individually looks too small to raise, while collectively they are most of the reason your week does not fit.
The mistake is to try to deal with it in one conversation. The pile was not assembled in one conversation, and a single meeting proposing to give eleven things back will be received as a person having a crisis rather than a structure being corrected. What works is one decision per item, made in advance, so that the conversations happen separately and each is small.
We publish the Clarity Reset System™ for that stage. It takes one situation at a time, puts it through the three filters of responsibility, time and energy, and returns a single decision, which is the constraint that makes it useful. A pile of ambiguous obligations is not resolved by understanding it more thoroughly. It is resolved one decision at a time, and the decisions have to be made somewhere other than in the middle of an urgent Tuesday.
For neighbouring ground: roles do not break, they blur covers the seams these items fall into, and the more you handle, the more you get follows what happens next.
The work with no owner will arrive again this week. It always does. Most organizations never find out how often, because nobody has ever written it down.
— HCOS