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
Growth Experiment workspace showing the question, observations, and next decision.
Growth
Growth Experiment
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
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 growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment.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.
Complexitydifferent
LowMediumLowHigh
Timedifferent
1-2 Tage1-2 Wochen15-45 min1-4 Wochen
Participantsdifferent
1-41-61-31-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExperiment card, Result summary, Next betADR File, Decision Log, RationaleExperiment results, Decision log, Learning summary
Tagsno overlap
ArchitectureDocumentationCommunication
MarketingGrowthExperimentsLearning
ArchitectureRationaleDocumentationGovernance
ExperimentsGrowthAnalyticsValidation
Add more methods