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 Value Chain Analysis |
|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 30-90 min | 20–45 min | Half day |
Participantsdifferent | 3-12 | Small cross-functional group | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Risk list, Mitigation plan, Assumption log | Value Chain Map, Lever List |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | RiskDecisionFailurePlanning | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






