Programs & delivery
The release breaks a critical journey
A deployment passes smoke tests but breaks a customer workflow. Rehearse stop/go criteria, rollback ownership and a credible update.
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, Release manager, Engineering lead, Product owner. These are discussion roles, not account invitations. One person records while the team talks.
What the team will practice
The dashboard is green, customers disagree
A green deployment is not the same as a healthy business journey.
Discussion: Who can pause rollout and what evidence defines impact?
The rollback is not obviously safe
The fastest-looking change may have a dependency that needs explicit verification.
Discussion: How will you choose a controlled rollback, fix-forward or pause?
The deadline becomes the argument
The team needs an owner-approved trade-off grounded in actual impact.
Discussion: What decision record and stakeholder update would support a defensible choice?
The corrected path works in a test
The team needs a controlled completion check and learning for the next release.
Discussion: What evidence and approval make reopening rollout reasonable?
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 →