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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.GIST Planning helps clarify target groups, value, goals, and priorities. It links customer value, product logic, and decision priorities, and captures the result as goals, an idea bank, and a step-project list.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
20-60 minWochen bis Monate je GoalAs needed45-90 min
Participantsdifferent
1-43-104-153-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathGoals, Idea bank, Step-project list, Tasks, Learning reportsIncident Log, Action Tracker, Stakeholder UpdatesImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
OperationsReliabilityDocumentation
RoadmapOutcomesPlanningExperiments
IncidentOperationsReliability
OutcomesStrategyBehaviorPlanning
Add more methods