MS
Maya Operations
If partner data arrives after September 3, we won’t have enough time to test before launch.
Risk Review & Pre-mortem
Imagine the failure. Leave with prevention, triggers, and owners.
Credible failure scenarios become prioritized risks, early-warning triggers, mitigations, and contingency ownership before the project is under pressure.
Just talk. BigWow keeps up. No special commands or constant note-taking. Have the conversation you were already going to have.
From Maya’s failure scenario Scenario · not a forecast
Late partner data Candidate risk Threatens the minimum test window
AL
Ari Launch owner
“Make this a top risk. Sam will define the cutoff and fallback by Friday.”
Priority risk Confirmed by Ari ✓
Risk response ✓
Priority risk Mitigation Enforce September 3 data cutoff Sam · Friday
Contingency Use validated fallback dataset Sam · Triggered at cutoff
From Maya’s failure scenario→Confirmed by Ari
How the template helps
A pre-mortem that turns imagination into operational readiness.
Failure scenarios stay distinct from facts while the team prioritizes preventable risk.
What the team leaves with
A risk register with signals and responses—not just worries.
Priority risks, causes, consequences, triggers, mitigations, contingencies, and owners stay together.
Run a risk pre-mortemPartner launch Risk plan
Top risks confirmedConfirmed outcome Treat late partner data as a priority launch risk
Three priority risks · three early signals · two contingency paths
Mitigation Confirmed
Enforce September 3 data cutoff Sam · Friday
Linked to the late-data scenarioContingency Confirmed
Use validated fallback dataset Sam · Triggered at cutoff
Activation rule attached