This suite is a complete integration program — charter through closeout — for a fictional health plan acquisition. Forty-seven artifacts, seventy-three named people, one set of numbers that every document derives from. Two things about it are worth knowing before you open anything else: what the colored annotations are, and how forty-seven documents are kept from contradicting each other.
1. The colored annotations are commentary, not part of the document
A real integration charter does not contain a colored box explaining why its constraint order is counterintuitive. These artifacts do. The annotations are the program manager's reasoning, added for the reader — they sit alongside the artifact rather than inside it. Strip them out and what remains is the document as it would actually have been issued. They are here because the reasoning behind a decision is the part worth showing, and a real deliverable never explains itself.
They form a deliberate ramp: neutral for a note, warm for a caution, red for the thing that matters most. Nothing in the artifact itself uses these colors.
| Annotation | What it marks | Example |
|---|---|---|
| Reasoning | Why a decision came out the way it did | Why coexistence duration selects the integration architecture |
| Trap | Where the obvious move is the wrong one | Terminating a vendor on the earliest available date causes an outage a month later |
| Load-bearing | The argument the artifact rests on, or the failure that would end badly. Capped at two per document. | In healthcare the two identity-matching error types are not symmetrical |
| Defensible position | What to say when the choice is challenged | Why the program refused to plan to the contractual maximum |
1.1 Point-in-time — why documents do not know their own future
Every artifact is dated and is true as at that date. A pre-close document contains nothing that was only knowable after closing. The risk register issued in February identifies the risk that materializes in April, sizes it, assigns it — and has no idea it is about to happen.
This is deliberate, and it is the hardest constraint in the suite to hold. A completed program written with hindsight flattens: every decision looks obvious, every gate reads approved, and the crisis loses its force because the reader can see it coming. Keeping period documents genuinely ignorant of the ending is what makes the program readable as something that happened rather than something that was narrated. Where a later view is genuinely useful, it appears as a separately dated annex — never as an edit to the original.
2. Where to start
If you have ten minutes and want the program’s argument rather than its documents:
- Integration Charter — the constraint priority order, and the rule that makes every later decision auditable against it
- Clean Team Protocol — why an acquirer may not look at the data that determines its own integration cost
- Application Disposition Matrix — twenty-two systems, each one a defended decision
- Data Migration & EMPI Strategy — the identity problem, and why the two error types are not symmetrical
- Closeout Report — what was delivered, what was cut, and where it went
One thing worth knowing as you read across documents: every figure in the suite comes from a single controlled source. The synergy target, the budget baselines, the dates, the seventy-three names — each appears in one place and every artifact derives from it, so a number quoted in the charter is the same number quoted in the closeout report twenty months later. Forty-seven documents that disagree with one another would say more about the author than the program does.
3. What is fictional and what is not
| Fictional | Real |
|---|---|
| ACME Health, Cumberland Valley Health Plan, Cheatham Mutual Holdings and every vendor | The regulatory framework — HSR, state Form A approval, HIPAA business associate obligations |
| All seventy-three named people | The antitrust constraints on pre-close conduct, and the Clean Team practice that follows from them |
| Every number, date and dollar figure | The methods — identity resolution, estimate classes, TSA exit management, disposition analysis |
| The transaction and its outcome | The failure modes, which are drawn from how these programs actually go wrong |
The program ends with damage, and that is a choice. It runs late against its plan, spends its contingency and management reserve, defers real scope, and has change requests that were rejected. It also lands inside its contractual limits and meets its synergy commitment. A portfolio program where everything went well demonstrates nothing about program management — the interesting questions are what gave, who decided, and whether the arithmetic ties. It does: the approved change requests sum exactly to the variance the closeout report reports.