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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2-4 h1-4 h1-4 Wochen45-60 min
Participantsdifferent
4-103-81-62-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogChallenge Findings, Risk Register, Mitigation PlanExperiment results, Decision log, Learning summaryAssumption map, Test backlog, Risk ranking
Tagsno overlap
JourneyServiceService design
RiskDecisionSensemaking
ExperimentsGrowthAnalyticsValidation
AssumptionsRiskExperimentsValidation
Add more methods