Picture a board of job tickets on a Monday morning. One column, labelled New, with forty-one cards stacked in it like unopened mail. Three of those cards were nine days old. One of the three was a loyal fleet customer who had already phoned twice, politely, to ask what on earth was happening with his broken window regulator. Nobody had lied to him. Nobody had decided to ignore him. The ticket simply belonged to everyone, and a thing that belongs to everyone belongs to no one. It sat there, perfectly visible, getting quietly older, while eight people walked past it all week assuming someone else had it.
The obvious next move is to build a smarter queue. A priority score. A timer that turns a card angry red after a day. An alert that pokes the manager when something gets stale. That is what every job-tracking tool on the market sells you, and honestly, that is what we very nearly built. It feels like progress. It feels like you are doing something about the pile.
We did not build it, because the next week handed us an embarrassing fact. Those old tickets were not old because the team was drowning in work. They were old because not one human being had reached out and claimed them. A red card on a shared board is still a red card belonging to nobody. A timer would have made the board louder, not faster. It would have added urgency to a thing that had no owner to feel it. So the strange move was to make the board quieter and simply write a name on every card the moment it was born.
Said plainly, it was almost too obvious to take seriously. Shared ownership is a polite phrase for nobody's problem. When a ticket has eight possible owners, each person runs the same quick maths: someone else will probably grab it, and if I grab it I inherit the angry customer attached to it. So everyone scrolls past, guilt-free, because technically it was never theirs. Put one name on the card and the maths flips. Now the question is not whether to take it. It is whether to refuse it, out loud, in front of everyone. And refusing is a far more uncomfortable thing than quietly scrolling by.
So we shipped the change. The load-bearing part was tiny: every new job had to have a name on it before it could be saved. Not optional. Not auto-stamped with whoever answered the phone. The person logging the complaint had to choose a specific mechanic, by name, right then. If she did not know who should own it, she had to get up, walk across the floor, and ask the foreman. That short walk was the entire invention. We added places for the assignee to jot down what they had tried, and a running history of the job, but those were supporting cast. The name on the card was the whole play.
In the weeks after, the time from a complaint coming in to a technician actually touching it fell from more than a day to a few hours. The number of tickets older than a week dropped to a single one, and that one was a genuine parts-supply delay, exactly the kind of holdup you want sitting in plain sight rather than hidden.
Here is the part that matters if you run a small operation with a shared inbox, a shared board, a shared anything. The temptation is always to pile more structure onto the shared thing. More columns, more tags, more colours, more clever alerts that nag when something goes stale. All of that treats the symptom. The real illness is that work without an owner drifts, and no dashboard on earth fixes drift.
The cure is uncomfortable, because it forces a decision earlier than anyone wants to make one. You have to hand a job to a specific person before you even know if they are the right one. You will be wrong sometimes. The mechanic hands it back, the foreman moves it, and that is not waste. That is the system breathing. The waste was the forty-one cards sitting in New, each one a tiny shrug. If your team has a shared queue and a speed problem, do not go shopping for a tool that ranks priority. Add one required field that asks who. Then watch the pile empty itself.