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 illustration of Lean UX Canvas with its method-specific working model.
UX Design
Lean UX 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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
The Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-3 h15-45 min1-3 h1-2 h
Participantsdifferent
3-81-35-303-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Completed Lean UX Canvas, Hypothesis list, First experimentADR File, Decision Log, RationaleConsensus Clusters, Theme Titles, Priority AreasArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
CanvasHypothesisOutcomesDiscovery
ArchitectureRationaleDocumentationGovernance
FacilitationConsensusWorkshopAlignment
CanvasArchitectureAlignmentWorkshop
Add more methods