Rebaseline Workshop¶
Facilitated workshop — instantiates Scope Creep Containment
A facilitated session that, when accumulated drift has made the old plan a fiction, deliberately establishes a new authorized baseline and archives the prior trajectory — so scope moves by explicit reset, not silent erosion.
A Rebaseline Workshop is a scheduled, facilitated event whose job is to legitimately move the reference itself — to look at how far the work has drifted from its original charter, decide whether the honest response is a new baseline (rebaseline) or a whole new mandate (recharter), and then establish that new reference on the record. Its defining move is wholesale, authorized reset: rather than adjudicating the next request, it steps back and re-sets the whole perimeter at once, with new authority, capacity, and success criteria attached, and archives the old trajectory so the system remembers what moved and why. It is the archetype's release valve against false rigidity — the mechanism that keeps "hold the line" from meaning "pretend the original plan is still real." It is not a per-request gate; it is the periodic, deliberate act of admitting the plan has genuinely changed and writing down the new one.
Example¶
A state workforce-development program was chartered three years ago to place 2,000 long-term-unemployed residents into apprenticeships. Since then it has absorbed a childcare-subsidy component, a rural-transportation pilot, an employer tax-credit administration duty, and expanded eligibility twice — each added by a well-meaning agreement, none rechartered. Staff are exhausted, the original placement metric looks like failure, and nobody can say what "on track" now means.
The program director convenes a Rebaseline Workshop: two days, the right authorities in the room (the funding agency, the program lead, a labor-department sponsor), and a facilitator. The session lays the accumulated changes on the table against the original charter — the drift is undeniable. Rather than keep measuring against a three-year-old plan, the group decides on a formal rebaseline: a new scope statement that folds in childcare and transportation as authorized components, drops the tax-credit duty as out of mandate, and sets fresh targets and a new capacity envelope. The prior charter and the full change history are archived as the record of how we got here, not deleted. The program leaves the workshop measuring itself against a plan that is finally true.
How it works¶
What distinguishes the workshop from ordinary change approval is that it operates on the reference, not on requests:
- Triggered by accumulated drift, not by a single ask. It is convened when the gap between charter and reality has grown too large to govern change-by-change — often on a signal from a drift monitor or a board's escalation.
- Chooses rebaseline vs. recharter explicitly. Rebaseline updates the operating reference for authorized change; recharter admits the undertaking is now different and needs new authority. Naming which one prevents silent creep from masquerading as continuity.
- Requires the authority to reset. The right sponsors must be present, because a new baseline without new authorization is just a wish.
- Archives the old trajectory. The prior baseline and the change history are preserved, so the reset adds a new reference without erasing the memory of the movement — the anti-amnesia guarantee.
Tuning parameters¶
- Convening threshold — how much drift triggers a workshop. A low threshold rebaselines often (responsive but destabilizing and easy to abuse); a high one lets the plan rot into fiction before anyone resets it.
- Rebaseline vs. recharter bar — how much change forces a full recharter rather than a lighter rebaseline. Setting it loose lets big expansions slip through as mere rebaselines.
- Authority quorum — which sponsors must attend for the new baseline to be binding. Too thin and the reset isn't real; too heavy and it can never be convened.
- Archival depth — how much of the prior trajectory is preserved. Deep archives protect memory and accountability but cost effort to maintain.
When it helps, and when it misleads¶
Its strength is that it gives scope a legitimate way to change: without a rebaseline path, a team either freezes an obsolete plan or lets scope erode silently, and the workshop is the honest third option, echoing the earned-value practice of formally rebaselining a project whose original plan no longer reflects reality.[n1] It converts drift from a source of shame into a governed decision.
Its signature failure mode is rebaseline laundering — convening a reset not because the work legitimately changed but to erase a track record of overruns, so every quarter's failure is absorbed into a fresh baseline and no plan is ever missed because no plan is ever kept. The guarding discipline is to make rebaselining rare, authority-gated, and archived: if the old baseline vanishes and resets happen whenever targets are about to be missed, the workshop has stopped containing scope and started hiding it.
How it implements the components¶
rebaseline_or_recharter_gate— the workshop is that gate in action; it deliberates and enacts the choice between updating the baseline and re-authorizing the undertaking.chartered_scope_baseline— its output is a new remembered reference state: a fresh scope statement with authority, capacity, and success criteria attached.scope_change_ledger— it archives the prior baseline and the full trajectory of accepted changes, preserving the record of how the perimeter moved.
The workshop resets the whole perimeter; it does not adjudicate individual additions — the per-request scope_addition_admission_rule is the Change Control Board's, and the per-change cost trace, the capacity_and_dependency_impact_model, is the Impact Assessment Checkpoint's.
Related¶
- Instantiates: Scope Creep Containment — the workshop is the legitimate reset that keeps boundary integrity from ossifying into fiction.
- Consumes: Scope Drift Dashboard supplies the accumulated-drift signal that tells the program a reset is due.
- Sibling mechanisms: Change Control Board · Scope Change Request Template · Plus/Minus Scope Review · Scope Freeze Protocol · Impact Assessment Checkpoint
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Rebaseline Workshop operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a facilitated session that, when accumulated drift has made the old plan a fiction, deliberately establishes a new authorized baseline and archives the prior trajectory — so scope moves by explicit reset, not silent erosion.
Independent corroboration: The frozen evidence defines Rebaseline Workshop as 'A facilitated session that, when accumulated drift has made the old plan a fiction, deliberately establishes a new authorized baseline and archives the prior trajectory — so scope moves by explicit reset, not silent erosion', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Communication, Facilitation & Learning — Rebaseline Workshop includes features of a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Formal rebaselining is established program, project, and change-management practice.
Review resolution: Both blind reviewers agree that organizational_management is the primary origin. Explicit reconciliation of encyclopedia synthesis disagreement adopts reviewer_a's classification because formal rebaselining is established program, project, and change-management practice. The resulting lineage records alternates=none, origin_mode=single_lineage, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The workshop and the Change Control Board both touch the rebaseline decision, but at different grains: the board triggers a rebaseline when incremental approvals have piled too high and then defers to the workshop; the workshop executes it, producing the new baseline the board will govern against next. The board handles the stream of requests; the workshop handles the occasional reset of the riverbed.
[n1] Rebaselining (earned-value / project management) — the formal act of replacing a project's original performance measurement baseline with a new authorized one when the original no longer reflects the agreed plan, so future performance is measured against a realistic reference. Legitimate rebaselining is authorized and documented; its abuse — resetting to erase overruns — is what the guarding discipline above targets. ↩