Risks are written as uncertain events with consequences.
ROAM Board
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
Prerequisite
What needs to be finished first
Owners and risk acceptors are available or named.
Preparation
What needs to be ready before start
Four-column board, prioritised risk list, planning objectives, owner directory, and review calendar.
Facilitator or RTE, risk owners, affected teams, subject experts, and authorised risk acceptor.
Prepare risks with consequences, current assessment, and existing treatments.
20–40 minutes initially; 10–20 minutes per review.
Display column criteria and required fields for owners, dates, treatments, and acceptance.
Core question
The one question this method answers
How will each relevant risk be treated, and what must happen before the next review?
Flow
Phases with goal, actions, output and pitfall
ROAM is a collaborative risk-treatment practice for planning and review. Owned is an interim state with accountability, Accepted requires an authorised decision, Mitigated requires a concrete plan, and Resolved requires evidence that the concern has ended.
ROAM Board
Fictional worked example
Four treatment states with status-specific required information.
Resolved
Test environment capacity
Additional capacity confirmed; risk ended on 14 June.
Owned
Certificate approval delayed
Clarification blocked
Owner Security; escalation by 21 June; treatment still undecided.
Accepted
One-day shipping delay
Business owner accepted on 12 June; reconsider at >1 day or >5% of orders.
Mitigated
Identity provider outage
Fallback tested; residual switch-over risk up to five minutes; review 30 September.
- Resolved
- Evidence shows the concern has ended; record rationale and date.
- Owned
- An owner investigates; next action and date are required.
- Accepted
- An authorised person accepts residual risk with rationale and trigger.
- Mitigated
- A treatment reduces likelihood or impact; keep residual risk visible.
- 1
Prepare
Qualify risks for ROAM

Goal
Provide a bounded, understandable list of relevant risks with consequence and context.
Inputs for this step
- Current risks from planning or register
- Objectives and affected dependencies
- Existing assessment or urgency
Actions
- Separate duplicates and issues that have already occurred.
- Write each risk as a possible event with consequence.
- Include only risks within the joint decision scope.
Output
Qualified risk list
Risk scenario · consequence · context · urgency
Quality check
Is every item a risk rather than a task or issue? Is the affected objective clear?
Pitfall
The board fills with vague worries and operational tasks that cannot support a ROAM decision. Rewrite items as risk scenarios or move them to issue and action lists.
Timing: 5–10 minutes
- 2
Decide
ROAM every risk

Goal
Choose the appropriate treatment and record the decision rationale.
Inputs for this step
- Qualified risks
- Response options and decision authority
- People with risk and delivery knowledge
Actions
- Check whether evidence shows the risk no longer exists: Resolved.
- If more work is needed, distinguish Owned, Accepted, and Mitigated.
- Record the decision rationale and remaining uncertainty on the card.
Output
ROAM assignment
Category · rationale · residual uncertainty
Quality check
Can the category be traced to a criterion? Is Owned kept distinct from Mitigated and Resolved?
Pitfall
Risks are placed in the most convenient column without rationale or residual uncertainty. Apply the exit criterion for each column and treat doubtful cards as Owned with an investigation action.
Timing: 10–20 minutes
- 3
Commit
Add ownership and review dates

Goal
Make open risks actionable with owners, actions, acceptance authority, and the next review.
Inputs for this step
- ROAM board
- Responsibilities
- Review cadence and escalation path
Actions
- Owned receives an owner, next action, and due or review date.
- Mitigated receives a treatment, expected reduction, and evidence of effect.
- Accepted receives rationale, risk acceptor, and reconsideration trigger.
Output
Actionable board
Owner · action · date · evidence · acceptance
Quality check
Can every open card be actively tracked to the next review? Is acceptance documented by an authorised person?
Pitfall
Owned cards contain a name but no next action; Accepted becomes a parking place for uncomfortable risks. Complete status-specific fields and escalate unauthorised acceptance.
Timing: 10–15 minutes
- 4
Review
Update status from evidence

