apply-second-front-strategy

name	apply-second-front-strategy
description	Use when competing for contested territory against a stronger opponent who outguns you in direct confrontation — to relieve pressure on the primary front by creating a genuine crisis at the opponent's rear or home base
source	Thirty-Six Stratagems
tags	["thirty-six-stratagems","second-front","flanking","competitive-strategy","besiege-wei"]
verified	true

Apply Second Front Strategy

Force an opponent stronger on the primary front to split their attention by opening a credible second front at their rear or home base, creating the opening you need on the original contested ground.

Why This Is Best Practice

Origin: Stratagem #2 of the Thirty-Six Stratagems derives from the Battle of Guiling (353 BC): when Zhao was besieged by Wei, general Sun Bin did not march to relieve Zhao directly — he marched on Wei's capital. Wei was forced to withdraw from Zhao to defend its own territory. The stratagem's insight is that a stronger opponent cannot defend two genuine crises simultaneously; the second front converts a defensive situation into an offensive one.

Adopted by: Every major flanking strategy in business follows this pattern. Google's Android launch (2007) did not attack Microsoft's Windows directly — it attacked the mobile market that was becoming Microsoft's path to ubiquity in computing. Microsoft was forced to split attention between Windows, mobile, and the browser war simultaneously. Amazon Web Services targeted enterprise IT infrastructure (IBM, HP, EMC territory) while competing in retail — each front forced the incumbents to defend turf they could not easily abandon. Christensen's innovator's dilemma describes why incumbents cannot respond effectively to second fronts: the rear attack requires defending a less-profitable position that leadership undervalues.

Impact: Direct confrontation with a stronger opponent on their chosen ground is the most expensive form of competition. The second front converts your opponent's strength into a vulnerability — their dominance on the primary front requires commitments (people, capital, attention) that cannot instantly redeploy to the rear. The time window between opening the second front and the opponent's effective response is your operational opportunity on the primary front.

Why best: Most competitive responses are mirror-image: match the opponent's product, price, or channel. The second front strategy breaks the mirroring — it forces the opponent to respond to an attack they didn't expect on ground they considered secure. The asymmetry is the advantage: you choose the second front based on where you can create maximum disruption at minimum cost; the opponent must respond regardless of cost.

Sources: Thirty-Six Stratagems #2 (Sawyer trans. 1994); Verstappen, The 36 Strategies of Ancient China (2007); Grove, Only the Paranoid Survive (1997); Christensen, The Innovator's Dilemma (1997)

Steps

Step 1: Map the opponent's rear — where are they undefended?

Identify the parts of the opponent's position that are:

• Essential to them — they cannot afford to lose it
• Under-defended — less attention, less investment, less capability than the primary front
• Reachable by you — you have or can build the capability to threaten it

Rear vulnerability type	Signal
Home market	Dominant in one geography, expanding into yours
Key accounts	Incumbent in enterprise; SMB left unserved
Adjacent product category	Strong in core; weak in adjacent segment they need to defend
Supply or distribution	Dependent on a specific supplier, platform, or channel
Talent base	Key capability concentrated in one location or team

Step 2: Assess whether the second front is genuinely threatening

The second front must pass two tests:

1. The opponent cannot ignore it: If they ignore the second front, they lose something essential. A threat they can ignore is not a second front — it is a distraction to yourself.
2. You can sustain it: You must be able to maintain pressure on the second front long enough to exploit the primary front opening. A second front that collapses on contact is worse than no second front.

If the second front does not pass both tests, do not open it.

Step 3: Open the second front before the opponent can pre-empt

Speed determines whether the second front succeeds. Once the opponent recognises the threat, they will either:

• Reinforce the rear before you can establish position
• Try to force a resolution on the primary front before your rear pressure takes effect

Move to establish position on the second front before signalling your intent. Announcement after establishment; not announcement as the move.

Step 4: Maintain credible pressure — do not allow the second front to collapse

A second front that is abandoned forces the opponent back to full concentration on the primary contest. Requirements for sustained second-front pressure:

