Red Queen Effect

Thinking Tools3.4 Facts About the FutureAlso known as Red Queen Hypothesis

From evolutionary biology, named by Leigh Van Valen (A New Evolutionary Law, 1973) and popularized by Matt Ridley (The Red Queen, 1993), and carried into business by William P. Barnett and Morten T. Hansen (The Red Queen in Organizational Evolution, 1996).

Explains why, among rivals who keep improving, a firm that stops adapting loses ground even as its own capability holds steady, and treats improvement as a standing cost.

The bank's app gets better every year and still falls behind, because rivals get better faster

A regional bank's mobile app against its rivals', both scored 100 today. Select R1 to light the race, then set how fast the bank improves and how fast the rivals do, and play ten years: the bank's own capability rises at any setting above zero, but its lead over the rivals falls below zero whenever it improves more slowly, and at zero it loses ground every year. Illustrative.

Select a loop to trace it, or a box to read it.R1, The race. Every gain by one side raises the bar for the other, so both keep improving and neither pulls ahead for long. No negative (−) links: an even count, so the loop reinforces.Our app's capability. Features, speed, and reliability of the bank's app, scored 100 today.Pressure on rivals. Each gain the bank makes raises the bar the rivals' customers compare against.Rivals' capability. The average score of the three apps customers most often switch to, also 100 today.Pressure on us. Each rival gain raises the bar the bank's own customers compare against.Our position. How far the bank's score sits above or below the rivals', in percent: zero means level, below zero means behind.
3%
5%

Our app's capability

0: 1001: 1032: 1063: 1094: 1135: 1166: 1197: 1238: 1279: 13010: 1340501001502000123456789100: 1001: 1032: 1063: 1094: 1135: 1166: 1197: 1238: 1279: 13010: 134050100150200012345678910

Our lead over the rivals, in percent (below zero is behind)

0: 01: −22: −43: −64: −75: −96: −117: −138: −149: −1610: −17−500501000123456789100: 01: −22: −43: −64: −75: −96: −117: −138: −149: −1610: −17−50050100012345678910

Year 10 of 10

Our app's capability
134
Our lead over the rivals, in percent (below zero is behind)
−17

R1, The race
Every gain by one side raises the bar for the other, so both keep improving and neither pulls ahead for long. No negative (−) links: an even count, so the loop reinforces.
Our app's capability
Features, speed, and reliability of the bank's app, scored 100 today.
Pressure on rivals
Each gain the bank makes raises the bar the rivals' customers compare against.
Rivals' capability
The average score of the three apps customers most often switch to, also 100 today.
Pressure on us
Each rival gain raises the bar the bank's own customers compare against.
Our position
How far the bank's score sits above or below the rivals', in percent: zero means level, below zero means behind.

An example

A regional bank had invested steadily in its mobile app for four years, and every internal score said it was better than the year before: faster logins, more features, fewer crashes. The board's question was why customers kept leaving for other banks.

The head of digital stopped reporting the app's score on its own and put it beside the average score of the three apps customers most often switched to. The bank's app had improved about 3 percent a year; the rivals' apps had improved about 5. On its own scale the app was well ahead of where it started. Against the field it had lost ground every year, and on the same trend it would sit about a sixth behind in ten years. The board changed how it budgets: holding position became a recurring line set at the rivals' pace, and anything beyond that pace was funded as growth, with a case of its own.

Why it works

Customers judge capability against the alternatives on offer, and last year's version of the product is not one of them. A firm can improve on every internal measure and still lose position, because position is a ratio and the rivals are moving the bottom half of it. The Red Queen effect is that ratio under competition: each side's improvement raises the bar for the other, so both keep running and neither stays ahead for long.

Two consequences follow. Standing still is never neutral; where rivals improve, it is a steady decline. And part of what a firm spends on improvement is the cost of staying in the race, as unavoidable as rent. Budgeted that way, it is harder to cut in a lean year on the belief that the firm is only pausing.

The thinking behind it

Leigh Van Valen Leigh Van Valen, an evolutionary biologist at the University of Chicago, published A New Evolutionary Law in the journal Evolutionary Theory (1973). He found that a group's probability of extinction stays roughly constant over time, however long the group has already lasted. His explanation, the Red Queen hypothesis, is that species coevolve: each one's gains worsen the conditions of the species it competes with, so every species must keep evolving just to hold its place.

William P. Barnett William P. Barnett, a professor at the Stanford Graduate School of Business, carried the biologists' idea into organization theory with Morten T. Hansen in The Red Queen in Organizational Evolution (Strategic Management Journal, 1996). In their account, competition prompts a firm to learn, its learning raises the bar for its rivals, and their learning in turn raises it again, so competition and learning escalate together. Barnett extended the argument in The Red Queen among Organizations (2008).

How to run it

  1. Pick the measure customers compare. Use the capability buyers actually weigh when they choose, such as delivery time or app ratings.
  2. Score the rivals on the same measure. Track the two or three alternatives customers most often switch to; the whole market blurs the picture.
  3. Report position as a ratio. Show the firm's score divided by the rivals', so improvement that only matches the field reads as flat.
  4. Measure the field's pace. Estimate how fast the rivals have improved over several years; that pace is the cost of standing still.
  5. Budget holding position as a recurring cost. Fund improvement at the rivals' pace every year, as a standing line.
  6. Fund gains beyond it separately. Anything above the field's pace is a growth bet and needs its own case.
  7. Recheck when the field changes. A new entrant or a shift in technology can raise the pace in a single year.

Where it goes wrong

The first failure is measuring progress against the firm's own past. The trend line climbs, the team celebrates, and the loss of position shows up only as customers leaving. Put the rivals on the same chart before anyone reads the trend.

A second failure is cutting the holding budget in a lean year and calling it a pause. Where the field keeps improving, a year of standing still is a year of decline, and catching up later costs more than keeping pace. Name the holding line in the budget so it is seen for what it is. The third is assuming every field runs this race. Some improve slowly or not at all; check that rivals are really moving before funding a race that is not on.

When to use something else

  • Technology S-Curve. When the question is whether the technology itself is near its limit, so the race is about to move to a new curve.
  • Porter's Five Forces. When the pressure comes from the structure of the industry, buyers and suppliers included, beyond the rivals' pace.
  • Escalation Archetype. When two sides are matching each other's moves in a spiral neither wants, such as a price or feature war.

Where it sits in SOLVE eX

Go to the source

  • A New Evolutionary Law, Evolutionary Theory 1, 1973
  • The Red Queen: Sex and the Evolution of Human Nature, 1993
  • The Red Queen in Organizational Evolution, Strategic Management Journal 17, 1996

Back to the catalog