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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-90 min45-90 minAs needed45-60 min
Participantsdifferent
1-62-84-152-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Decision Tree, Option Map, Assumption ListAssumption List, Critical Assumptions, Learning PlanIncident Log, Action Tracker, Stakeholder UpdatesAssumption map, Test backlog, Risk ranking
Tagsno overlap
DecisionTreeOptions
AssumptionsRiskDecisionDiscovery
IncidentOperationsReliability
AssumptionsRiskExperimentsValidation
Add more methods