View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Funnel Analysis |  Systems Thinking Systems Mapping |  Domain Modeling Domain Context Map |  Growth Flywheel |
|---|---|---|---|---|
Purposedifferent | 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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 1-3 h | 60-120 min |
Participantsdifferent | 1-5 | 3-12 | 3-10 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | System Map, Dependencies, Leverage Points | Domain Context Map, Boundary Notes, Ownership Map | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | AnalyticsConversionGrowth | Systems thinkingMappingBoundariesChange | Domain-Driven DesignContextBoundaries | GrowthRetentionConversion |