View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  DevOps Blameless Postmortem |  Decision Making Assumption Surfacing |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 30-90 min | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Postmortem Doc, Action Items, Timeline | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Site Reliability EngineeringIncidentLearningReliability | AssumptionsRiskDecisionDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
