View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Software Architecture CanvasBlameless PostmortemArchitecture Decision RecordConsensus Workshop
| Criterion |  Architecture Software Architecture Canvas |  DevOps Blameless Postmortem |  Architecture Architecture Decision Record |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-2 h | 30-90 min | 15-45 min | 1-3 h |
Participantsdifferent | 3-10 | 3-12 | 1-3 | 5-30 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Postmortem Doc, Action Items, Timeline | ADR File, Decision Log, Rationale | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | Site Reliability EngineeringIncidentLearningReliability | ArchitectureRationaleDocumentationGovernance | FacilitationConsensusWorkshopAlignment |