Programs & delivery
The migration numbers do not match
A cutover reaches its decision gate with a reconciliation gap. Practice evidence, fallback criteria and cross-team ownership.
20 minutes suggested · Four incident updates · One shared screen
Start this rehearsal →Watch the quick field guide
24-second visual guide · captions and transcript · no autoplay
Read the guidance transcript
Read the delivery situation. A deadline, failed dependency or disputed acceptance can pull a program in different directions. Establish the facts.
Make the trade-off explicit. Choose a controlled pause, scoped workaround or release decision. Read the fictional consequence with the team.
Coordinate the handoff. Name the decision owner and the affected teams. Record what must be true before the next milestone.
Turn friction into a plan. Debrief the branch you took. Give each improvement an owner and due date, then export the shared record.
Who should be in the room?
Facilitator, Migration lead, Data owner, Business sponsor. These are discussion roles, not account invitations. One person records while the team talks.
What the team will practice
The reconciliation is off
The missing count might reflect filtering or incomplete transfer; the team does not yet know.
Discussion: What evidence and stop/go criteria are needed before cutover?
The fallback window is shrinking
There is a real trade-off between time, certainty and operational complexity.
Discussion: Who decides whether to pause, narrow scope or use the fallback?
Teams disagree about acceptance
Technical transfer and business acceptance are separate checks.
Discussion: How will the teams agree a single acceptance record and decision owner?
A bounded discrepancy is explained
Explaining one difference does not close the entire reconciliation gap.
Discussion: Which remaining exceptions and sign-offs control the final go/no-go?
What you’ll leave with
Your own recorded decisions, uncertainties and improvement actions with owners, dates and status. Print a readable report or export a browser-local session to revisit.
Original fictional content, not a technical response procedure. No real systems are changed. This exercise does not certify security readiness or compliance.
Read the facilitator guide →