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 |  Product Discovery Concierge MVP |  Decision Making Force Field 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. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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. | 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 | Medium | Low | Low |
Timedifferent | 30-90 min | 1-4 Wochen | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-10 Kunden | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Concierge Learnings, Service Blueprint, MVP Risks | Force Field Map, Change Levers, Risk Notes | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | MVPValidationServiceDiscovery | ChangeDecisionStrategy | AssumptionsRiskDecisionDiscovery |