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 | ![]() Growth Flywheel | ![]() Growth Funnel Analysis |
|---|---|---|---|
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. | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 60-120 min | 1-3 h |
Participantsdifferent | 2-8 | 3-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Funnel report, Drop-off analysis, Optimization hypotheses |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | GrowthRetentionConversion | AnalyticsConversionGrowth |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






