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 illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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 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
LowHighLowMedium
Timedifferent
30 min Setup, dann laufend2-6 h20-40 min initial, dann laufend1-2 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-83-154-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceFault Tree, Critical Paths, Cause Hypotheses, Control ActionsROAM Board, Owner ListAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskRoot causeSafety
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods