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
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
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
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.A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.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
LowMediumHighLow
Timedifferent
1-2 Tage2-4 h1-4 Wochen1-5 Tage
Participantsdifferent
1-45-151-6Nutzertraffic
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewQuality Scenarios, Priority List, Architecture ConcernsExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ArchitectureDocumentationCommunication
RequirementsArchitectureWorkshop
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods