methodatlas
Session Builder

Plan my session

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

Method session30-60 minWorkshop or asyncRisikomatrix

Session: Risk Matrix

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-10. 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 Risikomatrix. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Calibrate scale

    10 min

    Review scale definitions together. At least one example per level (for example I=5: total outage >24h, I=1: tooltip wrong). Capture consensus. Hint: Without calibrated scale, evaluation becomes gut feeling. If examples are not quickly tangible, sharpen scale definition before workshop.

    FacilitatorRisikomatrix
  2. 2

    Phase 2: Place risks individually

    15-30 min

    Read each risk card, team estimates P and I separately (for example thumb signal or voting tool). On divergence discuss briefly, then consensus value or mean. Hint: Maximum 2 min discussion per risk. If no convergence, take higher value (precautionary principle). Endless debates signal unclear scale.

    FacilitatorTop-Risiko-Liste
  3. 3

    Phase 3: Zone analysis

    10 min

    Check risk distribution across zones. Extract red zone as top list. Yellow zone as watch list. Green zone documented as Accepted. Hint: More than 10 red risks signals undervalued system risk or scale too strict. Recalibrate scale or reduce risk before continuing initiative.

    FacilitatorRisikomatrix
  4. 4

    Phase 4: Actions per high risk

    15-20 min

    Define action per red risk: avoid, reduce (mitigate), transfer or accept. Set owner and deadline. Handover to ROAM Board or RAID Log. Hint: Without action, matrix is picture book. At least every red zone has owner and next action. Accepting is valid action, but must be documented consciously.

    OwnerTop-Risiko-Liste
  5. 5

    Publish artifact

    10 min

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

    OwnerRisikomatrix
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Risk Matrix

Goal

Artifact: Risikomatrix

Working Question

Where does each risk sit on probability-impact scale, and which risks need immediate action, which observation, which accepted exposure?

Context

Risk list distributed beforehand; written scale definition (for example probability 1=rare, 5=almost certain; impact 1=cosmetic, 5=existential); zone definition (green=accept, yellow=watch, red=action).

Setup

  • Format: Method session
  • Duration: 30-60 min
  • Mode: Workshop or async
  • Participants: One facilitator who keeps scale present and moderates consensus; 3-10 participants with risk context (engineering, operations, compliance, product, sponsor); one scribe for evaluation and actions.
  • Owner: One facilitator who keeps scale present and moderates consensus
  • 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 Risikomatrix. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with matrix (3x3 or 5x5, probability horizontal, impact vertical); colored zones (green/yellow/red); risk list as cards; scale definitions visible; timer.

Preparation

Draw matrix grid on board (5x5 common). Label scale values. Mark zones with colors (green=P*I 1-6, yellow=7-14, red=15-25). Scale definitions visible as banner.

Agenda

  1. Phase 1: Calibrate scale (10 min) Owner: Facilitator Action: Review scale definitions together. At least one example per level (for example I=5: total outage >24h, I=1: tooltip wrong). Capture consensus. Hint: Without calibrated scale, evaluation becomes gut feeling. If examples are not quickly tangible, sharpen scale definition before workshop. Output: Risikomatrix

  2. Phase 2: Place risks individually (15-30 min) Owner: Facilitator Action: Read each risk card, team estimates P and I separately (for example thumb signal or voting tool). On divergence discuss briefly, then consensus value or mean. Hint: Maximum 2 min discussion per risk. If no convergence, take higher value (precautionary principle). Endless debates signal unclear scale. Output: Top-Risiko-Liste

  3. Phase 3: Zone analysis (10 min) Owner: Facilitator Action: Check risk distribution across zones. Extract red zone as top list. Yellow zone as watch list. Green zone documented as Accepted. Hint: More than 10 red risks signals undervalued system risk or scale too strict. Recalibrate scale or reduce risk before continuing initiative. Output: Risikomatrix

  4. Phase 4: Actions per high risk (15-20 min) Owner: Owner Action: Define action per red risk: avoid, reduce (mitigate), transfer or accept. Set owner and deadline. Handover to ROAM Board or RAID Log. Hint: Without action, matrix is picture book. At least every red zone has owner and next action. Accepting is valid action, but must be documented consciously. Output: Top-Risiko-Liste

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

Closeout

  • Update result artifact: Risikomatrix
  • 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

Risikomatrix: Risk Matrix

Working Question

Where does each risk sit on probability-impact scale, and which risks need immediate action, which observation, which accepted exposure?

Context

Risk list distributed beforehand; written scale definition (for example probability 1=rare, 5=almost certain; impact 1=cosmetic, 5=existential); zone definition (green=accept, yellow=watch, red=action).

Participants

  • Owner: One facilitator who keeps scale present and moderates consensus
  • Participants: One facilitator who keeps scale present and moderates consensus; 3-10 participants with risk context (engineering, operations, compliance, product, sponsor); one scribe for evaluation and actions.

Input

Whiteboard or Miro board with matrix (3x3 or 5x5, probability horizontal, impact vertical); colored zones (green/yellow/red); risk list as cards; scale definitions visible; timer.

Template

Risk Matrix Working Matrix

ElementDescriptionRatingEvidenceOwnerNext step
1
2
3

Output artifacts

  • Risk Matrix:
  • Top Risk List:

Decision or recommendation

What consequence follows from the matrix?

Completion Check

  • Risikomatrix 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

Risk Matrix Working Template

View templateCompact working template for Risk Matrix with context, input, output artifacts, and next step.
spreadsheet

risk-matrix-working-template.md

Compact working template for Risk Matrix with context, input, output artifacts, and next step.

Risk Matrix Working Matrix

ElementDescriptionRatingEvidenceOwnerNext step
1
2
3

Output artifacts

  • Risk Matrix:
  • Top Risk List:

Decision or recommendation

What consequence follows from the matrix?

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Risikomatrix.
  • Snapshot per evaluation round with date. Document evaluation changes with rationale. Mark resolved risks as Resolved, do not remove. Quarterly new matrix as update, old archived.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet