When to use it
Use the Flywheel when you have a product or business running but growth has stalled or feels random. It's for when you can describe what you do but not why it compounds — or when your team can't agree on what actually drives growth.
It's particularly effective after you've completed a Lean Canvas and want to understand the growth engine underneath it, or when you need to show a board or investors how your initiative will compound, not just launch.
How it works in The Studio
Here's how a session works with WAiDE:
Sample output
Here's what a flywheel diagram looks like in practice:
| 1→2 | STRONG |
| 2→3 | UNPROVEN |
| 3→4 | DEVELOPING |
| 4→1 | STRONG |
What you get
A tight flywheel diagram with 3–5 components, each connection annotated with its mechanism and strength (Strong / Developing / Unproven). The bottleneck is identified along with a concrete 90-day acceleration plan and a 48-hour first step.
Your downloadable report includes the full flywheel map, WAiDE's coaching observations on where the loop is weakest, a recommended next step, and relevant Wade articles and programs.
Foundation
Developed by Jim Collins in "Good to Great" (2001). Made famous by Jeff Bezos at Amazon with the most well-known business flywheel. Popularised as a replacement for the sales funnel by Brian Halligan and Dharmesh Shah at HubSpot.
Why it works
Jim Collins introduced the flywheel concept to describe a pattern he observed in companies that made the leap from good to great: they didn't grow through a single defining move or breakthrough moment, but through the accumulated momentum of consistent actions that reinforced each other over time. The flywheel metaphor captures the physics of this: early turns of the wheel are effortful and produce little visible motion; as momentum builds, the same effort produces dramatically greater output. The compounding is structural, not circumstantial.
What makes the flywheel analytically powerful is the causal loop structure. Unlike a growth projection or a value chain map, a flywheel explicitly asks: what causes what? Which actions lead to which outcomes, and which outcomes reinforce which actions? This forces clarity about the mechanism of growth rather than just the direction of it. Amazon's flywheel — lower prices drive traffic, traffic attracts sellers, sellers increase selection, selection improves customer experience, which enables lower prices — is so powerful because every element of the loop feeds the others. You can't weaken one element without weakening the whole.
The flywheel also solves a common problem in strategic planning: teams identify what they want to achieve but not what actually produces it. A revenue target is not a flywheel — it's an outcome. The flywheel forces the team to trace backwards from the outcome to the mechanism: what specifically causes revenue to grow in this business, and what causes that thing to grow? This is where most strategic plans are weakest, and where the flywheel thinking is most valuable.
The mechanism: Flywheels don't create momentum — they reveal where momentum is already trying to accumulate, so you can invest there rather than in places that don't compound. The discipline is in being honest about which loop you're actually in, not the one you'd like to be in. An honestly drawn flywheel is a strategic clarity tool; a flattering one is just a diagram.
Frequently asked questions
How many elements should a flywheel have?
Typically four to six. Fewer than four and the causal loop is usually too simple to be accurate; more than eight and the diagram becomes a general description of everything that matters rather than a focused model of the core mechanism. The discipline is in keeping the loop tight: every element should be causally necessary for the next one to grow. If an element is interesting but not causally required, remove it. A smaller, honest flywheel is more actionable than a large, comprehensive one.
How is a flywheel different from a business model?
A business model describes how the business creates, delivers, and captures value — the static structure. A flywheel describes the dynamic mechanism by which growth compounds — how each part of the system makes the other parts stronger over time. A business can have a clear business model and a broken flywheel (each element doesn't reinforce the others), or a strong flywheel and a weak business model (the loop compounds but in a direction that doesn't capture value). You need both.
What if our flywheel isn't spinning — what does that tell us?
A flywheel that isn't spinning usually means one of two things: the loop is broken (one of the causal connections doesn't actually hold in practice), or one element is missing (the loop is actually longer than you've drawn it, with a missing step that breaks the compounding). WAiDE will help you diagnose which by asking where specifically the chain breaks down — where the expected output of one element isn't materialising as the input to the next. That's the constraint the loop needs.
Can a flywheel be used for internal initiatives, not just whole businesses?
Yes — and it's often more immediately useful at that level. Any initiative that needs to build momentum over time — a community, an internal platform, a training program, a product feature — has a potential flywheel structure. The question is always the same: what causes adoption to grow, and does that growth cause further adoption? Drawing the loop for a specific initiative makes the compounding mechanism visible and allows you to identify where to invest to accelerate it.