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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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 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.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 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
LowHighLowLow
Timedifferent
1-2 Tage1-4 Wochen15-45 min1-5 Tage
Participantsdifferent
1-41-61-3Nutzertraffic
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExperiment results, Decision log, Learning summaryADR File, Decision Log, RationaleInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ArchitectureDocumentationCommunication
ExperimentsGrowthAnalyticsValidation
ArchitectureRationaleDocumentationGovernance
ValidationExperimentsDemandGrowth
Add more methods