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
Paper radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.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.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
MediumLowLowMedium
Timedifferent
1-2 h1-2 h15-45 min1-3 h
Participantsdifferent
2-103-101-35-30
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Radar Map, Capability Scores, Action AreasArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
AssessmentPortfolioCapability
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
FacilitationConsensusWorkshopAlignment
Add more methods