View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Growth Flywheel | ![]() Growth North Star Metric | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 60-120 min | 1-2 h | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 3-8 | 3-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | North Star metric, Input metric tree, Measurement cadence | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | GrowthRetentionConversion | GrowthMetricsAlignmentRetention | StakeholdersFacilitationAlignmentGovernance |



