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 a branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Purposedifferent
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.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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.
Complexitydifferent
MediumLowLow
Timedifferent
1-2 Tage20-40 min initial, dann laufend60–90 min
Participantsdifferent
Based on research question3-152-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Findability Metrics, Path Analysis, Revised IAROAM Board, Owner ListStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
Information architectureNavigationFindability
RiskAgileTrackingAlignment
StakeholdersAlignmentFacilitationChange
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model