Rollout Postmortem

At the end of each phase, run a structured postmortem. Not a retrospective — a postmortem. Retrospectives ask "what went well and what could be better?" Postmortems ask "what happened, why did it happen, and what changes so it does not happen again or can be reproduced if it was good?" The rollout that does not run postmortems between phases repeats its mistakes at scale. The rollout that does run them carries institutional learning forward at every phase transition. The discipline is not difficult. The discipline is consistently skipped in favor of moving faster.

ROLLOUT POSTMORTEM — [Phase Name]
Date: [Date]
Facilitator: [Name]
Attendees: [Initiative Lead, Phase Lead, Champion Network Rep, Support Lead]

SECTION 1: WHAT HAPPENED
Adoption rate achieved: [%]
Performance metric outcome: [result vs. target]
Champion network performance: [did coverage hold? effectiveness?]
Support ticket volume: [expected vs. actual]
Training effectiveness: [any gaps that surfaced?]

SECTION 2: WHY IT HAPPENED
Root cause analysis for any metric that did not meet target:
  Issue: [description]
  Root cause: [why did this happen?]
  Contributing factors: [what made it worse or better?]

Root cause analysis for any unexpected success:
  Success: [description]
  Why it worked: [specific conditions that enabled it]
  Replicable: [yes/no — if yes, how?]

SECTION 3: WHAT CHANGES FOR NEXT PHASE
Training adjustments: [specific changes]
Champion network adjustments: [specific changes]
Support infrastructure adjustments: [specific changes]
Communication adjustments: [specific changes]
Scope/pace adjustments: [specific changes]

SECTION 4: WHAT STAYS THE SAME
[Specific elements of the current phase approach to preserve]

SECTION 5: DECISIONS MADE
[Named decisions, decision owners, effective dates]