View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  DevOps Blameless Postmortem |  Decision Making Assumption Surfacing |
|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | 60-90 min | 30-90 min | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Postmortem Doc, Action Items, Timeline | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskArchitectureWorkshopValidation | Site Reliability EngineeringIncidentLearningReliability | AssumptionsRiskDecisionDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
