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 for Fake Door Test
Product Discovery
Fake Door Test
Paper illustration of MVP Test Matrix with a method-specific labelled workspace.
Product Discovery
MVP Test Matrix
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.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1-2 Tage1-4 Wochen1-5 Tage45-75 min
Participantsdifferent
1-41-6Nutzertraffic2-8
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExperiment results, Decision log, Learning summaryClick Data, Interest Signal, Learning DecisionTest Matrix, Test Plan
Tagsno overlap
ArchitectureDocumentationCommunication
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandDiscovery
ExperimentsValidationDiscoveryOptions
Add more methods