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 Software Architecture Canvas | ![]() Architecture Architecture Inception 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 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 60-120 min | 1-2 h | 1-2 h |
Participantsdifferent | 2-6 | 3-8 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | VisionNarrativeAlignment | GrowthRetentionConversion | CanvasArchitectureAlignmentWorkshop | AlignmentArchitectureCanvas |



