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 CanvasArchitecture Decision Record3-Circle Venn DiagramStakeholder Salience Model
| Criterion | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Decision Record | ![]() Facilitation 3-Circle Venn Diagram | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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 three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 h | 15-45 min | 15-45 min | 60-90 min |
Participantsdifferent | 3-10 | 1-3 | 2-8 | 3-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | ADR File, Decision Log, Rationale | Venn Diagram, Overlap Notes, Differentiators | Salience Diagram, Strategy per Class |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | ArchitectureRationaleDocumentationGovernance | ComparisonFacilitationAlignment | StakeholdersFacilitationAlignmentGovernance |



