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 |  Architecture Software Architecture Canvas |  Product Strategy Product Vision Board |
|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | When a product needs a shared direction, it connects target audience, benefit, and business picture in a clear vision. It makes the envisioned future legible for the team. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-120 min | 1-2 h | 1-2 h |
Participantsdifferent | 3-8 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Product Vision Board, Vision Statement, Assumptions and Validation Questions |
Tagsno overlap | GrowthRetentionConversion | CanvasArchitectureAlignmentWorkshop | VisionCanvasStrategyAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
