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 RecordConsensus WorkshopDecision Rights MappingSoftware Architecture Canvas
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Facilitation Consensus Workshop | ![]() Decision Making Decision Rights Mapping | ![]() 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. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | 1-3 h | 90-180 min | 1-2 h |
Participantsdifferent | 1-3 | 5-30 | 4-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Consensus Clusters, Theme Titles, Priority Areas | Decision Rights Matrix, Agreement | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | FacilitationConsensusWorkshopAlignment | DecisionGovernanceAlignmentResponsibility | CanvasArchitectureAlignmentWorkshop |



