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
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.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.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
MediumLowLowHigh
Timedifferent
2-4 h15-45 min1-5 Tage1-4 Wochen
Participantsdifferent
4-101-3Nutzertraffic1-6
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogADR File, Decision Log, RationaleInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
JourneyServiceService design
ArchitectureRationaleDocumentationGovernance
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods