View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Blameless PostmortemRisk MatrixATAM (Architecture Tradeoff Analysis Method)Assumption Surfacing
| Criterion | ![]() DevOps Blameless Postmortem | ![]() Decision Making Risk Matrix | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() 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 a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Low | High | Low |
Timedifferent | 30-90 min | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Risk Matrix, Top Risk List | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | RiskDecisionPrioritizationAssessment | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskDecisionDiscovery |



