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 |  Architecture Software Architecture Canvas |  Architecture Risk Storming |
|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 3-12 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Architecture Canvas, Goals, Constraints, Quality Attributes | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | CanvasArchitectureAlignmentWorkshop | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
