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 Flywheel |  Systems Thinking Future Reality Tree |  Domain Modeling Domain Context Map |  Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 60-120 min | 2-4 h | 1-3 h | 60-120 min |
Participantsdifferent | 3-8 | 3-8 | 3-10 | 2-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Domain Context Map, Boundary Notes, Ownership Map | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | GrowthRetentionConversion | Theory of ConstraintsSystems thinkingChange | Domain-Driven DesignContextBoundaries | Theory of ConstraintsAssumptionsSystems thinking |