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 North Star Metric |  Growth Flywheel |  Architecture arc42 |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 60-120 min | 1-2 Tage | 1-4 h |
Participantsdifferent | 3-8 | 3-8 | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | North Star metric, Input metric tree, Measurement cadence | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | GrowthMetricsAlignmentRetention | GrowthRetentionConversion | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |