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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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 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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.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.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
1-3 h1-3 h1-3 h1-4 Wochen
Participantsdifferent
2-83-81-51-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Context Map, Integration Patterns, Boundary NotesContext Canvas, Glossary, Integration NotesFunnel report, Drop-off analysis, Optimization hypothesesExperiment results, Decision log, Learning summary
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignBoundariesModeling
AnalyticsConversionGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods