Scenario 1
The certification window
Reconcile incomplete evidence, choose a release posture under a fixed external deadline, respond when that posture produces a live consequence, and report the accepted exposure after the operational call.
Your Call — the two-minute version
This is an optional library of three representative capability scenarios, built from recurring real patterns—not a record of any employer, customer, title, or internal workflow. Read what each scenario demonstrates in two minutes, or choose a complete walkthrough below.
Scenario 2
The overlooked dependency
Stabilize a live platform when a shared-infrastructure dependency, missed at launch prep, starts failing as load climbs — buying safe headroom, sequencing a fix that is itself disruptive, and keeping the customer honestly informed.
Scenario 3
Not every problem is an incident
Handle a problem that never trips the incident bar but still threatens a customer's certification milestone — reading a masked signal, root-causing an undocumented change, containing it narrowly, and warning every customer exposed to the same latent risk.
Before you start
How every scenario works
Two things stay constant across all three scenarios: the shape of the decisions you make, and where your authority begins and ends.
The shared pattern
Three consequence-led decisions
Each scenario asks you to make exactly three decisions: set the operational posture, respond to its consequence, and choose what leadership needs to hear. Every choice shows Protected and Risk accepted before a non-scoring peer comparison.
The role & its boundary
Own the call without claiming specialist work
You own release judgment, coordination, accepted risk, recovery cadence, and the leadership report. Specialist teams retain ownership of testing, operations, and technical fixes. Leadership is informed after the operational call; the report does not reopen a decision already within the release owner's authority.