methodatlas
Playbook

Conduct Risk and Readiness Review

Move from optimism to visible risks, controls, tests, and release decision.

Outcome

A prioritized risk backlog with controls, tests, and go/no-go criteria.

At the end you have

Risk ListRisk MatrixFailure ScenariosROAM Board

Decision point

You can decide whether a release or initiative is ready, which risks are accepted, and which must be mitigated first.

Next step

Own top risks, perform controls or tests, and check go/no-go criteria before the decision.

Ideal for

  • Critical releases
  • Architecture or operations risks
  • Programs with many dependencies

Not good for

  • small routine changes
  • teams without mandate for countermeasures
Preparation

What should be clear before you start

Roles

  • Release or program owner
  • Engineering, operations, and security
  • relevant business or support stakeholders

Inputs

  • Release scope or initiative description
  • known dependencies and risks
  • operational, security, or quality requirements

Setup

  • Define readiness criteria
  • Collect risks in advance
  • Clarify decision point and escalation path
Flow

Method path

0 methods
    Completion criteria
    Templates

    Artifacts for this playbook

    Artifacts stay collapsed until you actually need them.

    MarkdownShow template

    Failure Scenario Analysis Working Template

    Compact working template for Failure Scenario Analysis with context, input, output artifacts, and next step.

    # Failure Scenario Analysis Working Template

## Goal

Analyzes plausible failure scenarios to prepare weak points, controls, and response options.

## Context

When and for what do we use this method?

## Input

Which data, observations, decisions, or materials are available?

## Execution

Short notes along the runsheet.

## Output artifacts
- Failure Scenarios:
- Risk Notes:
- Control Gaps:
- Test and Response Actions:

## Assumptions and open questions

- ...

## Decision / Next step

Owner, date, and success signal.