A request without an owner is already adrift

Winslow Homer's sailor is not in danger because of the sharks. He is in danger because nothing connects him to help: no mast, no oars, no line to the ship on the horizon that may or may not have seen him. The Gulf Stream is a painting about drift, and drift is what happens to work that belongs to everyone.

Sent to all, owned by none

Post a problem to a group and something strange happens: the more people who could act, the more certain each one is that someone else will.

Nobody was lazy. Nobody was even wrong. There was simply no moment where the job attached itself to a person, so it floated between three of them. Floated is another word for sinking slowly.

One name, in writing, visible to everyone

Every ticket in fam. carries exactly one assignee. Not because one person does all the work, a job can pass through many hands on its way done, but because at every moment exactly one person answers for where it stands.

The single name changes three conversations:

• The requester knows who, not "the team". "Any update?" has an address, and mostly stops being asked.
• The handoff becomes an event, not an assumption. Reassignment happens on the record, not by shrugging in a group chat.
• The queue becomes honest. Ten tickets against one name is a workload you can see and rebalance. Ten tickets floating in a channel is folklore about who seems busy.

Ownership is not blame

The point of the name is not knowing who to shout at when something goes wrong. It is the opposite. A clear owner can say "not mine, reassign it" in one tap, which is exactly the conversation an unowned job never gets to have. Ambiguity is what wears people down; a queue of things that are definitely yours, each with a date, is just a job.

The ship on Homer's horizon never turns. With a system underneath, it does not need to: the moment the mast broke, the ticket had a name on it, and someone was already rowing out.