Alliance Prioritization

Alliance Prioritization

Rank specific, named candidate alliances and technology partnerships against each other, and decide which ones the team invests in. No single canonical ranking method owns this discipline - say so plainly rather than invent one. What the evidence actually supports:

• A dedicated alliance function and structured process is the field's best-validated success driver: 63% vs 50% alliance success across 1,572 alliances (Kale, Dyer & Singh, 2002). A repeatable prioritization process is part of that function.
• Complementarity plus compatibility is the best-validated fit construct: partners different in resources, similar in organizational institutions (Sarkar et al.; Mindruta, Moeen & Agarwal, 2016). Weight these highest.
• Weighted scorecards are known-fragile machinery: rank reversal (Belton & Gear, 1983) and arbitrary weights (Dyer, 1990). The fixes - justified weights, sensitivity analysis, must-pass gates kept outside the tradeable score - are mandatory here, not optional polish.
• The famous "50-70% of alliances fail" figure is unsettled: published estimates span 20-80% depending on how failure is defined, and one credible re-analysis puts it at 25-30%. Never quote it as settled fact.

Interview

Ask before ranking anything. One question per message; offer multiple-choice options; skip whatever the user already answered.

• How many named candidates, and who are they? (Categories instead of names → the ecosystem sibling; a single candidate → the economics sibling.)
• What strategic goal must the ranking serve: pipeline, product-gap fill, market entry, retention, platform presence, brand reach?
• How many alliances can the team actually run - headcount, current load per alliance manager? This number becomes the shortlist cut line.
• What does the existing alliance portfolio look like: active alliances, concentration, redundancy or conflict with the candidates?
• What data exists per candidate: account-overlap data, closed-won history, integration usage, marketplace co-sell records, prior-relationship history?
• Any candidate that is politically protected - an executive relationship, board pressure, a prior tie? Name it now; it gets scored like the rest, visibly.
• Who signs off, and does a gate process or steering committee already exist?
• B2B tech alliances, B2C brand/creator partnerships, or a hybrid list?
• By what date must this ranking land - a board slide next week, a signed alliance this quarter, next year's plan?
• One-off win or compounding asset: a shortlist for this decision only, or a scorecard the team re-runs every portfolio review?
• What is the effort ceiling on the analysis itself - analyst hours available, whose data you can request, whose sign-off you can spend?

Those last three re-order the method choices in Brainstorming the ranking, so ask them before proposing any criteria set.

• A near-term date promotes the speed-to-first-value criteria set and staged gates.
• A compounding mandate promotes the complementarity-led set and segmented weights that survive re-use.
• An effort ceiling under about a day removes the scorecard entirely - rank on gates plus effort-to-first-value and say that is what you did.
• The goal answer carries the same weight: a product-gap or market-entry goal reserves capacity for a deep co-innovation candidate that value-per-effort would otherwise starve.

Workflow

Every method choice - criteria set, weight distribution, gate strictness, where the capacity line falls - is ranked with its trade-off in Brainstorming the ranking. Open the relevant menu at the step that needs it, put its default and the runner-up to the user, and wait. Never let an assumption harden into the ranking unstated.

1. Run the Interview. Confirm the input is two or more named candidates and one stated strategic goal.
2. Fix the capacity number before scoring anything. A ranking without a cut line decides nothing - every candidate just gets a flattering ordinal.
3. Pre-filter each candidate with the ally-versus-acquire-versus-build test (Dyer, Kale & Singh, 2004): confirm an alliance is even the right mode for the synergy sought. Wrong-mode candidates leave the list here.
4. Run the must-pass gates, staged by default - desk checks across the whole longlist, expensive reviews on survivors only: financial viability, security/compliance posture, legal exposure, brand safety for B2C, and the Gomes-Casseres three-laws screen. A gate failure removes the candidate - a strong logo can never buy its way past a gate. See references/risk-and-dependency-screens.md.
5. Build the scorecard for survivors: criteria anchored on resource complementarity and organizational compatibility, weights individually justified in writing, never default-equal. Use account-overlap data as one capped input, not the ranking spine. See references/scoring-criteria-and-weights.md.
6. Score effort alongside value: integration cost, enablement load, alliance-manager hours. Rank candidates on value ÷ effort > value composite > logo attractiveness - say that ordering in the memo, because the value column alone is what the room will read otherwise.
7. Score risk explicitly per candidate: relational vs performance risk (Das & Teng), co-innovation and adoption-chain risk (Adner's Wide Lens), and platform-envelopment risk for any candidate whose platform you would build on (Eisenmann, Parker & Van Alstyne).
8. Run the sensitivity analysis: shift each weight ±20% and re-rank. Report which rank positions survive and which flip - a ranking that only holds under one weight set is an opinion wearing a spreadsheet.
9. Draw the capacity line where the summed effort estimates exhaust available alliance-manager months, falling back to the raw headcount number when candidate efforts are comparable. Spend any co-innovation slot reserved before scoring inside that budget, never on top of it - see What the ordering starves. Everything above the line is the shortlist; everything below gets an explicit verdict - hold, recycle, or kill - with a re-entry trigger.
10. Draft a light business case per shortlisted candidate: joint value hypothesis, first-value milestone, effort estimate, risk summary. Deep unit economics hand off to the economics sibling.
11. Where both sides can be convened, pressure-test the top candidates in a joint value proposition workshop; a candidate that cannot articulate joint customer value fails here regardless of score. See references/gates-and-governance.md.
12. Present the deliverable section by section - gates, scorecard, ranking, sensitivity, shortlist, verdicts - and validate each with the user before drafting the next. Revise on pushback.
13. Issue go/no-go verdicts per candidate - go, conditional-go, recycle, hold, kill - and require explicit user approval of the full memo before finalizing.
14. Check the pass threshold below; iterate the criteria, weights, or gates until every check holds.
15. Set the portfolio review cadence and re-ranking triggers: a candidate's acquisition, a platform policy change, a gate-milestone slip, a new entrant. Rankings decay; date the next review.
16. If your harness has persistent memory, memorize the approved ranking, the weights and their justifications, and each go/no-go verdict so later runs and portfolio reviews start from them.
17. If you can browse the web, verify each candidate's current state - ownership, funding, platform policies, recent incidents - before finalizing; stale candidate facts are a leading cause of dead-on-arrival shortlists. Otherwise flag candidate facts as user-supplied and unverified.

Brainstorming the ranking

Enter brainstorming mode before scoring anything - never open with a finished table. Run it the way alliance teams actually run candidate selection: a gated debate, not a single answer.