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 DIBB with its method-specific working model.
Product Strategy
DIBB
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
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.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
20-60 min1-2 hAs needed45-90 min
Participantsdifferent
1-42-84-152-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDIBB document, Belief list, Bet list, Learning reportIncident Log, Action Tracker, Stakeholder UpdatesAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
OperationsReliabilityDocumentation
StrategyDecisionAssumptionsHypothesis
IncidentOperationsReliability
AssumptionsRiskDecisionDiscovery
Add more methods