Developed by Jennifer Kemeny (The Fifth Discipline Fieldbook, 1994) and later set out by Daniel H. Kim and Virginia Anderson (Systems Archetype Basics, 1998).
Describes how two allies each make moves that make sense locally but undercut the other, read the shortfall as bad faith, and pull back further.
Sales and operations: a partnership that grows both, and two local fixes that turn them into adversaries
R1 is the partnership: sales shares forecasts, which lift the plant's margin, and the plant holds capacity for sales' deals, which lifts quota. B1 and B2 are each side's fix for its own shortfall, and their side effects join into R2, which runs the partnership backward. Play the year with sales discounting hard: both results slide. Set the discounting to zero and replay: R1 takes over and both grow. Illustrative.
Quota attained, %
Operations margin, %
Month 12 of 12
- Quota attained, %
- 80.3
- Operations margin, %
- 16.4
- Discount, points
- 7.4
- Order rules, strictness
- 7.5
- Forecasts shared, 0 to 10
- 4.1
- Capacity held, 0 to 10
- 3.6
- R1, Partnership
- Sales doing well shares better forecasts, which lift the plant's margin, and a healthy plant holds capacity for sales: each side's success feeds the other's. No negative (−) links: an even count, so the loop reinforces.
- B1, Sales' fix
- Short of quota, sales discounts and promises rush orders, which closes deals and lifts quota. It works for sales. One negative (−) link: an odd count, so the loop balances.
- B2, Operations' fix
- Short of margin, the plant tightens its order rules, which cuts the costly orders and lifts margin. It works for the plant. One negative (−) link: an odd count, so the loop balances.
- R2, Accidental adversaries
- Sales' discounts cut the plant's margin, the plant's rules then lose sales' deals, and sales discounts more. Four negative (−) links: an even count, so the loop reinforces. Four negative (−) links: an even count, so the loop reinforces.
- Sales quota attained
- Share of quota sales closes each month: 90% in January.
- Operations margin
- Plant margin on what ships: 20% in January.
- Forecasts shared
- Sales' help to the plant: early, honest forecasts of what will ship. Sales shares more when it is hitting its numbers.
- Capacity held for sales
- The plant's help to sales: slots kept open for sales' best deals. The plant holds more when its margin is healthy.
- Discounts, rush orders
- Sales' own fix when it is short of quota: deeper discounts and promises of rush delivery.
- Order rules, lead times
- Operations' own fix when margin slips: minimum order sizes, longer lead times, no rush orders without approval.
An example
At an industrial parts maker, sales and the plant had been allies: sales brought in volume, the plant built it at a good margin, and both were paid on profitable growth. Then a soft quarter left sales short of quota, and the regional managers did the sensible thing for sales: deeper discounts and promises of rush delivery to close deals. Rush orders broke the plant's schedule and the discounts thinned its margin, so the plant did the sensible thing for the plant: minimum order sizes, longer quoted lead times, and no rush order without the plant manager's approval. The new rules lost deals, and sales discounted more.
By autumn each side described the other as working against it. The general manager put both teams in a room and drew the four arrows. Neither side's fix was wrong on its own; together they made one loop that was costing both. They agreed a joint rule: rush orders priced at the real cost of the overtime, discounts above five points approved by both, and one monthly forecast built together.
Why it works
Two partners each have a problem of their own, and each fixes it in the way that makes sense locally. Each fix lands on the partner: one side's discount is the other's lost margin, and the other's protective rule is the first side's lost deal. Each sees only its own fix and the damage done to it, and reads the damage as bad faith.
The archetype makes the hidden link visible. Each local fix is a balancing loop that works for its owner, and the two connect through their side effects into a reinforcing loop that hurts both. Stopping either fix halts the slide, but usually only a shared look at the whole structure gets either side to stop. The way out is to name the pattern together, return to the shared interest, and agree on fixes that do not land on the partner.
The thinking behind it
Jennifer Kemeny Jennifer Kemeny, a consultant with Innovation Associates, described the archetype in Accidental Adversaries: When Friends Become Foes (The Systems Thinker, 1994) and in The Fifth Discipline Fieldbook of the same year. It was first recognized in the alliance between Procter and Gamble and Walmart: two parties who could gain from cooperating each take actions to fix their own problems that unintentionally hurt the other, and the alliance turns hostile.
Daniel H. Kim Daniel H. Kim and Virginia Anderson set the archetype out as a practical template in Systems Archetype Basics: From Story to Structure (1998), a Pegasus Communications workbook that teaches each of the archetypes of The Fifth Discipline through worked stories and causal loop diagrams. Kim's guides and his articles in The Systems Thinker made archetypes like this one into diagnostic tools a team can draw for its own situation.
How to run it
- Confirm the shared interest. Write down what both parties want; if they do not want the same result, this is a different problem.
- Map each side's own fix. What each does when its own results fall short, in its own words.
- Draw where each fix lands. Trace each fix's effect on the partner's results; that arrow is usually the one nobody has drawn.
- Close the loop. Show that the damage to each partner prompts more of its own fix, which does more damage.
- Name the pattern together. In one room, with the drawing, so each side sees its own fix as part of the loop.
- Agree fixes that do not land on the partner. Price the costly requests, share the forecast, or approve the risky moves jointly.
- Set a regular cross-check. A monthly look at each side's effect on the other catches the next locally sensible move early.
Where it goes wrong
The pattern gets read as a personality clash. Leaders replace the sales director or the plant manager, and the successors make the same moves, because the incentives are the same. Look for the structure before looking for the culprit.
One side is asked to stop and the other is not. A truce that only the plant honors leaves the plant absorbing every discount. Agree the changes in pairs, so each side gives something the other can see.
The shared interest is assumed. Some partnerships really have diverged (a supplier that no longer needs the account, a team whose goal changed), and drawing loops will not fix that. Check the shared interest first, as the first step says.
When to use something else
- Escalation Archetype. When the two parties are rivals, each answering the other's threat, not allies hurting each other by accident.
- Interest-Based Bargaining. When the parties already see the conflict and need a method for building terms from what each needs.
- Causal Loop Diagram. When the situation does not fit a known archetype and the loops have to be drawn from scratch.
Where it sits in SOLVE eX
Go to the source
- Accidental Adversaries, The Fifth Discipline Fieldbook (Senge, Kleiner, Roberts, Ross, and Smith, eds.), Doubleday, 1994
- Systems Archetype Basics: From Story to Structure, Pegasus Communications, 1998