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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
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.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.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.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.
Complexitydifferent
MediumMediumHighLow
Timedifferent
2-6 h1-3 h1-4 Wochen45-90 min
Participantsdifferent
2-82-81-62-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsContext Map, Integration Patterns, Boundary NotesExperiment results, Decision log, Learning summaryAnsoff Matrix, Growth Options, Risk Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesStrategy
ExperimentsGrowthAnalyticsValidation
GrowthStrategyMarketPortfolio
Add more methods