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 | ![]() Agile NoEstimates | ![]() Facilitation Alignment Mapping | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-120 min | laufend | 1-2 h | 60-90 min |
Participantsdifferent | 3-8 | 2-12 | 4-12 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Throughput Data, Flow Forecast, Slicing Rules | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | GrowthRetentionConversion | EstimationForecastingFlow | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |



