methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of a branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowMediumLowMedium
Timedifferent
20-40 min initial, dann laufend1-2 Tage30 min Setup, dann laufend1-2 h
Participantsdifferent
3-15Based on research question1-3 maintaining, briefing for everyone4-12
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop
Outputdifferent
ROAM Board, Owner ListFindability Metrics, Path Analysis, Revised IARAID Log, Status Report SourceAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RiskAgileTrackingAlignment
Information architectureNavigationFindability
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersStrategyFacilitation
Add more methods