View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Decision Making Pre-Mortem |  Business Strategy GAP Analysis |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | 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 early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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 | Medium | Low | Medium | Low |
Timedifferent | 30-90 min | 20–45 min | 1-3 h | 45-90 min |
Participantsdifferent | 3-12 | Small cross-functional group | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Risk list, Mitigation plan, Assumption log | Gap Matrix, Action Plan, Risk Notes | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | RiskDecisionFailurePlanning | StrategyAnalysisPlanning | AssumptionsRiskDecisionDiscovery |