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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
LowHighMediumHigh
Timedifferent
1-2 h1-4 h45-60 min1-4 Wochen
Participantsdifferent
2-83-82-81-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeChallenge Findings, Risk Register, Mitigation PlanAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RiskDecisionSensemaking
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods