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/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Purposedifferent
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.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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
Complexitydifferent
HighMediumMediumLow
Timedifferent
1-4 Wochen1-3 h1-3 h30-60 min
Participantsdifferent
1-62-83-82-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryContext Map, Integration Patterns, Boundary NotesContext Canvas, Glossary, Integration NotesCounter Metric List, Guardrail Definitions
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignBoundariesModeling
MetricsMeasurementStrategyExperiments
Add more methods