methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of shared options, independently placed voting dots, and a highlighted shortlist.
Facilitation
Dot Voting
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Purposedifferent
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.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 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 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
LowLowLowMedium
Timedifferent
1-2 Tage5-15 min15-45 min1-3 h
Participantsdifferent
1-43-201-35-30
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRanked list, Consensus signal, ShortlistADR File, Decision Log, RationaleConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
ArchitectureDocumentationCommunication
FacilitationVotingConsensusPrioritization
ArchitectureRationaleDocumentationGovernance
FacilitationConsensusWorkshopAlignment
Add more methods