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 a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
45-90 minMultiple workshops over several weeks1-3 h2-6 h
Participantssame
2-82-82-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Ansoff Matrix, Growth Options, Risk NotesHooked loop, Trigger map, Reward design, Ethics checkContext Map, Integration Patterns, Boundary NotesEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
GrowthStrategyMarketPortfolio
GrowthBehaviorRetention
Domain-Driven DesignBoundariesStrategy
EventsBlueprintDomain-Driven DesignBehavior
Add more methods