Apply Protracted Resistance

---
name: apply-protracted-resistance
description: Use when facing a stronger, better-resourced incumbent in an active, ongoing competitive struggle — not a single defeat already suffered — where a quick decisive confrontation favors the incumbent; instead trade ground for time in an opening phase, mobilize broad, distributed, sustained resistance to shift the balance of resources and will over years, then transition to open offensive once that balance has genuinely shifted.
source: 'Mao Zedong, 论持久战 "On Protracted War" (1938), a wartime military-strategic essay written during the Second Sino-Japanese War, analyzed in Western strategic-studies scholarship alongside Clausewitz and Sun Tzu as a classical theory of asymmetric/protracted warfare (e.g., Michael Handel, "Masters of War: Classical Strategic Thought", 3rd ed., 2001, treats this protracted-war theory as one of the core classical strategic frameworks); Eric Raymond, "The Cathedral and the Bazaar" (1999) and Yochai Benkler, "The Wealth of Networks" (2006) on distributed, mass-participation development outlasting concentrated incumbent resource advantage'
tags: [protracted-conflict, asymmetric-strategy, attrition, mobilization, chinese-history, phased-strategy, underdog-strategy]
related: [apply-strategic-endurance, apply-competitive-patience, apply-strategic-momentum]
---

# Apply Protracted Resistance

Against a stronger, actively-engaged opponent, trade ground for time rather than seeking a decisive early confrontation, mobilize broad and sustained resistance to grind down the opponent's resource and will advantage over years, then transition to open offensive only once that balance has genuinely shifted.

## Why This Is Best Practice

**Origin:** In 1938, during the Second Sino-Japanese War, Mao Zedong wrote "On Protracted War" to argue against both the view that China would be quickly defeated by Japan's superior military technology and the view that a single decisive battle could expel the invasion. He proposed a three-phase framework instead: a strategic defensive phase, in which a weaker defender deliberately trades territory for time rather than risking annihilation in a decisive early battle against a stronger opponent's initial advantage; a strategic stalemate phase, in which broad, distributed, sustained resistance — not concentrated in one force or one front — continuously drains the invader's resources, logistics, and political will over years; and a strategic counter-offensive phase, entered only once the balance of attrition has genuinely shifted, transitioning from distributed resistance to conventional offensive operations. The essay is treated in Western strategic-studies scholarship as a classical theory of protracted and asymmetric warfare, analyzed alongside Clausewitz and Sun Tzu.

**Adopted by:** The distributed, mass-participation mechanism generalizes directly to a documented modern business pattern: the open-source software movement's protracted competitive position against concentrated, well-resourced proprietary incumbents. Eric Raymond's "The Cathedral and the Bazaar" and Yochai Benkler's "The Wealth of Networks" document how a distributed, broadly-mobilized volunteer base — individually far weaker than a single incumbent vendor — sustained a multi-year, multi-front competitive effort that neither sought nor could have won a single decisive confrontation, and instead ground down incumbent advantage gradually until platforms like Linux moved from a minor curiosity to displacing proprietary Unix and, later, contesting server and cloud infrastructure dominance over roughly two decades.

**Impact:** The historical case's own outcome carries an important caveat: Japan's eventual defeat in 1945 resulted from the combination of China's sustained resistance and Allied intervention (including the Pacific theater and the atomic bombings), not from protracted resistance alone — the framework's phases describe a real, documented strategic logic, but the case shouldn't be read as proof that protracted resistance alone reliably defeats a stronger power in every instance. In the generalized business case, the open-source movement's multi-decade shift from marginal to dominant in server infrastructure is a more directly attributable, if slower, outcome of the mechanism itself.

