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 | ![]() Domain Modeling Bounded Context Canvas | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Systems Mapping |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 60-120 min | 1-3 h | 2-4 h | 1-3 h |
Participantsdifferent | 3-8 | 3-8 | 3-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Context Canvas, Glossary, Integration Notes | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | System Map, Dependencies, Leverage Points |
Tagsno overlap | GrowthRetentionConversion | Domain-Driven DesignBoundariesModeling | Theory of ConstraintsSystems thinkingChange | Systems thinkingMappingBoundariesChange |



