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 Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Flywheel.
Growth
Flywheel
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
MediumMediumMediumHigh
Timedifferent
1-3 h60-120 min45-60 min1-4 Wochen
Participantsdifferent
3-83-82-81-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Context Canvas, Glossary, Integration NotesFlywheel Map, Friction Points, Growth Levers, Experiment BacklogAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
Domain-Driven DesignBoundariesModeling
GrowthRetentionConversion
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods