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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 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
MediumLowLowMedium
Timedifferent
30-90 min30 min Setup, dann laufend20-40 min initial, dann laufend1-2 h
Participantsdifferent
1-61-3 maintaining, briefing for everyone3-154-12
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListRAID Log, Status Report SourceROAM Board, Owner ListAlignment Map, Open Issues, Decision Questions
Tagsno overlap
DecisionTreeOptions
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods