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 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
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Purposedifferent
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.
Complexitysame
MediumMediumMedium
Timedifferent
45-90 minAs needed1-2 h Setup, laufend
Participantsdifferent
3-84-151
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsIncident Log, Action Tracker, Stakeholder UpdatesAction Lists, Project List, Review Routine
Tagsno overlap
OutcomesStrategyBehaviorPlanning
IncidentOperationsReliability
ProductivityPlanningTasksExecution
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
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper scorecard with four perspectives, connected objective cards and columns for measures, targets and initiatives.
Business Strategy
Balanced Scorecard
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem