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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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 method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.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.
Complexitydifferent
MediumMediumHigh
Timedifferent
2-6 h60-120 min1-4 Wochen
Participantsdifferent
2-82-81-6
Formatdifferent
Workshop + asyncWorkshopAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsExperiment results, Decision log, Learning summary
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Theory of ConstraintsAssumptionsSystems thinking
ExperimentsGrowthAnalyticsValidation
Add more methods

Often compared together

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

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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