View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Working Backwards |  Growth Flywheel |  Architecture Architecture Communication Canvas |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 60-120 min | 60-120 min | 1-2 h |
Participantsdifferent | 2-6 | 3-8 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | VisionNarrativeAlignment | GrowthRetentionConversion | ArchitectureCommunicationStakeholdersCanvas | CanvasArchitectureAlignmentWorkshop |