There is a particular organisational cost that never appears in a report, because no single instance of it is large. It's the cost of the open loop: the task that was started, more or less done, and never explicitly closed. Nobody declared it finished. Nobody declared themselves satisfied. It just trailed off, and now it sits in a fog where half the people involved assume it's handled and half assume someone is still on it. Multiply that by every loosely-closed commitment in a busy team and you get a permanent background drain — attention spent re-checking things that were probably done, work redone because the first version was never confirmed, and a slow erosion of trust as “done” stops meaning anything reliable.
Coordinated work moves through a simple sequence: someone requests, someone commits, the work happens, and then — this is the part that gets skipped — someone declares it complete and someone declares themselves satisfied. The completion is a real move, a small act of language that shuts the loop. Skip it and the work is functionally unfinished even when it's physically done, because its status now lives only in people's assumptions, and assumptions diverge.
Here's how it plays out. A marketing lead asks a designer for “a couple of options for the landing page.” The designer sends two mockups and moves on to the next thing, considering it done. The marketing lead sees the email, thinks “great, I'll review these properly later,” and never replies. Two weeks pass. The designer assumes the options were fine and are in use. The marketing lead assumes the designer knows feedback is still coming. The launch arrives and the page isn't ready, and both are genuinely surprised, because both were sure the loop was somewhere it wasn't. No one was negligent. The completion was simply never declared, so two reasonable people held two incompatible pictures of reality.
The completion move feels redundant. The work is obviously done; saying so seems like ceremony. But “obviously” is doing enormous work in that sentence. What's obvious to the person who did the task is frequently invisible to the person who asked for it, and the gap between those two states is exactly where the cost lives. The more capable and busy a team is, the more it relies on this kind of implicit “everyone knows,” and the more open loops it quietly accumulates.
What's obvious to the person who did the work is frequently invisible to the person who asked for it.
The repair is almost embarrassingly small: make completion explicit. “That's done — the report's in your inbox, anything else you need on it?” “Great, that's closed for me, thank you.” Two sentences. They cost seconds and they collapse the fog. The loop is shut, both people know it, and nobody spends next Tuesday wondering.
For a leader, the higher-leverage version is to build the expectation into how the team works. Requests come with a clear picture of what “done” means, agreed up front, so completion is unambiguous when it arrives. Commitments are closed out loud rather than left to evaporate. And the team develops a shared allergy to the trailing-off ending, the “I think that's handled?” that signals an unclosed loop. None of this is a new tool or a new meeting. It is a single missing move, added back in — and it is one of the cheapest performance improvements available to any team.
The deepest fix happens before the work even begins. Most open loops are really ambiguous-completion loops: the task got done to one person's definition of finished and not the other's, so the close never feels safe to declare. Agreeing the conditions of satisfaction up front — “done means the three options costed, with a recommendation, in a one-page summary” — removes the ambiguity in advance, so completion becomes a fact both people can see rather than a judgement call one of them has to risk. It feels like over-specifying. It is actually the cheapest insurance there is against the most common kind of rework.
And as with most of this, the leader sets the temperature. A leader who lets their own loops trail off — who asks for things and never acknowledges receiving them, who leaves their own commitments hanging — teaches the whole team that open loops are normal. A leader who visibly closes every loop, who reliably says “got it, that's done, thank you,” makes closing the loop the ambient standard. People finish things the way they see things finished with them.
Try the audit. Look at what your team is carrying right now, and separate the genuinely active work from the open loops nobody closed. The second pile is almost always bigger than anyone expects, and almost all of it is free to clear — not by doing more work, but by finishing the conversations that were already nearly done.