What is execution drift?
Definition
Execution drift is the gradual divergence between what an organisation decided to do and what is actually being done. It builds through small, unrecorded changes: a scope adjusted in one meeting, a deadline quietly moved, a dependency nobody passed on. It usually goes unnoticed until a status review or a missed milestone.
Also called: plan drift, strategy drift, strategy-execution gap
Updated
No plan survives contact with the week. That in itself is not the problem; plans should change. Execution drift is the case where the plan changes in practice but not on record, so different people end up working to different versions without knowing it.
How it happens
Drift rarely starts with a decision to deviate. It starts with an adjustment made in the room: “let’s push the integration to next sprint”, “we’ll leave the German market for now”. The people in the meeting act on it. The plan, the roadmap and the people who were not there do not change. A month later, two teams are building against different assumptions and the steering group finds out at the next review.
The longer the gap between checkpoints, the more drift accumulates unseen. Status meetings exist largely to find it, which is why they make up the largest share of the coordination tax: 8.1 of the 16.5 weekly hours managers itemised in the Coordination Tax Index 2026 (In Parallel, n=247, Pollfish, June 2026).
Why it matters
Drift found late is expensive. By the time it appears in a variance report or a missed launch, the work has been done to the wrong version and the cost is already booked. Drift found the day it happens is a conversation: either the plan changes deliberately, or the work goes back on course.
Execution drift vs context decay
Context decay is about the record: information that was true and quietly stops being so. Execution drift is about the work: activity moving away from the decision. Decay often hides drift, because a stale plan gives nobody anything to compare against.
How In Parallel approaches it
In Parallel records each decision with its status, who made it, when, and the meeting it came from, so people can check later conversations against the source rather than against memory. Risks and open questions stay open until someone resolves them, and Pages are updated after each meeting, which keeps the written plan closer to the work. The surface open risks use case shows this in practice. See also living plan.
FAQ
Common questions
- What causes execution drift?
- Mostly information that does not travel. Decisions change in meetings that not everyone attends, the plan document is not updated, and teams keep working from the version they last saw. Each change can be reasonable; the drift comes from nobody seeing them together.
- How is execution drift different from scope creep?
- Scope creep is one kind of drift: work being added without an agreed change. Execution drift is broader and includes slipping dates, changed priorities and dependencies that move without anyone downstream knowing.
- How do you catch execution drift early?
- Keep a dated record of what was decided and by whom, and compare new conversations against it as they happen rather than at the next quarterly review. The earlier a divergence is visible, the cheaper the choice between correcting course and updating the plan.
Start with your next meeting.
Bring your team in. Use every surface, including every other team's. From €29 per user per month, billed monthly, no commitment.
30-minute demo. We'll show you how meeting signals become a shared record of decisions, owners and risks.