View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Dot Voting | ![]() Architecture arc42 | ![]() Architecture C4 Model | ![]() Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | 5-15 min | 1-2 Tage | 1-4 h | 1-3 h |
Participantsdifferent | 3-20 | 1-4 | 1-5 | 5-30 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ranked list, Consensus signal, Shortlist | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | FacilitationVotingConsensusPrioritization | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization | FacilitationConsensusWorkshopAlignment |



