View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy Value Chain Analysis | ![]() DevOps Blameless Postmortem | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Half day | 30-90 min | 45-90 min |
Participantsdifferent | 3-8 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Value Chain Map, Lever List | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | StrategyBusiness modelDiagnosisAnalysis | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






