Flywheel Design

---
name: flywheel-design
description: Design self-reinforcing growth cycles where each element feeds the next, creating compounding advantages over time. This is the strategic architecture behind Amazon's dominance.
license: MIT
metadata:
  version: 1.0.4018
  author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- flywheel-design
- structure
- writing
---

# Flywheel Design

Design self-reinforcing growth cycles where each element feeds the next, creating compounding advantages over time. This is the strategic architecture behind Amazon's dominance.

---

## When to Use

- User asks "How do we scale?"
- Business model design or redesign
- Growth strategy development
- Understanding competitive moats
- Creating sustainable advantages
- Request for flywheel analysis

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| business | Yes | The business, product, or initiative |
| components | No | Key activities or value drivers (will be identified if not provided) |
| constraints | No | Resources, market, or capability limits |

---

## The Flywheel Concept

### What is a Flywheel?

A flywheel is a heavy revolving wheel that builds momentum. Once spinning, it's difficult to stop and generates energy that feeds itself.

In business, a flywheel is a self-reinforcing cycle where each element accelerates the others. You push hard to get it started, but once moving, momentum carries it forward with less effort.

### The Amazon Flywheel (Original Example)

Bezos sketched this on a napkin in 2001:

```
Lower Prices
    → More Customers
    → More Sellers
    → Better Selection
    → Better Customer Experience
    → More Traffic
    → Lower Cost Structure
    → Lower Prices
```

Each element feeds the next. The cycle compounds over time.

### Flywheel vs. Linear Growth

**Linear growth:** More effort → More output (constant ratio)
**Flywheel growth:** More effort → More momentum → Disproportionately more output

Flywheels create increasing returns. Each revolution is easier than the last.

---

## Design Framework

### Step 1: Identify the Core Value

What is the primary value you deliver to customers? This anchors the flywheel.

**Questions:**
- What do customers pay for?
- What would they miss most if you disappeared?
- What job are you hired to do?

### Step 2: Map the Reinforcing Loop

Identify elements that feed each other:

**Questions:**
- If we improve [A], what else improves automatically?
- What enables us to deliver more value?
- What do we get more of when we succeed?
- How does success breed more success?

### Step 3: Identify the Acceleration Points

Where does additional investment have disproportionate impact?

**Questions:**
- Which element, if improved 10%, would improve others most?
- Where do small wins create big momentum?
- What's the highest-leverage point in the cycle?

### Step 4: Find the Friction Points

What slows the flywheel?

**Questions:**
- Where does the cycle break down?
- What prevents acceleration?
- Where do we lose customers/momentum?

### Step 5: Design for Compounding

Ensure the flywheel truly compounds:

**Requirements:**
- Each element must feed at least one other element
- There must be a complete loop (no dead ends)
- The loop must be positive (growth, not decline)
- Time must make it stronger, not weaker

---

## Common Flywheel Patterns

### The Network Effect Flywheel
More users → More value to each user → More users

**Example:** Social networks, marketplaces

### The Content Flywheel
More content → More traffic → More creators → More content

**Example:** YouTube, Medium

### The Data Flywheel
More usage → More data → Better product → More usage

**Example:** Google, Netflix recommendations

### The Scale Flywheel
More volume → Lower costs → Lower prices → More volume

**Example:** Amazon, Walmart

### The Brand Flywheel
Better experience → More word-of-mouth → More customers → More resources → Better experience

**Example:** Apple, Costco

---

## Workflow

### Step 1: Gather and Review Inputs

Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria

### Step 2: Analyze the Situation

Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings

### Step 3: Generate Recommendations

Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility

## Output Format

```markdown
## Flywheel Design: [Business/Product]

### Core Value
[What anchors the flywheel - the primary customer value]

### The Flywheel

```
[Element A]
    → [Element B]
    → [Element C]
    → [Element D]
    → [Element A]
