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 HEART Framework with its method-specific working model.
UX Research
HEART Framework
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.Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.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
LowMediumHighMedium
Timedifferent
1-2 h120 min initial, dann laufend1-4 Wochen45-60 min
Participantsdifferent
2-83-61-62-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeHEART-GSM Table, DashboardExperiment results, Decision log, Learning summaryAssumption map, Test backlog, Risk ranking
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
MetricsUX researchMeasurementSatisfaction
ExperimentsGrowthAnalyticsValidation
AssumptionsRiskExperimentsValidation
Add more methods