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 Assumption Surfacing |  Architecture Architecture Decision Record |
|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-90 min | 45-90 min | 15-45 min |
Participantsdifferent | 3-12 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Assumption List, Critical Assumptions, Learning Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | AssumptionsRiskDecisionDiscovery | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
