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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min20-40 min initial, dann laufend1-2 h30 min Setup, dann laufend
Participantsdifferent
1-63-154-121-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Decision Tree, Option Map, Assumption ListROAM Board, Owner ListAlignment Map, Open Issues, Decision QuestionsRAID Log, Status Report Source
Tagsno overlap
DecisionTreeOptions
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
RiskTrackingStakeholdersGovernance
Add more methods