A Task Without One Owner Belongs to Everyone. And Therefore Nobody.

Nine people received the message. Three replied with a thumbs-up. Nobody did the work.

The message was perfectly clear: “Can someone send the customer the revised packing list before dispatch?” It named the task, the recipient, even the deadline. The only thing it did not name was a person — and that one omission decided everything that followed.

Each of the nine had a reasonable thought. The dispatch clerk assumed sales would send it, since the customer was theirs. The sales engineer assumed accounts had it, since the packing list came from their file. Two people were on site and read the message at night. The rest saw three thumbs-ups and concluded, sensibly, that it was handled.

A task addressed to everyone is addressed to no one.

Nobody refused it. Nobody dropped it, exactly. There was simply never a moment when one specific person became the one who would answer for it. Responsibility, divided nine ways, rounds down to zero.

The usual response, after the customer calls, is a speech about proactiveness — as if the failure were a character defect shared by nine people at once. It wasn’t. Nine conscientious people each made a correct local judgement. The failure was structural: the request created work without creating an owner.

The fix costs one name. Not “can someone send the packing list” but “send the packing list before dispatch” — addressed to one person. The moment a name is attached, everything changes shape. That person can do it, delegate it, or say “I can’t before dispatch — it needs to be sales.” All three answers are fine. All three produce an owner. What no longer exists is the silent middle state where everyone assumes and no one answers.

One name is not about blame. It is about there being, at every moment, exactly one person who can answer “where does this stand?” — and who knows they are that person. Helpers can help. Ownership doesn’t divide.

Run this test tonight: scroll your work group and find the last ten requests. Count how many named a single person. For most teams the honest answer is two or three — which means most of the work in flight right now is held by assumption.

The group can stay. The thumbs-ups can stay. The work just needs one name on it.

That is the first rule TaskMIS enforces: a task cannot exist without one named owner. Not a team, not a group — a person. The system will not accept “someone.”

Every task, one owner. Every owner, an answer.