View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Facilitation Dot Voting |  Architecture Software Architecture Canvas |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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. | 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 | Low | Low | Medium |
Timedifferent | 60-90 min | 5-15 min | 1-2 h | 1-3 h |
Participantsdifferent | 4-12 | 3-20 | 3-10 | 5-30 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Ranked list, Consensus signal, Shortlist | Architecture Canvas, Goals, Constraints, Quality Attributes | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | RiskArchitectureWorkshopValidation | FacilitationVotingConsensusPrioritization | CanvasArchitectureAlignmentWorkshop | FacilitationConsensusWorkshopAlignment |