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
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
As needed45-90 min20-35 min1-2 h
Participantsdifferent
4-152-81-52-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesAssumption List, Critical Assumptions, Learning PlanTest Card with a pre-set thresholdDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
IncidentOperationsReliability
AssumptionsRiskDecisionDiscovery
ExperimentsValidationDiscoveryHypothesis
StrategyDecisionAssumptionsHypothesis
Add more methods