View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordQuality Attribute WorkshopConsensus WorkshopSoftware Architecture Canvas
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Architecture Quality Attribute Workshop | ![]() Facilitation Consensus Workshop | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 2-4 h | 1-3 h | 1-2 h |
Participantsdifferent | 1-3 | 5-15 | 5-30 | 3-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Quality Scenarios, Priority List, Architecture Concerns | Consensus Clusters, Theme Titles, Priority Areas | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RequirementsArchitectureWorkshop | FacilitationConsensusWorkshopAlignment | CanvasArchitectureAlignmentWorkshop |



