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 Contextual Inquiry.
UX Research
Contextual Inquiry
Stakeholder Mapping
Facilitation
Stakeholder 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.When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise.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
LowMediumLow
Timedifferent
30 min Setup, dann laufend1-3 Wochen60–90 min
Participantsdifferent
1-3 maintaining, briefing for everyone4-12 Beobachtungen2-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceField Notes, Workflow Insights, Pain PointsStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
RiskTrackingStakeholdersGovernance
UX researchObservationContext
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