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 Force Field Analysis |  Facilitation Alignment Mapping |
|---|---|---|---|
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 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-90 min | 45-90 min | 1-2 h |
Participantsdifferent | 3-12 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy | AlignmentStakeholdersStrategyFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
