View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Systems Mapping | ![]() Growth Hooked Model | ![]() Systems Thinking Evaporating Cloud | ![]() Growth Flywheel |
|---|---|---|---|---|
Purposedifferent | 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. | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Multiple workshops over several weeks | 60-120 min | 60-120 min |
Participantsdifferent | 3-12 | 2-8 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Hooked loop, Trigger map, Reward design, Ethics check | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | Systems thinkingMappingBoundariesChange | GrowthBehaviorRetention | Theory of ConstraintsAssumptionsSystems thinking | GrowthRetentionConversion |



