Keel
  1. Keel
  2. Blog
  3. Catching plan drift

Plan drift: how to catch it before the launch slips

Plan drift is the gap between what the plan says and what is really happening. Learn the common signals of drift and simple rules that catch it early.

Cover: Plan drift: how to catch it before the launch slips

Plans rarely fail in one dramatic moment. They drift: a little further from reality every day, until the gap is too big to hide.

What drift looks like

  • A task marked in progress with no commits for six days.
  • A task marked done while the tasks depending on it are still blocked.
  • A task past its due date that nobody has touched.
  • A delay mentioned in chat that never reached the plan.

None of these is a crisis on its own. Together, they are why the launch review turns into a surprise.

Why people miss it

Drift is quiet. Nobody announces that they stopped working on a task. The signals are spread across tools: commits in one place, chat in another, the plan in a third.

Rules that catch it

You do not need AI to detect most drift. Simple, testable rules do the job:

  1. Stale activity: in progress, no linked activity in N days.
  2. Broken order: done, but with blocked dependents.
  3. Overdue: past due and not done.

Where AI helps is in explaining the mismatch in plain words and linking it to evidence, so the alert says why, not just what.

Act on it early

A drift alert is only useful if it leads to a decision: re-plan, re-assign, or confirm the task is fine. The cheapest time to make that decision is the day the drift starts.

Setting thresholds

The right number of days for a stale-activity rule depends on the work. A two-day task with no activity for three days is a concern; a two-week task might not be. Start conservative, for example five working days, and tune it after a few weeks based on how many alerts turned out to matter.

Avoid alert fatigue

An alert nobody trusts is worse than no alert. Keep the rules few, show the evidence with every alert, and let people dismiss an alert with a reason so the rules can be tuned. Precision matters more than catching everything.

A weekly drift review

  1. List every open drift alert.
  2. Check the ones on the critical path first.
  3. For each, decide: re-plan, re-assign, or confirm it is fine.
  4. Record the decision so the same alert does not come back unanswered.

Keel runs drift rules against your plan and activity and shows each alert with its evidence. See launch health and drift.

Questions

What is plan drift?

A mismatch between what the plan says and what is actually happening, such as a task marked in progress with no recent activity.

How do you detect plan drift?

With simple rules: no linked activity in a set number of days, done tasks with blocked dependents, and overdue work, each shown with its evidence.