Incremental Vs Leap Growth

---
name: incremental-vs-leap-growth
description: "Activate when: growth has stalled despite good execution; a team disagrees whether a goal is 'realistic'; someone says their initiative is transformative but measures it with quarterly targets; you're designing a new market entry or capability platform.
  Do NOT activate when: organization is in survival mode (cash runway < 6 months) — address that constraint first; the goal hasn't been defined yet — use first-principles or jobs-to-be-done first. More: deciqai.com/s/incremental-vs-leap-growth"
---

# Incremental vs. Leap Growth

## Overview

The most common strategic error is applying the wrong growth *mode* to a goal. Incremental optimizes within an existing trajectory — phased execution, quarterly measurement. Leap abandons the existing trajectory for a higher-order one — grand goal first, resource assembly second, concurrent parallel workstreams. The tools, timescales, and risk profiles are fundamentally incompatible. Organizations default to incremental (it's measurable on familiar timescales), systematically strangling leap initiatives before they reach the stage where value accumulates.

**Compose with:** [strategic-spiral-momentum] (phases 1–3 = leap; phases 7–8 = incremental) · [margin-of-safety] (leap needs larger buffers) · [okr-goal-setting] (run after classifying mode).

## When to Use

- Transformative initiative measured quarterly — suspected mode-metric mismatch
- Growth plateaued despite good execution — possible trajectory ceiling
- New market entry, business model, or capability platform — leap mode by default
- Cost-efficiency, retention, or process excellence program — incremental mode by default
- Leadership disagrees on whether a goal is "realistic" — often a masked mode disagreement

**When NOT to use:** Survival mode (cash runway < 6 months); goal not yet defined (use first-principles first); purely operational work.

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** concrete initiative → run The Process directly.
- **Coach mode:** unfamiliar or no concrete case → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. "Two ways to grow: get 5% better each month, or jump to a completely different track. They need completely different plans."
2. "Does your goal feel like optimizing what you have, or building something qualitatively new?"
3. "Is your goal more like *getting better at something you're already doing*, or *doing something at a completely different scale*?" > **[WAIT — do not advance until user responds]**
4. "Write your goal. Then: 'I'll know we're making progress when ___.' Quarterly number = incremental. Capability/position you don't yet have = leap." > **[WAIT — do not advance until user responds]**
5. "Once you know the mode, you stop feeling anxious that your leap isn't showing results in month 3. Leap initiatives are quiet in phase 1 and explosive at stage transitions." > **[WAIT — do not advance until user responds]**

## The Process

**Step 1 — Classify.** Optimization of existing trajectory (incremental) or step-change to a new one (leap)?
- 5–30% better on existing metrics → incremental; requires capabilities/positions you don't have → leap
- Primary resource = execution excellence → incremental; capital/talent/partnerships you lack → leap
- Quarterly progress meaningful → incremental; only at 12–36 month milestones → leap
- **Gate 1:** If both, split into separate workstreams with separate metrics and governance.

**Step 2 — Verify tool-set alignment.**
| Dimension | Incremental | Leap |
|-----------|------------|------|
| Goal | Specific improvement vs. baseline | Grand goal: destination state regardless of current resources |
| Execution | Sequential: build on what works | Concurrent: N parallel subtasks simultaneously |
| Measurement | Output metrics, quarterly | Stage transition criteria; milestone gates |
| Resources | Deploy existing | Identify missing; then assemble |

**Step 3 — For leap: state the grand goal.** "By [year], we will [position/capability/scale] such that [strategic consequence]." List resources required — not what you have, but what must exist.

**Step 4 — Design stage transitions.** Stage 1 exit: leap hypothesis viable? Stage 2: model scaling? Stage 3: new trajectory established?

**Step 5 — Design concurrent execution.** Decompose into N parallel subtasks. Assign owner, timeline, integration point to each.

**Step 6 — Stop-rule.** Cannot name stage transition criteria = leap *aspiration*, not a *plan*. Return to Step 4.

### Output: Growth Mode Diagnostic
```
Initiative: ___  Date: ___  Classification: [ ] Incremental  [ ] Leap  [ ] Split  Evidence: ___
Incremental → Baseline: ___ Target: ___ Timeline: ___ OKR: ___ Owner: ___
Leap → Grand goal: ___  Missing: Capital/___ Talent/___ Partners/___ Capabilities/___
       Stage 1 exit: ___  Stage 2 exit: ___  Stage 3 exit: ___
       Subtask 1: ___ / Owner: ___ / Integration: ___  Subtask 2: ___ ...
Mode-metric alignment: [ ] Yes [ ] No  If No: ___
```
*→ Method in Action: [U.S. Interstate Highway System (1956–1992)](examples/us-interstate-highway-system-1956-1992.md)*

## Growth Mode Packs
- **Startup Scaling:** Pre-PMF = leap. Post-PMF = incremental. Failure: founders stay in leap when incremental discipline is needed.
- **Corporate Innovation:** Incremental governance (quarterly OKRs, cost center budgets) kills leap programs. Leap needs stage-gated funding.
- **National Industrial Policy:** South Korea DRAM (1983–1993) — state grand goal, assembled resources, concurrent investment across Samsung/Hyundai/LG. Source: Mathews & Cho, *Tiger Technology* (Cambridge, 2000).

## Applying It Well

1. State the mode before stating the plan — mismatched tools create team incoherence.
2. Incremental stalls when measured lazily; leap stalls when measured prematurely.
3. Leap requires a resource *assembly* plan, not a deployment plan — missing resources = stage transition failure.
4. Concurrent execution is a design choice: assign explicit owners, timelines, integration points.
5. Exit leap mode at Stage 3; preserve incremental discipline (weekly cadence) within each parallel subtask.
6. Separate governance: leap needs its own budget pools and review cadences.
*→ Primary sources: [references/sources.md](references/sources.md)*

## Common Rationalizations

**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**

| Rationalization | Why It Fails |
|-----------------|--------------|
| [D] "We're doing both simultaneously." | Possible only if workstreams are separated. Blended = neither mode works. |
| [D] "No results yet — but it's only been 6 months." | Valid only if stage transition criteria were defined upfront. Without them, can't distinguish normal leap pattern from failure. |
| [D] "Incremental is too slow — we need to leap." | Leaping from a broken incremental foundation produces an unstable leap. Fix the baseline first. |
| [D] "We set a 10x goal, so we're in leap mode." | Goal size doesn't determine mode. 10x via optimization = incremental. 2x requiring new capability platform = leap. |
| [D] "We can track pipeline quarterly for the leap." | Pipeline in phase 1 is not a stage transition indicator. Requires stage-level criteria. |
| [D] "We'll do a lean leap due to resource constraints." | Fails at stage transition — not because the goal was wrong but because the resource hypothesis was wrong. |
| [D] "We'll know progress when we see it." | Motivated reasoning — any positive signal gets declared as progress regardless of capability actually established. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |

## Red Flags
- "Transformational" initiative with quarterly OKRs on existing metrics — mode-metric mismatch
- Progress narrative is activity-based ("held workshops") not stage-transition-based ("validated hypothesis with 3 paying customers at target economics")
- Timeline extended repeatedly without specifying which stage transition criteria will be met
- Resource assembly plan is "we'll figure it out as we go"
- Leap language on an optimization goal to avoid accountability; or leap team in a single sequential workstream

## Verification
- [ ] Classified as incremental or leap (not "both" unless workstreams separated)
- [ ] Incremental: quarterly metrics, baseline, target, execution owner stated
- [ ] Leap: grand goal as destination state; resource assembly names what's missing and how to obtain it
- [ ] Stage transition criteria defined for leap: Stage 1 → 2 → 3 conditions stated
- [ ] Measurement cadence matches mode: quarterly for incremental; stage-gate for leap
- [ ] Concurrent execution documented: N parallel subtasks, owners, integration points
- [ ] Stop-rule verified: failure criteria and timing articulated; governance separated

---
*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/incremental-vs-leap-growth** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*

*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/incremental-vs-leap-growth.json*