Why Is My Team Busy But Still Missing Deadlines?

If your team is busy all week and still misses deadlines, the problem is rarely effort. It is the gap between activity and control — the work slipping sideways through decisions, dependencies and handoffs while everyone stays occupied.

Why a busy team still misses deadlines

A busy team misses deadlines because activity and control are not the same thing. Busyness is what effort looks like; control is what effort produces. A team can answer hundreds of messages, attend a full diary of meetings and move tickets all week, while the one decision that gates the deadline sits unmade and the one dependency it depends on goes quiet. The honest test of a week is not how occupied people were. It is whether the team knew more about the real position of the work on Friday than it did on Monday. If uncertainty did not shrink, the effort became motion, not progress — and the date kept moving in the background.

This is not a niche failure. Asana's Anatomy of Work Global Index 2023 found that knowledge workers spend roughly 58% of their time on "work about work" — coordinating, chasing status, searching for information and switching between tools — rather than on the skilled work itself.¹ When more than half the working week is spent around the work, deadlines do not slip because people are idle. They slip because effort is being absorbed by coordination that never quite resolves the few things that matter.

Where the deadline actually slips: decisions, dependencies and handoffs

The deadline slips in the seams between people, not in the visible tasks. Most slips trace back to one of three quiet places:

• Waiting decisions. Work that is technically "in progress" but is really parked behind a choice nobody has made. A decision is a scheduled event with a person attached, not an ongoing discussion. When it has no date and no decider, it drifts, and everything downstream drifts with it.
• Silent dependencies. Something you are relying on from another team, supplier or stakeholder that has gone quiet. "Awaiting response" for three cycles is not patient tracking — it is a dependency that has lost its grip and is now slipping the date without anyone watching it do so.
• Lost handoffs. Work that everyone assumes someone else is holding. The designer thinks the project manager has it; the project manager thinks the developer picked it up; nobody is actually driving it. The item has an owner in name and no owner in practice.

These are three of the seven places drift hides — the predictable seams where the drift tax quietly accumulates. None of them shows up as a missed task on a board. Each shows up later as a missed deadline, and by then the cheap moment to fix it has passed.

"Looks busy" vs "is under control": how to tell them apart

A team that looks busy and a team that is under control can be indistinguishable from the outside, especially to the people doing the work. The difference is not effort; it is whether the state of the work is legible and steerable. The table below is the fastest way to tell which one you are running.

The right-hand column is not more work than the left. It is the same work, made visible enough to steer. As the book puts it:

"Busy is what effort looks like. Controlled is what effort produces." — The Control Standard

How to diagnose it on your team today

Diagnose a busy-but-slipping team by working backwards from a real slip, not forwards from a plan. Looking forward hides drift, because everything in progress looks fine; looking backwards exposes the exact seam where the work stopped moving. Three concrete steps you can run this week:

1. Trace one missed deadline to its last real movement. Take a recent slip and find the last point where the work genuinely advanced — a decision made, a deliverable shipped, a dependency resolved. The stretch between that point and the deadline is where it drifted. Name what was actually missing there: a decision, an owner, a date, or a dependency nobody chased.
2. Run the "two-minute" test on your three most important items. For each, ask: could someone who was not in the meeting read its real state in two minutes without asking me? If not, the item is being remembered, not controlled — and remembered work is exactly the work that slips unnoticed.
3. Hunt for stagnant lines. Walk your tracker or board and flag every item whose update is the same as it was a week ago: "still in progress", "awaiting response", "with client". A line that has not moved in seven days is not a status. It is a signal that the item has no live owner, date or next move — the early warning of a slip you have not been told about yet.

If the same item keeps failing the same step, you have found a recurring drift pattern, not a one-off. That is the moment to fix the system around the work rather than rescue this instance of it.

Why this is a system problem, not a people problem

A busy team that misses deadlines is usually showing you system information, not a verdict on the people. When researchers investigate teams that supposedly "won't take ownership", they land repeatedly on unclear roles, thin context, absent authority and low trust in the process — not on weak or lazy individuals. McKinsey's work on decision-making describes a closely related failure: decisions that have nominally been delegated drift back upward, because the less senior person does not feel confident taking the final call, so the manager keeps pulling it back.² From the manager's seat that reads as "my team won't own things"; from the contributor's seat it reads as "the decision gets overruled anyway, so why push?". Both blame the other person. Neither notices the system producing the drift on repeat.

Harvard Business Review has a precise name for what this produces: the predictable surprise — the disaster you should have seen coming, which sat half-flagged and half-owned at the edge of the picture for weeks before it went off.³ A missed deadline that "came out of nowhere" almost never did. It was visible to someone, somewhere, as a forming slip — it was simply never converted into something the team tracked and acted on. That is why the fix is rarely "work harder". It is to make drift visible early, while it is still cheap to correct.

How to stop the slips without adding more meetings

You stop the slips by converting uncertainty into a control point on each item that matters, not by adding oversight. In practice that means giving every important piece of work four things: a clear owner who is driving it, a dated next step, a decision or escalation date, and a fallback if it goes wrong. Work with those four can still go wrong — but it can no longer drift quietly, because the next missing piece is always obvious. This is the core practice of project control, and it is what The Control Standard teaches in depth.

Two adjacent moves do most of the remaining work. First, change what a status update is allowed to say: ban "on track" on its own and ask for the next dated move, the real blocker and the decision that would unstick it. Second, if you keep finding that everything routes through one person before it can progress, the deadline is gated by a bottleneck, not by capacity — see how to stop being the bottleneck for the fix. Neither needs another recurring meeting. Both make the work legible enough that slips announce themselves while there is still time to act.

If you want a fast read on where your own team's work is drifting right now, the free Drift Report below scores it in about five minutes.

1. Asana, Anatomy of Work Global Index 2023, reports that knowledge workers spend roughly 58% of their time on "work about work" — coordination, chasing status, searching for information and switching between tools — rather than on skilled work. See Asana, "Why work about work is bad" (asana.com/resources/why-work-about-work-is-bad). These are vendor survey estimates; the direction is consistent with a longer line of research on fragmented knowledge work. ↩

2. Aaron De Smet et al., "The limits of RACI — and a better way to make decisions", McKinsey & Company, describes the common pattern in which delegated decisions are escalated back to senior people because less-senior colleagues do not feel empowered to take the final call (mckinsey.com). ↩

3. Michael D. Watkins and Max H. Bazerman, "Predictable Surprises: The Disasters You Should Have Seen Coming", Harvard Business Review, April 2003 (hbr.org/2003/04/predictable-surprises-the-disasters-you-should-have-seen-coming). ↩