Why teams stay busy while nothing important closes

There is a peculiar pathology that afflicts growing companies, one that is difficult to diagnose precisely because it masquerades as its opposite. The engineering team is shipping features. The sales team is in conversations. The marketing team is publishing content. The leadership team meets daily. From the outside, the organisation appears vital, energetic, purposeful. And yet, when you look at what actually matters—the strategic objectives set at the beginning of the quarter, the critical path items that determine whether the company survives or thrives—almost nothing has moved.

This is what I call execution without closure. It is not a failure of effort. It is not a failure of talent. It is a failure of the underlying operating system—the invisible architecture of ownership, decision rights, and accountability that determines whether work actually produces outcomes.

The theatre of busyness

In most organisations that suffer from this pattern, there is no shortage of activity. The calendar is full. The Slack channels are active. The project management tool shows hundreds of tickets in progress. This creates a powerful illusion of progress. Leaders see their teams working hard and assume that outcomes must be following. They are not.

The problem is that busyness has become decoupled from completion. Teams are optimised for activity, not for closure. They are measured on how much they do, not on whether what they do actually matters. This creates a perverse incentive structure where starting new work is rewarded more highly than finishing old work, where being responsive in chat matters more than being effective in delivery, and where visibility trumps value.

The result is what I call work-in-progress inflation. Every team has more ongoing initiatives than they can possibly complete. Every individual is context-switching between multiple competing priorities. The cognitive overhead of simply tracking what is happening becomes a significant drain on capacity. And yet nothing is allowed to die. Old projects persist in a kind of zombie state, neither actively worked on nor formally closed, consuming attention and resources without producing value.

The anatomy of non-closure

To understand why teams stay busy without closing, we need to look at the specific failure modes that prevent completion.

First, there is the problem of unclear ownership. In many organisations, work is assigned to teams rather than to individuals. A feature might be "owned by engineering" or a campaign by "marketing." But when everyone owns something, no one owns it. When multiple people could complete a task, the task often completes no one. What is required is singular, named ownership—one person whose responsibility it is to drive a piece of work to completion, whose reputation and incentives are tied to its outcome.

Second, there is the problem of ambiguous completion criteria. Teams are often asked to "work on" something or to "look into" something. They are rarely given clear, testable definitions of what success looks like. Without a clear finish line, work can continue indefinitely. The fuzzy brief becomes a licence for endless iteration, for polishing that never ends, for exploration without extraction.

Third, there is the problem of decision bottlenecks. Work frequently stalls not because the people doing it are incapable, but because they are waiting for approval, for input, for a decision that never comes. The decision-makers are busy too, attending their own meetings, responding to their own messages. The work sits in queue, technically "in progress" but effectively frozen, contributing to the illusion of activity while producing no actual value.

The cost of drift

The cost of this pattern is enormous, though often invisible. There is the direct cost of wasted effort—hours spent on work that never ships, on projects that never achieve their objectives. There is the opportunity cost of what could have been done instead—the high-value work that was deprioritised in favour of low-value activity. There is the morale cost of working hard without seeing results, of the slow erosion of belief that the organisation is capable of achieving what it sets out to achieve.

Perhaps most damagingly, there is the cost to strategic coherence. When execution is decoupled from outcomes, strategy becomes meaningless. You can have the clearest strategic vision in the world, but if your operating system translates that vision into an endless churn of activity without closure, the strategy will never be realised. The organisation learns, implicitly, that strategic intent is not to be taken seriously—that it is merely a kind of performance, disconnected from the reality of how work actually happens.

What to rebuild

Fixing this pattern requires more than exhortation. Telling people to "focus" or to "be more efficient" does nothing when the system they are working within is structurally designed to produce busyness without closure. What is required is a deliberate redesign of the operating system.

Start with ownership clarity. Every significant piece of work should have a named, singular owner. Not a team, not a function, but a person. That person should have the authority to make decisions about the work and the accountability for its outcome. They should be able to answer, at any moment, what the current status is, what the next action is, and what is blocking progress.

Introduce sharp completion criteria. Before work begins, define what "done" means in specific, testable terms. If you cannot write down what success looks like in a single sentence, you are not ready to start. These criteria should be reviewed at the beginning of the work and at every status check. They are the contract between the organisation and the owner of the work.

Create decision velocity. Map the decisions that are required to complete work and ensure there is a clear, time-bound path to making them. If a decision requires input from multiple stakeholders, schedule the decision meeting at the same time you assign the work, not when the work is already stalled waiting for it. Treat decision latency as a first-class metric, as important as any other operational indicator.

Finally, practice ruthless prioritisation. The most common cause of non-closure is simply having too much in flight. Most organisations should be doing fewer things, with more focus, and closing them more completely. This requires the discipline to say no—to kill projects that are not working, to decline new work that does not meet a high bar, to accept that not everything that seems important actually is.

The shift to closure culture

The ultimate goal is to shift from a culture of busyness to a culture of closure. In a closure culture, the highest status is attached to completing things, not to starting them. People are celebrated for shipping, for hitting deadlines, for delivering outcomes. Meetings are about removing blockers to completion, not about sharing updates on activity. The metrics that matter are those that reflect actual progress toward strategic objectives, not proxies like hours worked or messages sent.

This shift is not easy. It requires sustained attention from leadership, a willingness to confront uncomfortable truths about how work actually happens, and the discipline to maintain new practices when old habits reassert themselves. But the alternative—an organisation that is perpetually busy and perpetually failing to achieve what matters—is far worse.

Execution is not about doing more. It is about doing what matters, and doing it until it is done.