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 |  Architecture Software Architecture Canvas |  Growth Flywheel |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 1-2 h | 60-120 min | 60-120 min |
Participantsdifferent | 1-5 | 3-10 | 3-8 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Architecture Canvas, Goals, Constraints, Quality Attributes | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AnalyticsConversionGrowth | CanvasArchitectureAlignmentWorkshop | GrowthRetentionConversion | ArchitectureCommunicationStakeholdersCanvas |