Why is everyone busy but nothing gets done. It is the question I get asked most often, usually in a corridor after a quarterly business review, from someone who lowers their voice slightly, as if the observation is a small act of disloyalty. It is not. It is usually the most accurate sentence spoken all day.
I hear it from chief executives, chief operating officers, chief financial officers, chiefs of staff and heads of enterprise PMOs, standing outside the room where the quarterly numbers just went up. Calendars are full from eight until six, every dashboard the functional leaders present is green, and the thing the CEO named as the priority at the start of the year has not moved. The instinct is to conclude people are busy with the wrong things, and sometimes that is right, but it is rarely the interesting part. I go further into the underlying cause, what I call Ownership Fog in cross-functional execution, in the main piece on this problem. This article stays with one symptom of it: the busy, flat organisation, and how to read it honestly.
Full Calendars Are Not Evidence of Progress
A full calendar tells you a person’s time has been claimed. It does not tell you by what, or whether the thing that claimed it was the outcome the business actually needs to move. I have sat with heads of function who could account for every hour of their week and could not tell me, without checking, whether the number the CEO cares about had shifted at all. That is not a failure of diligence, their diaries were full of exactly the meetings a conscientious leader is supposed to attend. Activity versus outcomes looks like a semantic distinction and is not, it is what a program reset day or a functional leader forum exists to surface, because from inside any single week the two look identical.
Green Workstreams, Red Outcome, No One Lying
Here is a pattern I see often enough to give it a name: the Green Dashboard. Five months of green workstream status, reported honestly by five or six capable functional leads, and an outcome that misses by a full quarter, without one false status report in the whole run. Each function had genuinely done what it committed to, on time. The dashboard was not lying, it was describing the wrong thing: each leg of a relay, never the relay itself, the baton moving from one function to the next without being dropped for three weeks while someone works out whose desk it is on. Busy but not productive is not a contradiction once you see it this way, it is the predictable output of a system where every function is measured on its own leg and nobody is measured on the finish line.
What Your Dashboard Measures and What It Cannot See
A status dashboard answers one question well: did this function do what it committed to. That is legitimate, and a well-run function should answer it in green most weeks. But it is structurally blind to the question that matters to the CEO, whether the outcome depending on four or five of those functions in sequence is any closer to real. A wall of green cells only proves no individual function is currently the visible bottleneck, it says nothing about the handoffs between them, where cross-functional outcomes actually live or die. Organisational drag rarely shows up as a red cell, it shows up as the gap between what the dashboard says and what the CEO feels in the room.
The Coordination Work Nobody Is Assigned
Every additional function an outcome has to cross adds coordination work: someone has to chase the handoff, reconcile two functions’ different definitions of “done,” resolve the sequencing argument nobody scheduled a meeting for. I call this the complexity tax, a real tax, paid whether or not anyone budgeted for it. That work is invisible on every report in the building, because it belongs to no line item and no job description, so it happens in the gaps of everyone’s actual job, usually late in the day, by whoever cares most rather than whoever is best placed to do it.
Ownership Fog is the condition where every task in a cross-functional initiative has a named owner and the outcome itself has none. I unpack that condition fully in the pillar piece on cross-functional execution and Ownership Fog, worth reading if this pattern is familiar. Here is the generous reading I offer leaders who assume their people must be at fault: your people are not busy with the wrong things, they are busy carrying the coordination cost of an outcome nobody owns, and that cost expands to fill the ownership vacuum. It is not laziness, and it is not poor prioritisation. It is a structural gap doing what structural gaps always do, getting quietly absorbed by whoever is conscientious enough to notice it.
Under-Resourced or Under-Owned? How to Tell the Difference
The two conditions call for opposite remedies, and most executives reach for the resourcing answer by default. Under-resourced looks like this: the work is clearly assigned, the plan is realistic, and the people doing it can tell you, specifically, what they cannot get to. Under-owned looks different: the work is assigned everywhere, nobody is short of tasks, and yet when you ask who is accountable for the outcome itself, rather than a piece of it, you get silence, or five different names, or one name offered without conviction.
Adding headcount to an under-owned outcome does not fix it. It adds another well-intentioned person to the relay, running their own leg competently, and the outcome remains as unowned, just with a larger cast. The tell is simple: if more people made the numbers worse before they improved, because inducting them consumed the only coordination capacity available, you were under-owned, not under-resourced.
Run the First 48 Hours Backwards
The First 48 Hours is a mechanism I use constantly, and its usual form is a test run forward: a decision is only believed when something visibly stops, starts or changes in the first 48 hours after it is made. Most leaders only use it that way, as a check before a decision. It also works run backwards, as a diagnostic on something already flat. Take the outcome that has not moved, go back to the meeting where it was agreed, and ask what visibly stopped, started or changed in the two days after. If the honest answer is that calendar invitations went out and a document got created, you have found the exact moment the outcome stopped being real, and it was not last quarter under a vague heading of “execution issues,” it was that week, in the gap between the decision and a first visible action. That is a far more useful diagnosis than concluding people are too busy, because it points at a decision moment you can redesign, rather than a workforce you cannot simply tell to work harder.
Three Things to Look at Instead of Utilisation
When a dashboard is green and an outcome is flat, I stop asking how utilised teams are and ask three questions instead. First, who owns the outcome end to end, not a piece of it, and can they name the next handoff without checking. Second, what visibly changed in the 48 hours after the decision was made, run backwards as above. Third, where is the coordination work actually happening, and who is absorbing it unpaid and unnoticed. The answers tell you more about whether an outcome will land than a full quarter of green status ever will.
Once you can see the pattern in your own dashboards, the useful move is not another status template, it is naming a single owner for the outcome itself. I set out how to do that cleanly in the piece on what to do once you can see the lack of ownership in your teams, which picks up where this diagnosis leaves off. Rob Cross and colleagues found something similar studying collaborative work inside large organisations: time spent coordinating across roles has grown sharply, and it concentrates on a small number of people who quietly absorb it, unmeasured, on everyone else’s behalf (Harvard Business Review, “Collaborative Overload”).
If you just walked out of a quarterly business review with a wall of green workstreams and a number that still has not moved, that is the moment to have this conversation properly, rather than filing it under next quarter’s agenda. Get in touch to talk it through.
