View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Agile Starfish Retrospective |  Domain Modeling Bounded Context Canvas |  Product Strategy Counter Metrics |
|---|---|---|---|---|
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 1-3 h | 30-60 min |
Participantsdifferent | 2-8 | 4-12 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Starfish Board, Practice Changes, Experiments | Context Canvas, Glossary, Integration Notes | Counter Metric List, Guardrail Definitions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | RetrospectiveImprovementExperimentsTeam | Domain-Driven DesignBoundariesModeling | MetricsMeasurementStrategyExperiments |