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
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
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
When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.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
HighMediumLow
Timedifferent
1-4 Wochen30-90 min1-2 h
Participantsdifferent
6-30 Experten3-122-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Expert Forecast, Consensus Range, Assumption NotesPostmortem Doc, Action Items, TimelineDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
ForecastingExpertsDecisionStrategy
Site Reliability EngineeringIncidentLearningReliability
StrategyDecisionAssumptionsHypothesis
Add more methods

Often compared together

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

Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command