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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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
LowMediumMediumLow
Timedifferent
45-90 minAs needed30-90 min1-2 h
Participantsdifferent
2-84-153-122-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanIncident Log, Action Tracker, Stakeholder UpdatesPostmortem Doc, Action Items, TimelineDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
AssumptionsRiskDecisionDiscovery
IncidentOperationsReliability
Site Reliability EngineeringIncidentLearningReliability
StrategyDecisionAssumptionsHypothesis
Add more methods