What Is the Drift Tax? The Hidden Cost of Work That Drifts

Every team pays the drift tax. Almost none of them measure it.

The drift tax is the price you pay when work drifts — when it slides sideways while everyone is busy and every individual task still looks fine. It is paid in rework, in chasing updates, in last-minute rescues, in windows that close before you reach them, and in the slow erosion of trust between people who keep being surprised by each other. It is real money and real morale, and it almost never appears as a line you can point to.

Busy is not the same as in control

Being busy is not the same as being in control: activity is what effort looks like, while control is what effort produces. The trap is that drift hides inside activity. People are working hard, calendars are full, tickets are moving — so the work feels under control. But a team can be maximally busy and still be drifting toward a surprise.

This matters because the data on project performance is sobering. The Standish Group's long-running CHAOS research has for decades found that fewer than a third of projects finish on time, on budget and on scope. The Project Management Institute's Pulse of the Profession has similarly reported that organisations waste close to a tenth of every pound invested to poor project performance. Most of that waste is not caused by dramatic failure. It is caused by drift.

Where the drift tax hides

The drift tax hides in a handful of predictable places, because drift rarely announces itself. It accumulates wherever a small slip can pass unremarked:

• Slipped dates that move a day at a time, so no single slip looks alarming.
• Waiting decisions — work that is technically "in progress" but is really parked behind a choice nobody has made.
• Silent dependencies on another team or supplier that go quiet until it is too late to react.
• Commercial erosion — small, unbilled extras and assumptions that quietly thin the margin.
• Stakeholder drift — the moment when what the client now expects has moved away from what the team is actually building.

Each of these is cheap to fix early and expensive to fix late. The drift tax is the difference between the two. These hiding places are not random: drift collects in seven predictable places, and knowing them by name is what makes the cost spottable before it compounds.

"Bad news early is not a failure. Surprise is." — The Control Standard

Why it compounds

The drift tax compounds because it behaves like interest, not a flat fee. A decision left unmade this week shapes the work done next week, which has to be partly redone the week after. A dependency that goes unmanaged becomes a crisis precisely when there is no slack left to absorb it. Because the cost is paid in scattered hours and quiet goodwill rather than a single invoice, there is no natural moment where someone says "this is what drift cost us." So it keeps growing.

How to stop paying it

You stop paying the drift tax by making drift visible early, while it is still cheap to correct. In practice that means converting uncertainty into a usable control point: a clear owner, a dated next step, a decision or escalation date, and a fallback if things go wrong. Work that has those four things can still go wrong — but it can no longer drift quietly, because the next missing piece is always obvious.

When the same drift keeps recurring — the same chase, the same late decision, month after month — the durable fix is not another rescue but systemising the pain: deciding whether that repeated work is worth a clearer process, an automation, or purpose-built software.

That conversion — from busy-but-drifting to genuinely steerable — is the core practice of project control, and it is what The Control Standard teaches in depth. If you want a fast read on where your own work is drifting right now, the free Drift Report below scores it in about five minutes.