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 Double Diamond with its method-specific working model.
Innovation
Double Diamond
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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 a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
Wochen bis MonateHalber TagAs needed1-3 h
Participantsdifferent
3-125-204-153-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Problem Statement, Solution Options, Prototypes, Deliverables per PhaseSimulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder UpdatesProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
ProcessDivergenceInnovation
ResilienceOperationsIncident
IncidentOperationsReliability
ProcessOperationsImprovement
Add more methods