Alliance & Partnership Design

Design a strategic alliance or partnership on purpose: why this partner and why not build or buy, how value and control are split, how the two sides will work together, and how it ends if it has to.

Evidence: mixed. The research overview by Kale & Singh (2009) finds that alliances are common, success rates are surprisingly low, and outcomes depend on how each phase is managed and on firm-level alliance capability. The failure modes on this page are this library's own list, not taken from the review. Outcomes vary widely by context.

Use it when:

• You are about to sign a joint venture, distribution, technology or co-development partnership.
• An alliance is your entry mode into a new market and you need to design the terms (see 7.12 Entry Mode & Local vs Global).
• An existing alliance drifts: meetings thin out, nobody owns it, and neither side is sure what it is for.

Skip it when:

• You are buying a standard service at a standard price: a plain supplier contract is enough.
• You have not yet decided between alliance, acquisition and going alone as an entry mode: do 7.12 Entry Mode & Local vs Global first.

Kale and Singh (2009) describe a paradox in alliance research: alliances are common, yet success rates are surprisingly low. They point to how each phase of the alliance is managed and to a firm-level capability for running alliances.

This page is the library's practitioner reading. Alliances that work tend to rest on complementarity and fit assessed before signing, governance written for the day interests diverge rather than for the honeymoon, and a deliberate way of running the relationship afterwards. The failure modes below are this page's own list, not verified against the review: neglect with no named owner, exclusivity granted before performance, and the learning race, where the partner absorbs your capability faster than you absorb theirs and the alliance fades from their side. Each section answers one of them.

Strong answer: the purpose fits one sentence and the choice of alliance is argued against alternatives: "Reach installers in Italy within two years without building a sales force; buying is too costly and a plain distributor contract gives no service quality." Not: "A strategic partnership for mutual growth."

What the alliance is for (one sentence):

Why an alliance and not build, buy or a plain supplier contract:

Illustrative example: the companies are made up.

A Finnish maker of electric boat motors partners with an Italian boatyard group. Section 1: the purpose is to reach yacht buyers in the Mediterranean in two years without building its own sales organization; buying a boatyard is too costly and a distributor contract gives no control over installation quality. Section 2: the maker brings the motors and training, the group brings customers and installation sites. The contract grants exclusivity only after the group meets sales targets; the customer register is held in a joint entity; two engineers from the maker spend part of each year at the group's yards as the learning plan. Section 3: a named owner on each side, monthly reviews. Section 4: exclusivity lapses after two years of missed targets; either side may buy the joint entity at a formula price.