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 illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.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 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 Tage30 min Setup, dann laufend60–90 min
Participantsdifferent
Based on research question1-3 maintaining, briefing for everyone2-8
Formatdifferent
AsyncAsyncWorkshop + async
Outputdifferent
Findability Metrics, Path Analysis, Revised IARAID Log, Status Report SourceStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
Information architectureNavigationFindability
RiskTrackingStakeholdersGovernance
StakeholdersAlignmentFacilitationChange
Add more methods

Often compared together

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

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