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 Force Field Analysis |  DevOps Blameless Postmortem |  Business Strategy Business Model Stress Test |
|---|---|---|---|
Purposedifferent | 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 45-90 min | 30-90 min | Half day |
Participantsdifferent | 3-12 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Postmortem Doc, Action Items, Timeline | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | ChangeDecisionStrategy | Site Reliability EngineeringIncidentLearningReliability | StrategyBusiness modelRiskDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
