View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  Growth Hooked Model |  Growth Flywheel |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | Multiple workshops over several weeks | 60-120 min | 1-2 h |
Participantsdifferent | 5-15 | 2-8 | 3-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Hooked loop, Trigger map, Reward design, Ethics check | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RequirementsArchitectureWorkshop | GrowthBehaviorRetention | GrowthRetentionConversion | CanvasArchitectureAlignmentWorkshop |