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 Request for Comments | ![]() Architecture C4 Model |
|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 5-15 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h |
Participantsdifferent | 3-20 | 3-20 Reviewer | 1-5 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Ranked list, Consensus signal, Shortlist | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | FacilitationVotingConsensusPrioritization | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






