View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Concept Mapping | ![]() Knowledge Modeling Knowledge Mapping | ![]() Growth Flywheel | ![]() Growth North Star Metric |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | 1-3 h | 60-120 min | 1-2 h |
Participantsdifferent | 1-8 | 3-12 | 3-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk | GrowthRetentionConversion | GrowthMetricsAlignmentRetention |



