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
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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
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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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
LowLowHighMedium
Timedifferent
1-2 h60-90 min1-4 Wochen45-60 min
Participantsdifferent
2-84-101-62-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeProblem Cluster, Prioritized Challenge, ExperimentExperiment results, Decision log, Learning summaryAssumption map, Test backlog, Risk ranking
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
FacilitationDecisionProblem solvingWorkshop
ExperimentsGrowthAnalyticsValidation
AssumptionsRiskExperimentsValidation
Add more methods