design-alliance-strategy

name	design-alliance-strategy
description	Use when competing in a market where third-party relationships — partners, distributors, platforms, standards bodies, or key suppliers — determine who wins, to build your own coalition while preventing the opponent from forming theirs
source	Sun Tzu "The Art of War" Ch.3, 11 (Giles trans. 1910; Griffith trans. 1963); Brandenburger & Nalebuff "Co-opetition" (1996); Doz & Hamel "Alliance Advantage" (1998)
tags	["alliances","partnerships","coalition","ecosystem","co-opetition","sun-tzu","art-of-war","intersecting-ground"]
related	["audit-partnership-values-alignment"]
verified	true

Design Alliance Strategy

Map every third party whose relationship determines the outcome, build your coalition before the opponent does, break apart their existing alliances, and control the intersecting ground where multiple stakeholders converge.

Why This Is Best Practice

Origin: Sun Tzu places alliance attack as the second-highest form of strategy — superior to attacking the enemy's army and vastly superior to besieging their cities: "The highest form of generalship is to balk the enemy's plans; the next best is to prevent the junction of the enemy's forces; the next in order is to attack the enemy's army in the field; and the worst policy of all is to besiege walled cities." (Ch.3, Giles trans.) Preventing the enemy's alliances is preferable to fighting them because it wins without the cost of direct conflict.

Adopted by: The "intersecting ground" principle from Ch.11 — "On intersecting ground, join hands with your allies" — is the strategic logic behind every major platform and ecosystem play. Brandenburger & Nalebuff formalised this in Co-opetition (1996): the value net (complementors, suppliers, customers, competitors) must be actively managed, not just analysed. Doz & Hamel's Alliance Advantage (1998) is the definitive business text on building and extracting value from alliances. Microsoft's control of PC OEM relationships in the 1990s, Google's Android OEM licensing strategy, and Salesforce's AppExchange ISV program are all alliance-as-weapon executions.

Impact: In markets with strong network effects, platform economics, or distribution chokepoints, alliance position often determines outcomes more decisively than product quality. A startup with a superior product but no distribution alliances loses to an inferior product with exclusive distribution. A platform with more complementors attracts more customers regardless of native feature parity.

Why best: Most organisations treat partnerships reactively — opportunistic relationships formed when both parties see mutual benefit. Alliance strategy treats the third-party relationship landscape as a competitive battlefield to be won before the engagement begins, not a friendly environment to be navigated after.

Sources: Sun Tzu, The Art of War (Giles trans. 1910) — Ch.3 (Attack by Stratagem), Ch.11 (Nine Situations / Intersecting Ground); Brandenburger & Nalebuff, Co-opetition (1996); Doz & Hamel, Alliance Advantage (1998); Porter, Competitive Advantage (1985) — value chain alliances

Steps

Step 1: Map the value net — all third parties whose position matters

Before building alliances, map every third party who affects the outcome of your competitive engagement:

Role	Who they are	What they control
Complementors	Companies whose products increase the value of yours	Platform extensions, integrations, ecosystem
Distributors	Channels through which customers find and buy	Market access, customer relationships
Suppliers	Inputs your product depends on	Cost, quality, availability of key components
Standards bodies	Organisations that set the rules of the market	Technical compatibility, regulatory approval
Influencers	Analysts, press, communities who shape buyer perception	Customer trust, evaluation criteria
Key customers	Reference accounts whose adoption signals legitimacy	Social proof, market validation

For each third party, assess: (1) How much does this relationship determine competitive outcomes? (2) Is this party currently allied with the opponent, neutral, or potentially aligned with you?

Step 2: Identify and occupy intersecting ground

Intersecting ground — Sun Tzu's 衢地 — is territory whose control gives influence over multiple parties simultaneously. On intersecting ground, "join hands with your allies before the opponent does."

In business, intersecting ground includes:

• Technical standards: A standard that every product must conform to gives its creator influence over every participant in the ecosystem
• Common platforms: An API, marketplace, or integration hub that multiple parties depend on; controlling the platform controls the relationships
• Industry associations and consortia: The organisation that chairs the industry working group shapes the rules
• Key reference customers: A customer whose adoption legitimises the category for other buyers

Occupy intersecting ground before the opponent. Once a standard is established, a platform is dominant, or a reference customer is committed, displacing the occupant is expensive.

Step 3: Build your coalition — prioritise by influence and exclusivity

Not all alliances are equally valuable. Rank potential allies by:

1. Influence over target customers: A partner who controls access to your ideal customer is more valuable than a partner who validates your technology
2. Exclusivity potential: A partner who can commit to working with you exclusively (or preferentially) removes them from the opponent's coalition
3. Complementarity: A partner whose capabilities fill gaps in your own creates a combined offering that neither can deliver alone
4. Strategic alignment: A partner whose long-term interests align with yours is more reliable than one whose interests are transactional

