Project Drift: How to Spot It Weekly

Project drift is the operational twin of scope creep, and firms that watch for creep often miss drift entirely.

Scope creep is about the client asking for more. Drift is about the firm delivering less — slipping quietly within the scope it already committed to.

Scope creep grows the work. Drift shrinks execution. Both hurt margin, but they hurt differently, and they're caught differently.

This is our POV on how drift shows up, where it comes from, and the weekly read that catches it before the project is red. Drift is often easier to catch when project phases are well-structured to begin with — see how to build project phases that hold under delivery pressure for the structural foundation.

Drift is not scope creep

Scope creep looks like: “The client asked for another round of revisions.”

Drift looks like: “We still owe the client that third round of revisions we promised two weeks ago and it hasn't started yet.”

Scope creep adds work to the project. Drift leaves promised work undone. Both show up as over-budget or late projects, but the mechanisms are different.

Firms that focus exclusively on scope management miss drift because they're watching the wrong side of the equation.

The three early indicators

Before drift produces a visible problem, it produces three measurable signals:

1. Rising burn vs. plan

Hours burning faster than planned, without corresponding scope expansion. If week 4 was budgeted for 60 hours and burned 78, that's drift — the work took longer than estimated.

One week of 10–15% overrun is noise. Three weeks running at 10% overrun is drift.

2. Shifting ownership

A project that was supposed to be led by one senior and staffed by two juniors is suddenly being done primarily by the senior. Or work that was scoped for a mid-level is being escalated to a partner.

Ownership shifts are usually invisible on the project plan but show up immediately in time data if you're looking. The project is still tracking to hours, but the mix is wrong — and the mix wrong means margin wrong.

3. Missed phase gates

Projects are usually structured with phase gates (kickoff, discovery complete, design approved, delivery). A phase that was supposed to close in week 3 but closes in week 5 is drift — even if overall budget still looks fine.

Late gates accumulate. A project that's two weeks late by week 5 is typically four weeks late by week 10. The slope compounds.

Where drift comes from

The counterintuitive finding: most drift isn't caused by problems within the project. It's caused by priority competition across the firm.

A senior consultant's project drifts not because the work is harder than expected but because she also got pulled into a sales meeting, a proposal review, and a crisis on another engagement. Her attention is distributed across four things; the project gets what's left.

This is why drift is often invisible from within the project team. The project looks fine from the inside. The slippage is happening because the staffing model assumed full attention that isn't being given.

Which means drift is a firm-level problem, not a project-level problem. The fix is usually in capacity planning and staffing, not in project management.

The weekly read

The 15-minute weekly project review catches drift if it's structured correctly. Three questions:

1. Actuals vs. plan. Did we burn what we expected? If not, why — scope, estimating, or attention?
2. Ownership. Is the right person doing the right work this week? Or has someone else absorbed the load?
3. Phase progress. Are we hitting the milestones this week that we said we'd hit?

The conversation is not “is anything wrong?” — project leads always say no. The conversation is “let's look at the three specific signals and see if any are flashing.”

When the signals are flashing, the decision options are always the same: accept the drift (and adjust expectations with the client), re-staff (and restore the planned mix), or de-scope (and reduce what we committed to deliver).

Each of those is a hard conversation. Each is easier when you have it in week 3 than when you have it in week 9.

The color-coding fallacy

Most services firms track project health with red/yellow/green indicators. This is fine until you realize that a red project didn't start red — it started green, drifted to yellow, and then turned red.

The goal isn't to catch red projects faster. It's to catch yellow projects before they turn red.

The trigger for yellow isn't “the partner feels worried.” It's:

• Any week with >10% over plan burn
• Any ownership mix more than 20% off from staffing plan
• Any phase gate missed by more than 3 days

Concrete triggers, measured weekly, flagged automatically. Human judgment isn't the right layer for signal detection — it's the right layer for intervention once the signal is flagged.

What to change

If drift is a persistent issue at your firm:

1. Separate drift from creep in your project reviews. They have different root causes and require different interventions.
2. Instrument the three signals. Actuals vs. plan, ownership vs. plan, phase progress vs. plan.
3. Pay attention to cross-project priority competition. Drift is usually a firm-level capacity issue, not a project-level execution issue. See the weekly partner dashboard for how to spot this cross-firm.

Firms that do this catch drift 3–4 weeks earlier than firms that don't. That lead time is the difference between an expensive recovery and a routine adjustment.

Octayne's Project Management surfaces weekly burn-vs-plan, ownership mix, and phase progress automatically so project leads see drift the week it starts. Book a demo to see the weekly project review on your data.