• Commit enough resource to make withdrawal from the second front painful, not tactical
• Ensure the second-front attack serves its own competitive logic, not just as a distraction
• Resist the temptation to consolidate resources back to the primary front before the opening appears

Step 5: Exploit the primary-front opening while the opponent is split

When the opponent redirects to the rear, the primary front opens. Act fast:

• The opening is temporary — the opponent will triage and reallocate
• The actions taken on the primary front during this window should be irreversible: signed contracts, integrated systems, locked-in key accounts, established market position
• Do not signal the primary-front move until you are executing it — the opponent must not be able to respond to both crises simultaneously

Rules

• Both fronts must be genuine competitive attacks, not one real and one feint. An obvious feint forces the opponent's best response onto the primary front; a genuine second front forces real resource allocation.
• Never open a second front that exhausts your reserve before the primary-front window opens. The second front is the instrument; the primary front is the objective.
• The second front should serve a strategic purpose beyond distraction — ideally, winning on the second front also creates value independently of the primary front opening.
• If the opponent ignores your second front and concentrates on defeating you on the primary front, you may need to escalate the second front or abandon it. Do not continue a second front that is not affecting opponent resource allocation.
• Assess whether the opponent can sustain simultaneous defence — a well-capitalised incumbent may not need to split attention if the second front is too small.

Examples

Google Android vs. Microsoft (mobile as second front): In 2007, Microsoft had dominant positions in desktop OS, enterprise productivity, and was the primary platform for PC software. Google did not attack Windows directly — it opened Android as a free, open-source mobile platform that threatened Microsoft's path to mobile ubiquity. Microsoft was forced to split executive attention, R&D budget, and partnership resources across Windows, Office, Bing, mobile, and the browser war simultaneously. Google exploited the primary front (search dominance, advertising, web services) while Microsoft's attention was fragmented. Windows Mobile and then Windows Phone never achieved traction; Microsoft's enterprise lock-in through Office eventually shifted to Google Workspace in the SMB segment.

Amazon AWS vs. IBM/HP/EMC (cloud infrastructure as rear attack): Amazon entered enterprise IT infrastructure — home territory for IBM, HP, and EMC — via AWS. The incumbents dominated on-premise hardware, services, and data center contracts. AWS did not compete on those contracts directly; it offered cloud infrastructure that made the data center itself unnecessary. IBM, HP, and EMC were forced to maintain existing business (profitable but declining) while building cloud capabilities (expensive, disruptive to margins). Amazon exploited the opening in the SMB and startup markets (undefended rear for enterprise incumbents), established irreversible position as the cloud standard, and then moved upmarket into enterprise contracts the incumbents had considered safe.

Startup flanking an enterprise incumbent: A startup selling DevOps tooling competes against an enterprise incumbent that controls the CI/CD budget in large enterprises. Direct competition on enterprise contracts is prohibitively expensive. Second front: target the open-source developer community with a free tool that individual engineers adopt without IT procurement approval. As the open-source tool spreads inside enterprise accounts, the incumbent finds its contracts up for renegotiation with engineering teams that have already standardised on the startup's tooling. The startup exploits the primary-front opening (enterprise contracts) only after the second front (developer adoption) has made the incumbent's position untenable.

Common Mistakes

Opening a second front the opponent can ignore: A second front that threatens something the opponent does not value — or can easily write off — produces no opening on the primary front. It only splits your own resources. Verify the second front attacks something essential before committing.

Under-resourcing the second front: A symbolic second front that the opponent can neutralise with minimal reallocation does not create the opening you need. The second front must require genuine opponent resource commitment.

Abandoning the second front prematurely: If the second front collapses before the primary-front opening appears, the opponent re-concentrates and your primary-front position is unchanged. Sustain the second front until the primary front is irreversibly won.

Conflating the second front with a product pivot: The second front is a competitive maneuver, not a hedge. If your organisation treats the second front as a fallback rather than an attack instrument, resource commitment will be insufficient to create genuine opponent pressure.

Telegraphing both attacks simultaneously: Announcing the second front before establishing position invites pre-emption. Establish, then announce.