Goal
Review risks regularly, justify transitions, and close completed cards traceably.
Inputs for this step
- Current ROAM board
- New evidence and treatment results
- Changed objectives or dependencies
Actions
- Review Owned and Mitigated cards first.
- Record every transition with date, rationale, and evidence.
- Add new risks and archive rather than delete Resolved cards.
Output
Versioned risk picture
Status history · new evidence · escalations
Quality check
Does every status change have a clear trigger? Are overdue Owned risks visibly escalated?
Pitfall
The board remains unchanged after planning and months later only reflects the original discussion. Establish a review cadence with an owner and escalate overdue cards.
Timing: 10–20 minutes per review
Artifact
What comes out at the end
Sketch: what the artifact looks like
Versioned ROAM board with rationale, owners, treatments, dates, and review triggers.
Log transitions with date, author, rationale, and evidence; archive Resolved cards.
- Physical or digital four-column board
- Risk register
- Action and decision log
roam-board-working-template.md
Set up the board once and establish a recurring review practice.
ROAM Board: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Establish ROAM practice Time: Ongoing practice with 10–20 minutes per review
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Four-column board, prioritised risk list, planning objectives, owner directory, and review calendar.
- Roles: Facilitator or RTE, risk owners, affected teams, subject experts, and authorised risk acceptor.
- Advance information: Prepare risks with consequences, current assessment, and existing treatments.
- Overall time needed: 20–40 minutes initially; 10–20 minutes per review.
- Setup: Display column criteria and required fields for owners, dates, treatments, and acceptance.
Prepare for the work steps
Prepare: Qualify risks for ROAM
- Current risks from planning or register
- Objectives and affected dependencies
- Existing assessment or urgency
Decide: ROAM every risk
- Qualified risks
- Response options and decision authority
- People with risk and delivery knowledge
Commit: Add ownership and review dates
- ROAM board
- Responsibilities
- Review cadence and escalation path
Review: Update status from evidence
- Current ROAM board
- New evidence and treatment results
- Changed objectives or dependencies
ROAM Board
Resolved
...
Owned
...
Accepted
...
Mitigated
...
Working policies
Resolved ...
Owned ...
Accepted ...
Mitigated ...
U.S. Department of Commerce Agile Framework
Prepare: Qualify risks for ROAM
Expected artifact: Qualified risk list
Risk scenario · consequence · context · urgency
Entry:
...
- Is every item a risk rather than a task or issue?
- Is the affected objective clear?
Decide: ROAM every risk
Expected artifact: ROAM assignment
Category · rationale · residual uncertainty
Entry:
...
- Can the category be traced to a criterion?
- Is Owned kept distinct from Mitigated and Resolved?
Commit: Add ownership and review dates
Expected artifact: Actionable board
Owner · action · date · evidence · acceptance
Entry:
...
- Can every open card be actively tracked to the next review?
- Is acceptance documented by an authorised person?
Review: Update status from evidence
Expected artifact: Versioned risk picture
Status history · new evidence · escalations
Entry:
...
- Does every status change have a clear trigger?
- Are overdue Owned risks visibly escalated?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/roam-board/run-sheet
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
roam-board-beispiel.md
Concrete filled scenario, fictional example
Fictional example: an external identity provider might fail during a PI objective. Status Mitigated because an automatic fallback was implemented and proven in a load test on 18 June. Owner: Operations. Residual risk: switch-over may take up to five minutes. Review after the first production failover or by 30 September.
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Qualify risks for ROAMThe board fills with vague worries and operational tasks that cannot support a ROAM decision.View in phase
- ROAM every riskRisks are placed in the most convenient column without rationale or residual uncertainty.View in phase
- Add ownership and review datesOwned cards contain a name but no next action; Accepted becomes a parking place for uncomfortable risks.View in phase
- Update status from evidenceThe board remains unchanged after planning and months later only reflects the original discussion.View in phase
Qualify risks for ROAM
The board fills with vague worries and operational tasks that cannot support a ROAM decision.
Rewrite items as risk scenarios or move them to issue and action lists.
ROAM every risk
Risks are placed in the most convenient column without rationale or residual uncertainty.
Apply the exit criterion for each column and treat doubtful cards as Owned with an investigation action.
Add ownership and review dates
Owned cards contain a name but no next action; Accepted becomes a parking place for uncomfortable risks.
Complete status-specific fields and escalate unauthorised acceptance.
Update status from evidence
The board remains unchanged after planning and months later only reflects the original discussion.
Establish a review cadence with an owner and escalate overdue cards.
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