**Why best:** This is a different mechanism than the closest adjacent skill, `apply-strategic-endurance` (Goujian's 卧薪尝胆). That skill starts from a single actor already defeated and subjugated, rebuilding covertly under a facade of submission with zero active engagement during the rebuild, ending in one decisive covert strike. This skill starts from an actor still actively engaged in an ongoing contest against a currently-stronger opponent, deliberately ceding ground in the open rather than hiding, sustaining broad and continuous — not covert — resistance throughout the middle phase, and transitioning gradually to open offensive as the balance shifts, rather than executing one hidden decisive strike. It's also distinct from `apply-competitive-patience`, which abstains from a fight already happening between other parties; here, the resistance is your own active, ongoing campaign, not spectating someone else's.

Sources: Mao Zedong, 论持久战 (1938); Handel, *Masters of War: Classical Strategic Thought* (2001); Raymond, *The Cathedral and the Bazaar* (1999); Benkler, *The Wealth of Networks* (2006).

## Steps

1. **Confirm you are in an active contest against a currently stronger opponent, not already defeated.** This distinguishes the starting condition from `apply-strategic-endurance` — the opponent hasn't yet won; a decisive early confrontation on their terms would likely favor them, but the contest is still open.

2. **Trade ground for time in the opening phase — don't risk a decisive early confrontation.** Deliberately cede low-value ground or defer contesting a battle you'd lose outright, in order to avoid the annihilating early engagement a stronger opponent wants. This is an open, acknowledged retreat from specific fights, not concealment.

3. **Mobilize broad, distributed resistance rather than concentrating in one front.** The middle phase's strength comes from sustained pressure across many simultaneous, smaller fronts rather than one large, decisive engagement — many independently-sustainable efforts are harder for a stronger opponent to defend against everywhere at once than a single large force is to defeat directly.

4. **Sustain the middle phase long enough to actually shift the resource/will balance.** The grinding phase has to run long enough to erode the stronger opponent's logistics, resources, or political will — judge progress by observable shifts in the opponent's capacity and commitment, not by a fixed calendar.

5. **Transition to open offensive only once the balance has genuinely shifted — not before.** Moving to concentrated, decisive offensive action while the opponent still holds the resource/will advantage repeats the mistake the opening phase was designed to avoid. Confirm the shift with observable evidence (opponent's resource exhaustion, reduced commitment, or overextension) before transitioning.

## Rules

- Confirm the contest is still active and the opponent hasn't already defeated you — if defeat has already occurred, use `apply-strategic-endurance` instead, not this framework.
- The opening retreat must be open and acknowledged, not a covert facade — this mechanism works through visible, distributed, sustained resistance, not concealment.
- Don't transition to concentrated offensive action until the resource/will balance has actually and observably shifted — premature offensive action against a still-dominant opponent repeats the exact risk the opening phase existed to avoid.
- Judge the middle phase's progress by the opponent's observable exhaustion, not by elapsed time alone.

## Examples

**Trigger:** A well-funded, dominant incumbent controls a market and could win any single head-to-head confrontation against a much smaller, distributed challenger community.
→ The challenger avoids a single decisive product battle it would lose. Instead, a broad, distributed base of independent contributors sustains development across many fronts simultaneously — not concentrated in one team or one product line — gradually eroding the incumbent's structural advantages (lock-in, switching costs, ecosystem lead) over years. Only once the incumbent's advantage has genuinely eroded does the challenger move to directly and openly contest the incumbent's core position, rather than doing so from a position of continued weakness.

**Trigger:** A smaller company is being squeezed by a dominant competitor's superior resources in every direct product comparison.
→ Rather than matching the incumbent feature-for-feature in a battle it would lose, the smaller company deliberately cedes ground in segments it can't defend, sustains a broad, low-cost, distributed presence across many smaller niches the incumbent can't efficiently defend everywhere at once, and waits for observable signs the incumbent's resources or focus are strained before committing to a direct, open confrontation over the core market.

## Common Mistakes

- **Applying this to a fight already lost.** If the opponent has already won decisively, the covert, single-actor rebuild logic of `apply-strategic-endurance` fits the situation better than this framework's open, distributed, actively-engaged resistance.
- **Concentrating resistance in one front instead of distributing it.** The middle phase's resilience against a stronger opponent comes specifically from being spread across many independently-sustainable fronts — concentrating defeats the purpose and exposes the resistance to the same decisive-confrontation risk the opening phase was designed to avoid.
- **Transitioning to offensive action before the balance has actually shifted.** Premature counter-offensive against a still-dominant opponent, based on elapsed time or wishful reading of progress rather than observed evidence, repeats the exact risk this framework exists to manage.
- **Treating the historical outcome as proof that protracted resistance alone always defeats a stronger power.** Japan's actual defeat involved Allied intervention alongside China's resistance — overstating the mechanism's standalone causal power misreads the historical record.

## When NOT to Use

- When a decisive early confrontation genuinely favors you — this framework is specifically for situations where the opponent currently has the advantage; using it when you could win decisively now just cedes ground you didn't need to cede.
- When the contest requires an immediate resolution and there's no viable multi-year runway — this is a multi-year, phased mechanism, not a fast turnaround technique.
- When resistance can't genuinely be distributed across independent fronts (a single team, a single product, a single point of failure) — the middle phase's resilience depends on distribution; without it, the mechanism collapses into a single vulnerable position the stronger opponent can target directly.