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 of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h45-90 min1-3 h1-3 h
Participantssame
2-82-82-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsAnsoff Matrix, Growth Options, Risk NotesGap Matrix, Action Plan, Risk NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
GrowthStrategyMarketPortfolio
StrategyAnalysisPlanning
Domain-Driven DesignBoundariesStrategy
Add more methods