View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Consensus WorkshopArchitecture Decision RecordPower Interest GridSoftware Architecture Canvas
| Criterion |  Facilitation Consensus Workshop |  Architecture Architecture Decision Record |  Facilitation Power Interest Grid |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 15-45 min | 30-60 min | 1-2 h |
Participantsdifferent | 5-30 | 1-3 | 2-8 | 3-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Consensus Clusters, Theme Titles, Priority Areas | ADR File, Decision Log, Rationale | Power Interest Grid, Strategy per Stakeholder | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | FacilitationConsensusWorkshopAlignment | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentPlanning | CanvasArchitectureAlignmentWorkshop |