Lead with the most influential, most exclusive potential allies. Winning the top-tier alliances creates a coalition that attracts further allies through association.

Step 4: Prevent the opponent's alliance formation

"Balk the enemy's plans" at the alliance level: identify which alliances the opponent is pursuing and act to prevent them before they are formalised.

Alliance prevention tactics:

• Exclusive commitments: Secure exclusive or preferred partnership agreements with the most strategically important third parties, removing them from the opponent's available alliance set
• Speed of formalisation: Sign partnership agreements, integration contracts, and co-marketing commitments before the opponent approaches the same party
• Better terms: Offer conditions the opponent cannot or will not match — better revenue share, deeper technical integration, preferred partner status, co-development investment
• Coalition credibility: Build a coalition that makes joining your side more credible and beneficial than joining the opponent's; late allies follow the winner's coalition

Step 5: Break apart the opponent's existing alliances

When the opponent has existing alliances that disadvantage your position, apply pressure to those alliances:

Alliance disruption tactics:

• Superior value to shared partners: Offer the partner better terms, better technology, or better market access than the opponent provides
• Highlight incompatibility: Surface the ways the opponent's interests conflict with the partner's — in the long run, what the opponent needs from the partner may harm the partner's position
• Timing: Approach the opponent's partners at the moment of maximum dissatisfaction — when a contract is up for renewal, when the opponent has failed them, when market conditions have changed
• Build alternative partnerships: If the opponent's partner cannot be moved, build a competing partnership that renders the opponent's alliance less strategically decisive

Step 6: Maintain and honour your alliances

Alliance advantage compounds only if alliances are maintained. The most common alliance failure is treating the partnership as a signing event rather than an ongoing relationship.

• Deliver on your commitments to allies before asking them to deliver on theirs
• Invest in partner success as a strategic priority, not a customer service function
• Manage the alliance relationship at the executive level, not just at the operational level
• Address alliance conflicts (competing interests, margin disputes, strategic divergence) before they deteriorate into defection

Rules

• Map the value net before building individual alliances. Uncoordinated alliance formation produces a portfolio of bilateral deals without strategic coherence. The map reveals which alliances create the most leverage.
• Speed matters. Alliance formation is a race. Approach high-priority partners before the opponent does.
• Offer asymmetric value. The alliance must benefit the partner enough that they prefer you over the opponent and maintain that preference under competitive pressure. Transactional alliances defect.
• Do not rely on alliances you do not control. An alliance with no formalised commitment, no exclusivity, and no invested relationship is not an alliance — it is a reference that the opponent can replicate.
• Attack the opponent's alliance strategy before attacking their product or price. Isolating an opponent from their distribution and complementor network is more decisive than matching their features.

Examples

Microsoft + PC OEMs (distribution alliance as weapon, 1980s–90s): Microsoft secured preferential licensing agreements with PC OEMs that effectively made Windows the default operating system on most consumer PCs. The alliance strategy — OEM licensing at attractive terms in exchange for Windows pre-installation — occupied the distribution channel before any competitor could establish a comparable position. Apple's failure to replicate this was as decisive as any product decision.

Google Android (ecosystem coalition, 2007–2010): Google's response to Apple's closed iOS ecosystem: build an open-source Android alliance with handset manufacturers (Samsung, HTC, LG, Motorola) who had no alternative to iOS's terms. By offering manufacturers an open platform and control over hardware differentiation, Google assembled a coalition that Apple's exclusive strategy could not match. The alliance strategy produced 80%+ global smartphone market share by volume.

Startup securing the exclusive reference customer: A startup selling compliance software identifies that Company X is the most influential buyer in the vertical — their adoption will signal legitimacy to all subsequent buyers. The startup offers Company X: (1) a significantly reduced price for the first year; (2) a dedicated implementation team; (3) co-development on features specific to their use case; (4) first right of refusal on new capabilities. In exchange: a public case study, a reference call program, and a 3-year contract. The incumbent cannot offer these terms — too small a customer for their standard process. The startup occupies the reference position before the incumbent responds.

Common Mistakes

Treating alliances as bilateral deals: Alliance strategy requires a portfolio view — each alliance should contribute to a coherent coalition position, not just bilateral benefit. A portfolio of non-strategic bilateral agreements does not produce ecosystem leverage.

Announcing alliances before they are secured: Announcing a partnership in a press release before the formal agreement is signed invites the opponent to counter-offer. Secure the commitment; then announce.

Under-investing in partner success: Partners who do not succeed with your product defect or become passive references. Active partner success investment is alliance maintenance.

Assuming neutrals are available: A third party that has not committed to either side is not neutral — they are in play. Treat uncommitted high-value third parties as contested ground and move to secure their commitment.

Allying with the wrong partner at the right moment: Speed without discrimination produces alliances with low-influence partners that consume relationship capital without creating leverage. Map influence first; then move fast on the high-priority targets.