Site mark: two outlined blocks sharing a hatched overlap
Wave2 Alliances

A reference on how organisations work together

Section strip showing two outlined blocks with a hatched shared area

Wave2 Alliances › Making them work

Why partnerships fail

Most partnerships do not end in a dispute. They end in inattention: nobody decides to stop, and eventually there is nothing left to stop.

Failure is rarely dramatic

The failures people expect are the loud ones — a breach, a disagreement over money, a party behaving badly. Those happen, and they are the minority. The common ending is quieter. Joint activity thins. Meetings are rescheduled and then not rebooked. The people who cared about it move on. Two years later somebody notices the arrangement is still technically in force and nobody can name anything it produced.

Because this ending is undramatic, it is rarely examined, and organisations repeat it. The patterns below recur often enough to be worth recognising early, when they are still cheap to correct.

Asymmetric effort

One side does most of the work. Sometimes that reflects the deal and is fine; the trouble comes when it does not, and when the imbalance is never named. The party doing more grows resentful and reduces its effort to match, and the other side reads that reduction as disengagement rather than as a response.

The correction is not fairness for its own sake. It is being explicit at the outset about who is expected to do more and why — often the larger party, or the one with more to gain — so that a lopsided distribution of effort is a design decision rather than an accumulating grievance.

The unowned middle

The most common structural fault is work that sits between the parties and belongs to neither. Following up the people who attended a joint event. Answering a question that requires both products to be understood. Fixing the join between two systems when it is unclear which side broke.

Each party assumes the other has it. Neither does. The work does not get done, the arrangement produces nothing, and both sides conclude the other was not serious. Naming an owner for every piece of joint work — including the unglamorous middle — prevents more failures than any other single practice.

Arrangements are usually the project of specific people. When those people move, the arrangement loses its advocate inside an organisation that was never entirely convinced. It does not get cancelled; it simply stops appearing in anyone's objectives.

This is survivable if the arrangement has been embedded — if it appears in plans, if operating staff on both sides have relationships of their own, if something concrete depends on it. Arrangements that live only in the relationship between two senior people are extremely fragile and should be recognised as such while both are still in post.

Conflict with the parties' own operations

A partnership frequently competes with something inside one of the parties: a direct sales team paid on deals the partner might have won, an internal team building what the partner supplies, a region that would rather serve the market itself.

Where incentives point away from the partnership, the partnership loses. Not through opposition, but through a hundred small choices about which deal to work on. No amount of governance overcomes a compensation scheme, which is why the effective fix is nearly always to change how people are measured rather than to insist harder.

Scope drift and mismatched motives

Scope drift is expansion by agreement, one reasonable step at a time, until the arrangement covers far more than either party resourced. The symptom is a partnership with a long list of workstreams and no visible output on any of them.

Mismatched motives are subtler and more terminal. Each side wanted a different thing, both were happy to sign because the words covered both readings, and the difference only surfaces at the first real decision. One side wanted capacity; the other wanted to learn how to do it themselves. Both statements are compatible with the document, and the arrangement cannot serve both.

What actually prevents it

The preventative measures are unremarkable, which is why they are skipped. Write the motive down, in both parties' words, and check they match. Start narrow. Name an owner for every piece of joint work, especially the shared middle. Check where the incentives point before assuming cooperation. Review honestly, including the question of whether to stop. Treat a clean ending as a good outcome rather than an admission.

None of these are hard. They are just unpopular during the period when everyone is enthusiastic, which is exactly when they must be done.

Where this leads

These patterns are not new. The same difficulties appear in cooperative trading arrangements going back several centuries, along with the same partial solutions.

Sections of this site

Each section is a standalone explanation. Nothing here assumes you have read the pages before it.