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 Futures Wheel with its method-specific working model.
Systems Thinking
Futures Wheel
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event.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.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.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
60-120 min20-60 min1-3 hAs needed
Participantsdifferent
3-101-43-104-15
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Futures Wheel, Consequence Chains, Strategic SignalsRunbook, Checklist, Escalation PathProcess Map, Handoff List, Improvement BacklogIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
ForesightSystems thinkingSignals
OperationsReliabilityDocumentation
ProcessOperationsImprovement
IncidentOperationsReliability
Add more methods