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 Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration for Flywheel.
Growth
Flywheel
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.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.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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 hMultiple workshops over several weeks60-120 min
Participantsdifferent
3-83-102-83-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesDomain Context Map, Boundary Notes, Ownership MapHooked loop, Trigger map, Reward design, Ethics checkFlywheel Map, Friction Points, Growth Levers, Experiment Backlog
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignContextBoundaries
GrowthBehaviorRetention
GrowthRetentionConversion
Add more methods