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
Empathy Mapping
UX Research
Empathy 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 for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
LowHighHighLow
Timedifferent
30–60 min1-4 h1-4 Wochen60-90 min
Participantsdifferent
4-83-81-64-12
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
Empathy Map, Assumptions List, Research GapsChallenge Findings, Risk Register, Mitigation PlanExperiment results, Decision log, Learning summaryAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
SynthesisQualitativeWorkshop
RiskDecisionSensemaking
ExperimentsGrowthAnalyticsValidation
RiskArchitectureWorkshopValidation
Add more methods