A Wrong Name Beats an Empty Box

The quarterly capability review is twenty minutes in. Forty-four boxes on the screen, each with an owner line under the label. Forty-three have names. The box labeled data quality remediation has a blank where a role should be, and the meeting has been working around it since the second slide. Someone finally offers the nearest thing to an answer: that work sits somewhere between the integration team and the analytics group. Heads nod. The facilitator types a note and moves to the next box.

The map asked a question out loud. The review moved on without answering it.

That blank has a name: an ownership vacuum. It comes in two forms. There is work the map says should happen that nobody does: the remediation queue that exists in the operating model and nowhere else, the vendor offboarding checklist everyone assumes runs. And there is work that gets done that belongs to nobody: real hours, real output, in no job description and no budget. Not under-resourced. Unaddressed.

The difference matters. An under-resourced capability can still fight for itself. It has an owner who can ask for people and a budget line that can grow. A vacuum has no one. No one to fund. No one to warn. You cannot even argue about it, because an argument needs someone on the other side.

You have seen one. There is a weekly operations summary that goes to forty people, and nobody maintains it. The last person who changed the logic left two years ago. Since then it has been forwarded, quoted in leadership meetings, and pasted into two board decks. Ask who owns it and you get the name of whoever fixes it when it breaks. That person never agreed to own it. No one ever asked them to.

The same blank sits under older things. An application that has not really changed since before three reorgs still handles a real share of daily volume. That is not unusual. The federal government's own watchdog found its most critical legacy systems still running at up to 59 years old, most of them still waiting on modernization (GAO, 2025). Whether this one should keep running is a different argument for a different piece. The question here is simpler: who owns it today? Honest answer: no one has since its builder left.

And it sits between things. Month-end reconciliation runs through four teams. Each team's steps are written down in that team's runbook. No one owns the whole. When it breaks inside a step, it gets fixed the same day. When it breaks between steps, it sits for a week while four owners correctly point out that their part ran clean.

Vacuums do not stay empty. The nearest competent person starts absorbing the work, informally, because they sit close enough to see it drop. What that costs them is its own subject, and I have written about it before. This piece is about the step before the cost: how the vacuum forms and why it holds.

Vacuums come from ordinary changes that nobody finished. A reorg moves the boxes and the work stays where it was, still shaped like the old structure. Or two systems get connected, each team owns its own end, and the agreement between them belongs to nobody. Sometimes it is a project team that ships something and disbands, and the thing they ran loses its home, because the project was the home. And often it is just succession: a person leaves, and whoever comes next inherits the job as written, not the job as lived. None of this is anyone failing at their job. The work outlived the structure that owned it.

I have done this work. For years, part of my job was keeping systems in agreement with each other. That part was written down nowhere, including in my own job description. The realization did not come as a crisis. It came as a list: the work was real, the hours were real, and it was nobody's job, including mine.

That is the tell. Even the person standing in a vacuum cannot tell you who owns the work. They can tell you who does it. When those two answers are different, you have found something. The odds were never good to begin with: fewer than half of employees say they clearly know what is expected of them in their own jobs (Gallup, 2025). Ownership of the work that sits between jobs is fainter still.

Now the wrong name. In one review, an empty box got filled the fast way. The person attached to it said, in the meeting, that the work was not theirs. No budget for it. No one trained on it. No room to take it. The chart shipped with their name anyway.

This is not carelessness. An empty box brings the question back at every review. A name closes it. The wrong name costs nothing in the meeting and buys a quarter of silence. Nobody decided to lie about ownership. The question just stopped coming up.

The honest objection: at least a name puts someone on the hook, and being on the hook produces motion. Sometimes true. But that only works on people who agreed to be on the hook. Real ownership is easy to check. The owner can tell you what the work costs to run. The work shows up in their goals or their budget. They can say no to new scope. A name with none of that behind it is ownership on paper. It forces nothing except the map to stop asking.

The fix is a review rule, not a reorg. No capability leaves your review with an empty box unless one of three things happened in the room. Someone with the authority to take the work accepted it and said so out loud, with a rough answer for who does the hours. Or you decided on purpose to leave it unowned, wrote down the risk, and put a date on the calendar to look again. Or the box went, by name, to the one person who can assign an owner, with a deadline.

The cost comes first. Your reviews run longer. Your maps look worse in steering decks. Some quarters end with blanks still showing, and blanks make leadership uncomfortable in a way wrong names never do. Good. That discomfort is doing its job. Three honest empty boxes are worth more than forty quiet names.

This week, pick one capability your team depends on and ask who owns it. If you get a hedge, you found a vacuum. If you get a name, ask that person whether they know. If they did not, you found ownership on paper.

Sources

Gallup, "U.S. Employee Engagement Sinks to 10-Year Low" (January 2025): https://www.gallup.com/workplace/654911/employee-engagement-sinks-year-low.aspx

U.S. Government Accountability Office, "Agencies Need to Plan for Modernizing Critical Decades-Old Legacy Systems," GAO-25-107795 (2025): https://www.gao.gov/products/gao-25-107795