Nothing in Your Unit Ever Finishes

Work does not pile up because your team is slow. It piles up because no one has been given permission to say a thing is done, so everything stays technically open.

Look at whatever list you use to track your team's work. Count the items that have been open for more than four months. Now ask a harder question about those items: how many are actually being worked on, and how many are simply sitting there because nobody has the standing to close them?

Most leaders assume the pile is a throughput problem. More people, better tools, tighter meetings, a cleaner way of ranking what matters. Those may all be worth doing, and none of them will change the number, because the number is not produced by how fast work gets done. It is produced by how work ends. In a unit where finishing has no definition, work does not end at all. It goes quiet, and quiet is not the same as closed.

Closing is a risk one person takes alone

Think about what happens to the person who declares something finished. They are making a claim in public that this is good enough, and they are making it without cover. If a problem surfaces in that work six weeks later, the trail leads back to them and to the moment they said it was done. Nobody else signed anything.

Now compare that to the alternative, which is leaving the item open. There is no cost to it. The item sits on a list, it gets a sentence in a status update every few weeks, and if anyone asks, the honest answer is that it is still in progress. Nobody has ever been disciplined for something that was still in progress. In a unit without a stated standard for good enough, closing is the only move that carries personal risk, so people stop making it. They are not being lazy. They are reading the incentives correctly.

What that costs you accumulates out of sight. Each open item takes a small amount of attention every week, in the form of a status line, a check-in, or the two minutes someone spends remembering what it was. Fifty of those is most of a person. That is the actual cost of the pile, and it is invisible because it never shows up as a task anywhere. It shows up as everyone being busy while the newest thing on the list is the only thing that moves.

What you will see instead of the real problem

Reorganizing the list rather than shortening it. Units in this condition become skilled at categories. Work gets tagged, ranked, moved to a parking area, marked as on hold, or grouped into a new section for things that are not currently active. All of it is real effort and none of it closes anything. If your team has changed how the list is organized twice in a year, that is the finding.

Work that gets revived at the worst moment. An item that was left open in March comes back in October, usually because someone senior remembers it. Nobody can say what state it was in, the person who knew has moved on, and the unit spends a week reconstructing something that was ninety percent done seven months ago. This is the direct cost of never closing, and it is why the pile is not free storage.

Your best people carrying the most open items. Capable people get handed the ambiguous work, and ambiguous work is the hardest to declare finished. Over a couple of years your strongest person accumulates a long tail of things that are basically complete and formally open, each one holding a thread of their attention. They will not complain about this, because none of it is heavy. All of it is on.

Three things that let work end

Say what good enough is before the work starts. Not the ideal version, the version that ships. Two or three specific conditions, agreed at the front, that let someone say afterward that the thing is done. Most work has never had this conversation, which is why finishing feels like a judgment call rather than a check. The conversation takes ten minutes at the beginning and saves the months of drift where nobody is sure whether more is expected.

Make closing a decision you make, not one they make alone. Take the exposure yourself. If you review a list of items and say plainly that these six are closed as of today, you have moved the risk from the individual to the person who can carry it, which is you. This is the single fastest thing on this list, and most leaders do not do it because it means owning a call about work they have not read in detail. Own it anyway. The alternative is that the work stays open forever and you own that instead, without ever having decided.

Close things that were never going to happen, and say so. A meaningful share of any pile is work that was proposed under conditions that no longer exist. It is not blocked and it is not late. It is finished as an idea, and nobody has said so because cancelling something feels like a small admission. Do it out loud, name what changed, and do not soften it into a pause. Everyone on your team already knows which items these are, and the fact that they are still listed tells your team that the list is not connected to what is real.

The version of this that runs on you

Look at your own open items, the ones that only you can close. Draft decisions, half-written notes, conversations you have started and not concluded, the thing you told someone you would think about in April. Same mechanism, same reason. Closing means saying something definite, and staying open means never being wrong.

There is one more layer worth naming. Some of the items on your list have been open for a year because closing them requires a decision you do not want to make, and leaving them in progress is a way of not making it while looking like it is being handled. That is worth being honest with yourself about, since your team can tell the difference. They have been watching those items sit there as long as you have.

Three questions

Take the ten oldest open items in your unit. For each one, can you say what would have to be true for it to be closed this month? If you cannot say it for more than half of them, nobody else can either.

When did you last close something yourself, by name, in front of the team? Not delegate the closing, not ask for a status. Say a thing is done and take the exposure for saying it.

Ask one person on your team what they are afraid would happen if they marked something complete and it turned out to be wrong. Ask it plainly, and then be quiet long enough for a real answer. What they tell you is the actual policy in your unit, regardless of what you have said about it.