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 paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h2-6 h20-35 min1-5 Tage
Participantsdifferent
2-82-81-5Nutzertraffic
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEvent Model, UI Flow, Commands, Read ModelsTest Card with a pre-set thresholdClick Data, Interest Signal, Learning Decision
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
EventsBlueprintDomain-Driven DesignBehavior
ExperimentsValidationDiscoveryHypothesis
ValidationExperimentsDemandDiscovery
Add more methods