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 ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |  Product Discovery Smoke Test |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-120 min | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min | 1-5 Tage |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | 2-8 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | GrowthRetentionConversion | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandGrowth |