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
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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
LowLowHighLow
Timedifferent
1-2 h15-45 min1-4 Wochen1-5 Tage
Participantsdifferent
3-101-31-6Nutzertraffic
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods