methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session60-180 minWorkshopFailure Scenarios

Session: Failure Scenario Analysis

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 3-8. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Failure Scenarios. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Fix scope

    10-20 min

    Define occasion, goal, and boundaries of analysis. Put off all off-topic themes in a parking lot. Hint: A narrow scope yields better results than a full but diffuse sweep.

    FacilitatorFailure Scenarios
  2. 2

    Gather raw material

    20-40 min

    Collect and make visible facts, events, options, constraints, and assumptions. Hint: Keep facts and interpretations separate. Mark uncertain points instead of smoothing them.

    FacilitatorRisk Notes
  3. 3

    Build structure

    30-60 min

    Fill Failure Scenarios step by step, clarify relationships between elements, and reveal contradictions. Hint: Do not evaluate too early. Stabilize structure first, then draw conclusions.

    FacilitatorControl Gaps
  4. 4

    Check and condense

    20-40 min

    Mark gaps, weak assumptions, counterexamples, and critical paths. Check the output for readability. Hint: If nobody can explain the logic in two minutes, the artifact is not ready.

    FacilitatorTest and Response Actions
  5. 5

    Define next steps

    15-20 min

    Document decision, experiment, test, measure, or follow-up with owner and date. Hint: A good artifact without a next action stays knowledge work without impact.

    OwnerFailure Scenarios
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerFailure Scenarios
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Failure Scenario Analysis

Goal

Artifact: Failure Scenarios

Working Question

How could the system plausibly fail, what would that impact be, and which controls are missing?

Context

Scope, occasion, known facts, relevant constraints, prior options or events, and desired workshop outcome.

Setup

  • Format: Method session
  • Duration: 60-180 min
  • Mode: Workshop
  • Participants: Facilitator; domain experts from affected area; one owner for outcome and follow-up; named decider when decisions are made.
  • Owner: Facilitator
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Failure Scenarios. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Workboard or document for Failure Scenarios; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Preparation

Prepare an empty Failure Scenarios template. Make scope and working question visible at the top. Mark each assumption as an assumption, not a fact.

Agenda

  1. Fix scope (10-20 min) Owner: Facilitator Action: Define occasion, goal, and boundaries of analysis. Put off all off-topic themes in a parking lot. Hint: A narrow scope yields better results than a full but diffuse sweep. Output: Failure Scenarios

  2. Gather raw material (20-40 min) Owner: Facilitator Action: Collect and make visible facts, events, options, constraints, and assumptions. Hint: Keep facts and interpretations separate. Mark uncertain points instead of smoothing them. Output: Risk Notes

  3. Build structure (30-60 min) Owner: Facilitator Action: Fill Failure Scenarios step by step, clarify relationships between elements, and reveal contradictions. Hint: Do not evaluate too early. Stabilize structure first, then draw conclusions. Output: Control Gaps

  4. Check and condense (20-40 min) Owner: Facilitator Action: Mark gaps, weak assumptions, counterexamples, and critical paths. Check the output for readability. Hint: If nobody can explain the logic in two minutes, the artifact is not ready. Output: Test and Response Actions

  5. Define next steps (15-20 min) Owner: Owner Action: Document decision, experiment, test, measure, or follow-up with owner and date. Hint: A good artifact without a next action stays knowledge work without impact. Output: Failure Scenarios

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Failure Scenarios

Closeout

  • Update result artifact: Failure Scenarios
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Failure Scenarios: Failure Scenario Analysis

Working Question

How could the system plausibly fail, what would that impact be, and which controls are missing?

Context

Scope, occasion, known facts, relevant constraints, prior options or events, and desired workshop outcome.

Participants

  • Owner: Facilitator
  • Participants: Facilitator; domain experts from affected area; one owner for outcome and follow-up; named decider when decisions are made.

Input

Workboard or document for Failure Scenarios; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Template

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.

Completion Check

  • Failure Scenarios is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Failure Scenario Analysis Working Template

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

failure-scenario-analysis-working-template.md

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.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Failure Scenarios.
  • Save artifact with date, scope, and participants. On new evidence, create new version or change note to keep decision logic traceable.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet