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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Purposedifferent
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent
MediumLowMedium
Timedifferent
As needed45-90 min45-90 min
Participantsdifferent
4-152-82-5
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesAssumption List, Critical Assumptions, Learning PlanA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
IncidentOperationsReliability
AssumptionsRiskDecisionDiscovery
LeanProblem solvingCoachingOperations
Add more methods

Often compared together

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

Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem