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 of Hooked Model with its method-specific working model.
Growth
Hooked Model
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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.The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.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 a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 hMultiple workshops over several weeks1-4 Wochen1-3 h
Participantsdifferent
3-82-81-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesHooked loop, Trigger map, Reward design, Ethics checkExperiment results, Decision log, Learning summaryDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
Domain-Driven DesignBoundariesModeling
GrowthBehaviorRetention
ExperimentsGrowthAnalyticsValidation
Domain-Driven DesignContextBoundaries
Add more methods