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 Making Assumption Surfacing |  DevOps Blameless Postmortem |  Decision Making Force Field Analysis |  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. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 30-90 min | 45-90 min | 1-2 h |
Participantsdifferent | 2-8 | 3-12 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis |