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 for Diary Study.
UX Research
Diary Study
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitysame
MediumMediumMedium
Timedifferent
1-4 Wochen45-90 minAs needed
Participantsdifferent
5-203-84-15
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineImpact Map, Outcome Hypotheses, Delivery OptionsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
UX researchTrackingBehavior
OutcomesStrategyBehaviorPlanning
IncidentOperationsReliability
Add more methods

Often compared together

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

Paper illustration for ALPEN Method
Operations
ALPEN Method
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis