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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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
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.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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1-2 h1-4 Wochen1-3 h45-60 min
Participantsdifferent
2-81-61-82-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeExperiment results, Decision log, Learning summaryArgument Map, Evidence Gaps, Decision RationaleAssumption map, Test backlog, Risk ranking
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ExperimentsGrowthAnalyticsValidation
SensemakingDecisionRationale
AssumptionsRiskExperimentsValidation
Add more methods