methodatlas
Session Builder

Plan my session

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

Method session20-40 min initial, then 10-15 min per reviewWorkshop or asyncROAM Board

Session: ROAM Board

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

  1. 1

    Phase 1: Calibrate definitions

    10 min

    Review definition per column together. Clarify that every risk is in exactly one column. Discuss edge cases (for example watched AND mitigated -> Mitigated wins). Hint: If definitions remain unclear, risks land in wrong column. Mitigated must mean active, not "we are thinking about it".

    FacilitatorROAM Board
  2. 2

    Phase 2: Initially assign risks

    15-20 min

    Choose column per risk, name owner. For Owned and Mitigated, next action and deadline. For Accepted, rationale in comment. Hint: Risk without owner is risk without consequence. Anyone not naming owner has not defined responsibility. Workshop does not end with risks without owner.

    FacilitatorOwner-Liste
  3. 3

    Phase 3: Set review cadence

    5 min

    Choose cadence frequency (weekly for active programs, every 2 weeks for stable). Create recurring calendar series. Define maintenance responsibility. Hint: Cadence decays quickly if not in calendar. First review within 1 week after initial creation. Without cadence, board dies in 4 weeks.

    FacilitatorROAM Board
  4. 4

    Phase 4: Run reviews

    10-15 min per review

    Per risk: status changed? Owner active? Action done? Document status move between columns. Escalate on repeatedly unmoved risks. Hint: Mitigated -> Resolved is target path. Owned unchanged after 4 weeks: check real owner or Accepted candidate?

    OwnerOwner-Liste
  5. 5

    Publish artifact

    10 min

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

    OwnerROAM Board
Usable artifact

Session Brief

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

session-brief.md

Session Brief: ROAM Board

Goal

Artifact: ROAM Board

Working Question

Which risks are in which follow-up state, who is responsible, and which need movement between columns now?

Context

Risk list from previous step; written definition per category; review cadence proposal (for example weekly or per sprint); escalation rules for unmoved risks.

Setup

  • Format: Method session
  • Duration: 20-40 min initial, then 10-15 min per review
  • Mode: Workshop or async
  • Participants: One risk owner (RTE, program lead, Tech Lead) for maintenance; all risk owners; reviewers per cadence (team representatives, stakeholders); optionally one coach for ROAM introduction.
  • Owner: One risk owner (RTE, program lead, Tech Lead) for maintenance
  • 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 ROAM Board. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Board with 4 columns (Resolved, Owned, Accepted, Mitigated); risk list as cards or notes; definitions per column visible; tool for async maintenance (Notion, Jira, Miro); review date in calendar.

Preparation

Board with four columns. Definitions per column as banner: Resolved=done; Owned=watched with owner; Accepted=consciously accepted without action; Mitigated=active countermeasure running. Review date as recurring series.

Agenda

  1. Phase 1: Calibrate definitions (10 min) Owner: Facilitator Action: Review definition per column together. Clarify that every risk is in exactly one column. Discuss edge cases (for example watched AND mitigated -> Mitigated wins). Hint: If definitions remain unclear, risks land in wrong column. Mitigated must mean active, not "we are thinking about it". Output: ROAM Board

  2. Phase 2: Initially assign risks (15-20 min) Owner: Facilitator Action: Choose column per risk, name owner. For Owned and Mitigated, next action and deadline. For Accepted, rationale in comment. Hint: Risk without owner is risk without consequence. Anyone not naming owner has not defined responsibility. Workshop does not end with risks without owner. Output: Owner-Liste

  3. Phase 3: Set review cadence (5 min) Owner: Facilitator Action: Choose cadence frequency (weekly for active programs, every 2 weeks for stable). Create recurring calendar series. Define maintenance responsibility. Hint: Cadence decays quickly if not in calendar. First review within 1 week after initial creation. Without cadence, board dies in 4 weeks. Output: ROAM Board

  4. Phase 4: Run reviews (10-15 min per review) Owner: Owner Action: Per risk: status changed? Owner active? Action done? Document status move between columns. Escalate on repeatedly unmoved risks. Hint: Mitigated -> Resolved is target path. Owned unchanged after 4 weeks: check real owner or Accepted candidate? Output: Owner-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: ROAM Board

Closeout

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

ROAM Board: ROAM Board

Working Question

Which risks are in which follow-up state, who is responsible, and which need movement between columns now?

Context

Risk list from previous step; written definition per category; review cadence proposal (for example weekly or per sprint); escalation rules for unmoved risks.

Participants

  • Owner: One risk owner (RTE, program lead, Tech Lead) for maintenance
  • Participants: One risk owner (RTE, program lead, Tech Lead) for maintenance; all risk owners; reviewers per cadence (team representatives, stakeholders); optionally one coach for ROAM introduction.

Input

Board with 4 columns (Resolved, Owned, Accepted, Mitigated); risk list as cards or notes; definitions per column visible; tool for async maintenance (Notion, Jira, Miro); review date in calendar.

Template

ROAM Board 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

  • ROAM Board:
  • Owner List:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • ROAM Board 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

ROAM Board Working Template

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

roam-board-working-template.md

Compact working template for ROAM Board with context, input, output artifacts, and next step.

ROAM Board 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

  • ROAM Board:
  • Owner List:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits ROAM Board.
  • Board is living. Snapshot per review (date) as archive. Status changes with date and rationale. Move Resolved risks to archive after 3 months, do not delete.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet