methodatlas
Session Builder

Plan my session

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

Method session60-90 minWorkshopAnnotiertes Diagramm

Session: Risk Storming

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 4-12. 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 Annotiertes Diagramm. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Introduce context and categories

    10 min

    Facilitator presents diagram (5 min), answers clarification questions. Explain risk categories and note colors. Give examples per category. Hint: If understanding questions about diagram remain after 10 min, postpone workshop. Risk identification without architecture understanding is speculation.

    FacilitatorAnnotiertes Diagramm
  2. 2

    Phase 2: Silent sticking phase

    20 min

    Each participant notes risks on sticky notes (one note, one risk, color by category) and sticks them to the matching place in the diagram. No discussion. Hint: Silence protects from anchoring effects. Anyone speaking gets one reminder. On repeated violation, short pause and reset. Silent phase is core protection of method.

    FacilitatorRisikoliste mit Priorisierung
  3. 3

    Phase 3: Cluster and prioritize

    20-30 min

    Together identify clusters and duplicates. Rate probability and impact (1-5) per cluster. Extract top risks from red area (P*I >=15). Hint: Clusters are more important than individual mentions. If 5 participants independently name same risk, consensus is strong. Single mentions can still be valid, but examine more critically.

    FacilitatorMaßnahmen-Backlog
  4. 4

    Phase 4: Owner and action

    15-20 min

    Name owner per top risk, define next action (spike, mitigation, ROAM entry), set deadline. Maximum 5-7 top risks, rest into backlog. Hint: Without owner, workshop fizzles. At least five risks with owner and deadline before end. Risk without action should be explicitly Accepted instead of forgotten.

    OwnerAnnotiertes Diagramm
  5. 5

    Publish artifact

    10 min

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

    OwnerAnnotiertes Diagramm
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Risk Storming

Goal

Artifact: Annotiertes Diagramm

Working Question

Which risks are embedded in this architecture or plan artifact, and which of them need action before the next iteration?

Context

Architecture diagram distributed 1-2 days beforehand with request to read; list of known incidents/problems from last 6 months; Quality Attributes (security, availability, scalability); risk category definition.

Setup

  • Format: Method session
  • Duration: 60-90 min
  • Mode: Workshop
  • Participants: One facilitator who protects silent phase and moderates clusters; 4-12 participants from mixed roles (architecture, engineering, operations, security, product); one scribe for owner assignment and actions.
  • Owner: One facilitator who protects silent phase and moderates clusters
  • 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 Annotiertes Diagramm. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Large-format print or digital board with architecture diagram at least A1 size; red, yellow, blue sticky notes for risk categories (technical, organizational, external); markers; timer; risk scoring grid (probability/impact).

Preparation

Diagram central on wall. Risk categories visible as legend (red=technical, yellow=organizational, blue=external). Announce silence rule. Evaluation grid (P/I 1-5) as banner.

Agenda

  1. Phase 1: Introduce context and categories (10 min) Owner: Facilitator Action: Facilitator presents diagram (5 min), answers clarification questions. Explain risk categories and note colors. Give examples per category. Hint: If understanding questions about diagram remain after 10 min, postpone workshop. Risk identification without architecture understanding is speculation. Output: Annotiertes Diagramm

  2. Phase 2: Silent sticking phase (20 min) Owner: Facilitator Action: Each participant notes risks on sticky notes (one note, one risk, color by category) and sticks them to the matching place in the diagram. No discussion. Hint: Silence protects from anchoring effects. Anyone speaking gets one reminder. On repeated violation, short pause and reset. Silent phase is core protection of method. Output: Risikoliste mit Priorisierung

  3. Phase 3: Cluster and prioritize (20-30 min) Owner: Facilitator Action: Together identify clusters and duplicates. Rate probability and impact (1-5) per cluster. Extract top risks from red area (P*I >=15). Hint: Clusters are more important than individual mentions. If 5 participants independently name same risk, consensus is strong. Single mentions can still be valid, but examine more critically. Output: Maßnahmen-Backlog

  4. Phase 4: Owner and action (15-20 min) Owner: Owner Action: Name owner per top risk, define next action (spike, mitigation, ROAM entry), set deadline. Maximum 5-7 top risks, rest into backlog. Hint: Without owner, workshop fizzles. At least five risks with owner and deadline before end. Risk without action should be explicitly Accepted instead of forgotten. Output: Annotiertes Diagramm

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

Closeout

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

Annotiertes Diagramm: Risk Storming

Working Question

Which risks are embedded in this architecture or plan artifact, and which of them need action before the next iteration?

Context

Architecture diagram distributed 1-2 days beforehand with request to read; list of known incidents/problems from last 6 months; Quality Attributes (security, availability, scalability); risk category definition.

Participants

  • Owner: One facilitator who protects silent phase and moderates clusters
  • Participants: One facilitator who protects silent phase and moderates clusters; 4-12 participants from mixed roles (architecture, engineering, operations, security, product); one scribe for owner assignment and actions.

Input

Large-format print or digital board with architecture diagram at least A1 size; red, yellow, blue sticky notes for risk categories (technical, organizational, external); markers; timer; risk scoring grid (probability/impact).

Template

Risk Storming Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Annotated Diagram:
  • Prioritized Risk List:
  • Action Backlog:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Annotiertes Diagramm 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 Storming Working Template

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

risk-storming-working-template.md

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

Risk Storming Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Annotated Diagram:
  • Prioritized Risk List:
  • Action Backlog:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Annotiertes Diagramm.
  • Snapshot per workshop with date, participant list and risk state. Repeat every 3-6 months as new entry, delta to previous version documented separately. Mark completed risks as Resolved, do not delete.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet