The Program Whose Strategy Moved: Divestiture at the Stage Gate
Meridian Health's $48M "One Patient Record" program was chartered to consolidate three clinical IT platforms after a merger, with a benefits case built on $9M per year of duplicate licensing and interface savings. Eighteen months in, the new CEO has announced the divestiture of the behavioral health division, which contributed 30% of the integration scope and 22% of projected savings. Two of six component projects are mid-build; $19M is committed. The sponsor says "the business case still stands" and wants to hold the next stage gate on schedule. The PMO's benefits register has not been re-baselined since charter approval, and the strategic plan refreshed last quarter does not mention the program.
1. The gate is in three weeks. What analysis must the program manager complete before it, and who must see it?
Read the worked answer
The program manager's obligation is strategic alignment, not schedule preservation.
Analysis required
- Re-derive the benefits case against the current strategic plan: strip the divested division's scope and its 22% of savings, then test whether the residual benefits still justify the residual cost.
- Quantify the remaining scope: which of the six components lose their justification, which have dependencies on divested platforms, and what the incremental cost-to-complete is for each option (continue full, descope, terminate and transition to operations).
- Identify new benefits the divestiture may create (smaller integration footprint, faster consolidation of two platforms) - the case may survive in altered form, but only if rebuilt.
Audience The sponsor alone is insufficient. A sponsor who has publicly said "the case still stands" is an advocate and has an anchoring bias. The output belongs to the program's governing body, which owns strategic fit, with the benefits owner and finance validating the numbers.
Bringing a rebuilt case rather than a status report is what turns the gate into a real decision.
2. The sponsor argues that stopping now wastes the $19M already spent. How should the program manager respond?
Read the worked answer
Sunk cost is not a decision criterion, and the program manager should say so plainly but respectfully.
The relevant question is marginal: from here, does the remaining spend produce benefits that exceed the remaining cost, given the company we now are? The $19M is the same number whether the program continues or stops, so it cannot discriminate between the options. Framing it as "we lose $19M" is also factually wrong - part of that spend produced assets with residual value (the consolidated data model, the decommissioned interfaces) that survive termination.
What the program manager can legitimately weigh alongside the economics:
- Transition and demobilization cost, and contractual termination liability.
- Reputational and workforce impact of stopping a clinical program.
- Option value of a descoped version.
Then present the three options with numbers and a recommendation. The program manager's credibility comes from being the person who brought the unwelcome analysis, not the person who defended the plan.
3. What governance artifacts must change if the board approves a descoped program?
Read the worked answer
A descoped program is a different program, and the paperwork must say so:
- Charter/business case - reissued through formal change control, not annotated; new scope statement, new funding envelope, new benefits targets.
- Benefits register and benefits realization plan - re-baselined with the 22% removed and any new benefits added, each with an accountable benefits owner and a measurement method.
- Component transitions - formal closure or re-scoping of affected projects, with dependencies re-mapped and residual deliverables handed to operations.
- Risk register - the divestiture introduces new risks (shared platforms, data separation, staff uncertainty) that did not exist at charter.
- Roadmap and gate criteria - the next gate's exit criteria must be rewritten for the smaller scope, or the program will be measured against a plan nobody intends to execute.
The failure mode to avoid is approving the descope verbally and letting the old baseline live on in the PMO's records.