Status drift: when the report and the work quietly diverge
Status drift is the slow divergence between a task's reported status and its real state — “on track” stays on the board long after the work has stalled.
Nobody updates the status to say it slipped, so the green stays green. The drift is invisible right up until a deadline forces the real state into the open.
What causes status drift?
Status is set once and rarely revisited. A task marked “in progress” or “on track” keeps that label by inertia, even as the work stalls — because updating it downward takes effort and admits a slip.
The more places status lives — a board, a doc, a standup, a thread — the more room there is for the label and the reality to come apart without anyone noticing.
How do you catch status drift early?
By comparing the reported status against the evidence the work actually leaves behind — commits, deploys, activity — instead of trusting the label. When the two diverge, that's the drift, and surfacing it early is the whole game.
Frequently asked
Is status drift the same as a missed deadline?
No — a missed deadline is the moment drift becomes visible. Status drift is the period before that, when the report still says fine but the work has already stopped matching it.
Stop being the reality check.
A small founding cohort — India + GCC. A direct line to the founder.