```

### Element Breakdown

| Element | How It Feeds Next | Metrics |
|---------|-------------------|---------|
| [A] | [Explanation] | [How to measure] |
| [B] | [Explanation] | [How to measure] |
| [C] | [Explanation] | [How to measure] |
| [D] | [Explanation] | [How to measure] |

### Acceleration Points
[Where to invest for maximum momentum]

1. **[Point 1]:** [Why this accelerates the flywheel]
2. **[Point 2]:** [Why this accelerates the flywheel]

### Friction Points
[Where momentum is lost]

1. **[Point 1]:** [What causes friction, how to reduce it]
2. **[Point 2]:** [What causes friction, how to reduce it]

### Flywheel Health Check

| Criterion | Status | Notes |
|-----------|--------|-------|
| Complete loop | [Yes/No] | [Observation] |
| All elements reinforcing | [Yes/No] | [Observation] |
| Compounds over time | [Yes/No] | [Observation] |
| Defensible | [Yes/No] | [Observation] |

### Investment Priorities

**Push hard on:** [Where to focus effort]
**Maintain:** [Elements that are working]
**Fix:** [Elements that are broken]

### Long-term Vision
[What this flywheel looks like at full momentum]
```

---

## Constraints

- Flywheels must be complete loops (no dead ends)
- Every element must truly feed the next (not just correlate)
- The flywheel must compound over time
- Complexity kills flywheels - keep it simple
- If you can't draw it on a napkin, it's not a flywheel

---

## Outputs

**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

**Format:**
```markdown
## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```

**Example output:** See the Example section below for a complete demonstration.

## Example

**Input:** "We're a SaaS company that provides project management tools. How do we think about our growth engine as a flywheel?"

**Output:**



**Why this works:**

This example demonstrates the key principles of the skill in action. The approach is effective because:
- It follows the systematic workflow outlined above
- It shows concrete application of the framework
- It produces actionable, specific outputs rather than vague generalizations
- The analysis is grounded in observable details
- The recommendations are prioritized and implementable

**Alternative applications:**

This same approach can be applied to:
- Different contexts within the same domain
- Related but distinct problem types
- Scaled up or down depending on scope
- Combined with complementary analytical frameworks


## Flywheel Design: Project Management SaaS

### Core Value
Teams ship projects more successfully with less coordination overhead.

### The Flywheel

```
More Successful Projects
    → More Team Adoption
    → More Data on Project Patterns
    → Smarter Automation/Suggestions
    → Less Coordination Overhead
    → More Successful Projects
```

### Element Breakdown

| Element | How It Feeds Next | Metrics |
|---------|-------------------|---------|
| More Successful Projects | Teams tell other teams; case studies for marketing | Project completion rate, NPS |
| More Team Adoption | Within-company expansion; more usage data | Teams per account, DAU |
| More Data on Project Patterns | ML training data; benchmark insights | Data volume, pattern accuracy |
| Smarter Automation | Features that differentiate from competitors | Automation adoption, time saved |
| Less Coordination Overhead | The core value delivered | Hours saved per project |

### Acceleration Points

1. **Within-company expansion:** A team that succeeds becomes an internal advocate. Make sharing and inviting frictionless. Every new team adds data and advocacy.

2. **Automation that actually saves time:** This is the moment users become evangelists. When the tool does something smart they didn't expect, they tell colleagues.

### Friction Points

1. **Onboarding complexity:** If the first project fails, the flywheel never starts. The first 7 days determine everything. Invest in onboarding until first-project success rate exceeds 80%.

2. **Data silos between teams:** If teams use the tool in isolation, you don't get cross-team pattern data. Design for organizational-level visibility to unlock the data flywheel.

### Flywheel Health Check

| Criterion | Status | Notes |
|-----------|--------|-------|
| Complete loop | Yes | Success leads back to more success |
| All elements reinforcing | Mostly | Data → Automation link needs investment |
| Compounds over time | Yes | More data = better product = more adoption |
| Defensible | Moderate | Data moat grows with scale |

### Investment Priorities

**Push hard on:**
- First-project success rate (the flywheel entry point)
- Automation that demonstrably saves time (the advocacy trigger)
- Within-company expansion mechanics (the growth multiplier)

**Maintain:**
- Core project management features (table stakes)

**Fix:**
- Data → Automation pipeline (underinvested, key differentiator)

### Long-term Vision

At full momentum: Every successful project generates data that makes the next project easier to run. Teams that use the tool can't imagine going back. Automation handles 50% of coordination that used to require meetings. New teams onboard by seeing how successful teams work, not by reading documentation. The product gets smarter faster than competitors because it processes more projects.

**The moat:** Your data on how successful projects run, across thousands of teams, is an asset no competitor can replicate without the same scale. This is the defensible flywheel.

---

## Integration

This skill is part of the **Jeff Bezos** expert persona. Use it when designing business models, growth strategies, or seeking to understand sustainable competitive advantages.