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
Paper illustration of Hypothesis Prioritization Canvas with a method-specific labelled workspace.
Product Discovery
Hypothesis Prioritization Canvas
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Purposedifferent
When many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog.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.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.
Complexitysame
MediumMediumMedium
Timedifferent
60-90 min2-6 h1-5 Tage
Participantsdifferent
3-82-8Nutzertraffic
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Prioritization Canvas, Hypothesis BacklogEvent Model, UI Flow, Commands, Read ModelsClick Data, Interest Signal, Learning Decision
Tagsno overlap
ExperimentsPrioritizationDiscoveryHypothesis
EventsBlueprintDomain-Driven DesignBehavior
ValidationExperimentsDemandDiscovery
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card