Recovering an Implementation Business Case When the Original Owner Leaves
On mid-size implementation projects, the business case often lives with one person. When they leave, executives need a corrective playbook fast. A short light guide.
When the only person who understood the case is no longer in the room
If the project pauses when one person goes on leave, you don't have a business case — you have a memorized one.
On mid-size implementation projects, the business case often lives more in one person's head than on paper. When that person leaves — for a new job, a long leave, or a reorg — the project goes blurry. The team continues executing, but the rationale for trade-offs is gone. By the time anyone notices, the project has drifted from its original justification.
This is the single point of failure pattern at the document level. The corrective is not a heroic effort to reconstruct what the original owner knew. It's a short executive intervention that makes the case re-defensible from the artifacts that exist.
“When our implementation lead left, I asked the new lead to walk me through the business case in 20 minutes. They couldn't. So we spent the 20 minutes rebuilding it from what was actually written, not from what we thought was written. It was a different case than I'd remembered.”
- Week 1Pull every artifactCharter, business case, signed approvals, slide decks, email threads. The new owner reads everything in chronological order.
- Week 1, endRebuild the case from artifacts onlyNew owner writes the business case as it stands — no inference about what 'must have been' agreed. If it isn't in writing, it isn't in the case.
- Week 2Sponsor reconciliation30-minute meeting with sponsor. Compare reconstructed case to sponsor's recollection. Differences are decisions to make, not facts to recover.
- Week 2, endResigned and circulatedReconciled business case is signed by sponsor and new owner. Circulated as 'business case v2' with explicit note that v1 is superseded.
Reconstruction discipline
0 / 5- Build the case only from artifacts that existed before the owner left
- Mark every gap explicitly — do not paper over it
- Bring gaps to the sponsor as questions, not as proposals
- Sign the reconstructed case as v2; archive v1 with a date stamp
- Add the sponsor and at least one backup as named stakeholders on the new case
The discipline of building the case only from artifacts is what makes this work fast. Trying to reconstruct what was 'understood' takes weeks and produces a document everyone politely accepts and quietly distrusts. Building from artifacts produces a thinner case, but it's a defensible one — and any gaps become explicit decisions that the sponsor either makes or escalates.
For the related pattern around silent disagreement on creative work, see the creative silent-disagreement version. For prevention rather than correction, see the twelve common business case mistakes.