Project Drift Correction Review¶
Governance review — instantiates Divergence Detection and Correction
Periodically compares a project's current work against its own charter, scope, and decision record to tell disciplined adaptation apart from unjustified drift — and resets scope when it has drifted.
Every project accumulates small course changes, and each one looks reasonable on the day it is made. Project Drift Correction Review is the recurring checkpoint that holds the sum of those changes against the project's own charter — the problem it was chartered to solve, the scope it was funded for, the decisions logged along the way — and asks the one question a busy team stops asking: are we adapting on purpose, or have we drifted into a different, less justified project without ever deciding to? Its defining move is that the reference is internal and documentary: a single bounded project judged against its own recorded intent, by the people accountable for it. When the gap is real, this review is also empowered to close it — to re-baseline the scope, revive the original goal, or formally ratify the new direction so the project once again matches a decision someone actually made.
Example¶
A six-person team was funded to ship a self-serve onboarding flow that would cut first-week support tickets. Ten weeks in, the quarterly drift review lays the current backlog beside the original one-page charter. The distance is stark: the last month of work has gone almost entirely into an admin dashboard that nobody in the charter asked for, added because two large customers requested it in a sales call. Support-ticket reduction, the funded target, has not moved. The review's diagnosis frame separates the candidate causes — is this a better goal discovered (in which case re-charter it explicitly), incentive pull (sales steering engineering), or scope leakage (yes-to-everything)? The read is incentive pull with no decision behind it. The correction is a re-baseline: the dashboard is spun out as its own funded initiative, the onboarding scope is restored, and the recovery target is set not at "flow fully shipped" but at "next sprint's work maps to the onboarding charter again" — the point where ordinary sprint planning can resume without this review hovering. What the team avoids is the quiet failure where a project ships something real, and entirely beside the point it was funded for.
How it works¶
- Lay work beside the recorded intent. Put the current state — backlog, demos, spend — next to the charter, scope statement, and decision log. The distance measure is qualitative: how far has what we are building drifted from what we said we would build?
- Diagnose before correcting. Route the gap through a small cause frame — discovered-better-goal, incentive pull, scope leakage, capacity shortfall, stale target — because each demands a different fix.
- Choose the matching correction. Re-baseline scope, re-charter explicitly, cut the added work, or reallocate — traceable to the diagnosed cause, not a blanket "get back on plan."
- Set a recovery target, not the finish line. Define the intermediate state at which the project is "back on track" enough for normal delivery cadence to take over.
Tuning parameters¶
- Review interval — monthly, per-milestone, or on-demand. Frequent reviews catch drift early but tax the team with governance; sparse reviews let scope wander far before anyone looks.
- Drift tolerance — how much deviation from charter is "healthy adaptation" before it counts as drift. Tight tolerance protects the original goal but can suppress genuine learning; loose tolerance invites goal substitution.
- Correction authority — whether the review can re-baseline scope itself or only recommend it. More authority means faster correction but concentrates judgment in the review body.
- Evidence depth — a glance at the backlog vs. a full trace through the decision log. Deeper evidence catches subtle goal substitution but costs preparation time.
When it helps, and when it misleads¶
Its strength is naming a failure that hides in plain sight: not a late or broken project, but one busily succeeding at the wrong thing. By anchoring on the decision record, it separates legitimate pivots (which get re-chartered) from scope creep and quiet goal substitution, and it blunts escalation of commitment — the drift that continues because too much has already been invested to admit it changed.[n1]
Its failure mode is hidden target shift: if the charter itself is silently edited to match wherever the work has wandered, the review will always report "on track" while measuring against a moving goalpost. It can also curdle into bureaucratic drag, second-guessing every adaptation until the team learns to route around it. The guarding discipline is to treat the target as revisable only explicitly and on the record — a re-charter is a logged decision, never a retroactive edit — so that adaptation stays honest and drift stays visible.
How it implements the components¶
target_distance_metric— the qualitative gap between current work and the chartered scope/decision record; direction, not activity count.cause_diagnosis_frame— the discovered-goal / incentive-pull / scope-leakage / capacity / stale-target frame that decides which correction applies.correction_rule— the re-baseline, re-charter, cut, or reallocate action, traceable to the diagnosis.recovery_target— the intermediate "back on track" state at which normal delivery cadence resumes.
It deliberately does not implement independent_signal_check or escalation_path — this review trusts internal documentary evidence and fixes the project in place. Auditing many distributed implementers against a written intent with independent evidence, then routing the gap upward, is the job of its near-twin Policy Drift Review; the separating components are independent_signal_check and escalation_path.
Related¶
- Instantiates: Divergence Detection and Correction — the periodic, charter-anchored detect-and-correct loop for a single project.
- Sibling mechanisms: Policy Drift Review · Model Training Divergence Monitor · Runbook-Based Course Correction · Loss-Limit Correction Rule · Negotiation Derailment Repair Protocol · Process Control Alarm and Tuning · Learning Remediation Loop
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Project Drift Correction Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it periodically compares a project's current work against its own charter, scope, and decision record to tell disciplined adaptation apart from unjustified drift — and resets scope when it has drifted.
Independent corroboration: The frozen evidence defines Project Drift Correction Review as 'Periodically compares a project's current work against its own charter, scope, and decision record to tell disciplined adaptation apart from unjustified drift — and resets scope when it has drifted', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Intervention, Treatment & Transformation — Project Drift Correction Review includes features of a direct treatment or transformation applied to a target to change its state or condition, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Comparing current work against charter, scope, and decisions is canonical project-governance practice.
Related originating lineages:
- Engineering & Design — The engineering_design tradition materially shaped Project Drift Correction Review through its own practice of physical-system design, process control, reliability, and safety engineering.
- Systems Thinking & Cybernetics — Feedback and divergence correction materially shape the recurring detect-and-reset loop.
Review resolution: Both blind reviewers agree that organizational management is the primary origin. Explicit reconciliation resolves reported ambiguity, alternate origin disagreement. Formative alternate lineages are retained as engineering_design, systems_cybernetics; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Attribution caveat: The exact encyclopedia label appears to synthesize established practices; the primary domain identifies the strongest formative lineage, while the alternates record material ingredients rather than downstream uses.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Escalation of commitment — the tendency to keep investing in a chosen course because of what has already been sunk into it, rather than on its remaining merits. A charter-anchored drift review is a structural counter: it re-evaluates against original intent on a cadence, independent of how much is already spent. ↩