Project Control: How to Keep Work Genuinely Under Control
The Seven Places Drift Hides (and How to Spot Each One)
By Andrew Lee Ward 5 min read Updated 27 Jun 2026
Drift hides in seven predictable places: decisions, dependencies, dates, cadence, stakeholders, commercials, and ownership. Each is a lens — a question you run over a piece of work to find where uncertainty is quietly eating the outcome. Drift under a load-bearing pillar is a crisis forming; drift elsewhere is usually a mild fact.
Most teams do not lose control in one dramatic moment. They lose it slowly, while everyone is busy and every individual task looks fine — and when you go back afterwards, the surprise almost always turns out to have been drifting in full view for a fortnight before it became a crisis. The reason it stayed invisible is that drift is not one thing. It is seven, and each hides in a different place.
Think of the list below as lenses, not categories: each is a question you run over an item, a meeting, or a week to find where uncertainty is eating the outcome unnoticed. The cost of leaving them unmanaged has a name — the drift tax — and the reason it matters is well documented. 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, and the Project Management Institute's Pulse of the Profession reports that organisations waste close to a tenth of every pound invested to poor performance. Very little of that is dramatic failure. Most of it is drift.
The first four: drift you can fix without a difficult conversation
The first four kinds of drift — decision, dependency, date and cadence — are the ones a team can usually fix quietly, without a hard conversation: a decision dragged into the open, a dependency given a date, a vague date sharpened, a cadence adjusted.
- Decision drift. A decision is not a discussion; it is a scheduled event with a person attached. The test: what is the next decision this work needs, who makes it, and by when? If the answer is vague, the decision is drifting. When you cannot get the decision date, get the date by which the decision date will be confirmed.
- Dependency drift. A dependency is not controlled by being on a list — it is controlled when it has an owner, a dated next move, and a fallback. The test: what is the next dated point at which this resolves or escalates, and what happens if it does not? Anything sitting as "awaiting response" for several cycles has lost its control point.
- Date drift. Not every date is the same promise. A delivery date, a decision date, a review date, a replan date and an escalation date are five different things, and most "are we on track?" conversations go sideways because two people are talking about two different kinds without noticing. The test: which kind of date is this, and what will the world look like when it arrives?
- Cadence drift. A review loop set at the wrong pace is a slow leak — a week between handover and review, a week between revision and comment, and an urgent piece of work is quietly on a month's timeline. The test: is this item on a cadence that matches its criticality, or running at the rhythm of the diary?
The next three: drift that sits between people
The next three kinds of drift — stakeholder, commercial and ownership — are harder, because they sit between people, between contracts, and between the surface of the work and the person meant to be holding it. Pause before these.
- Stakeholder drift. Projects move at the speed of stakeholder alignment, not the speed of the plan. The test: who really owns this decision on the other side, and what do they need to make it? Mistaking "they were in the meeting" for "they are aligned" is one of the commonest and most expensive errors in service work — which is why deliberate stakeholder management is a control skill, not a soft one.
- Commercial drift. Scope rarely jumps; it creeps. A half-hour of extra advice on Monday, a supportive call on Wednesday, a favour on Friday, and the delivery shape has changed while the commercial shape has not. The test: is the work still clearly covered by the agreed arrangement, and if not, who has flagged it? This is scope creep, and it applies to internal work just as much as client work.
- Ownership drift. The subtlest one. An item has a named owner, but that person has not really picked it up — not chasing, not escalating, just responding to updates about their own work. The test: is the owner actively driving this, or are we chasing on their behalf? Passive ownership is ownership in name only, and it leaks into the other six.
Point the lenses at what matters, not at everything
The seven lenses pay off only when you point them at what matters: the discipline is not to run all seven over every line of the plan, but to aim them at the handful of things the outcome actually depends on. A useful first question for any drifting decision, dependency or sign-off is whether it sits on the critical path — the longest chain of dependent steps that sets the earliest possible finish. If it does, the end date is already moving in slow motion. If it does not, the item is usually noise dressed up as a problem.
"Almost every ugly surprise, looked at afterwards, turns out to have been one of these seven — drifting in full view for a fortnight before it turned into a crisis." — The Control Standard
That is the payoff. Running the seven lenses takes two or three minutes, and it converts the abstract worry that something is "off" into a specific place to look. The wider practice of keeping work under control is what The Control Standard develops in full. If you want to see which of the seven is biting your own work right now, the free Drift Report below scores it in about five minutes.
Frequently asked
What are the seven types of drift?
How do I use the seven drift lenses in practice?
Which kind of drift matters most?
Is scope creep the same as drift?
What is the difference between decision drift and dependency drift?
What is ownership drift?
How is this different from a RAID log or risk register?
Keep reading
What Is the Drift Tax? The Hidden Cost of Work That Drifts
The drift tax is the invisible, compounding cost of work that slides sideways while everyone stays busy: rework, chasing, last-minute rescues, missed windows, eroded trust and personal stress. It rarely appears as a line on the P&L, which is exactly why it goes unmanaged — and why it quietly grows.
TermScope Creep
Scope creep is the gradual expansion of a project's work beyond what was agreed, without a matching change to the time, budget or commercial terms. It rarely arrives as one big request — it accumulates from small, reasonable-sounding extras — which is why the delivery shape can change completely while the contract stays still.
TopicProject Control: How to Keep Work Genuinely Under Control
Project control is the practice of keeping work predictable and steerable — converting uncertainty into clear owners, dated next steps, decision points and fallbacks — so problems surface early instead of as surprises. It is not about controlling people; it is about controlling drift, signals and outcomes.
GuideWhy Is My Team Busy But Still Missing Deadlines?
Your team misses deadlines while staying busy because activity is not control. The work slips in the gaps between decisions, dependencies and handoffs — places effort never reaches. Everyone is occupied, but uncertainty is not shrinking, so the date moves a day at a time until the slip surfaces as a surprise.