Influence & Persuasion · Part 3 of 7

Escalation of Commitment: Why Teams Keep Funding the Failing Project

Argumentree Team10 min
Escalation of Commitment: Why Teams Keep Funding the Failing Project

Escalation of Commitment: Why Teams Keep Funding the Failing Project

Escalation of commitment is the tendency to increase investment in a failing course of action across a series of decisions. Barry Staw demonstrated it experimentally in 1976 (Knee-deep in the Big Muddy, Organizational Behavior and Human Performance 16, 27–44): 240 business students played a financial vice-president allocating ten million dollars of R&D funding between two divisions, then allocated a further twenty million after seeing results. The design crossed personal responsibility with outcome. Participants who had personally chosen the division that then performed badly allocated an average of 13.07 million dollars to it, roughly half again as much as every other condition, which clustered around nine million; the responsibility-by-consequences interaction was significant at F(1,235) = 5.56, p < .019. The finding is not that failure causes escalation but that being personally responsible for the failure does. Staw later defined the phenomenon by its structure rather than its psychology (The Escalation of Commitment to a Course of Action, Academy of Management Review 6(4), 1981): a salient feature of escalation is that a series of decisions is associated with a course of action rather than an isolated choice, which is what distinguishes it from the sunk-cost fallacy, a single-decision error. The mechanism is Cialdini's commitment-and-consistency principle operating at organisational scale, and its smaller sibling is the foot-in-the-door effect demonstrated by Freedman and Fraser in 1966. The best-documented real-world case is Expo 86 in Vancouver, where Ross and Staw recorded projected losses rising from six million dollars in 1978 to over three hundred million in 1985 while the provincial government remained committed. The 2012 meta-analysis by Sleesman, Conlon, McNamara and Miles, covering 166 independent samples, found personal responsibility and sunk costs to be comparable drivers and noted that the prominence of sunk costs was lower than expected, meaning the common advice to ignore sunk costs addresses only part of the problem. The structural defence is to separate the decision from the decider's history: record the original reasoning, review projects against the case rather than the champion, and make the exit criteria explicit before the money is committed.

Share:

Same failing division, same numbers, two very different answers

The case was called A&S Financial. Adams & Smith Company, a technology firm in decline, ten years of sales and earnings on the page, and one job: you are the financial vice-president, allocate ten million dollars of R&D funding between the Consumer Products and Industrial Products divisions. Five years later — in the case's time, minutes in the room — a second decision: another twenty million from capital reserve.

Barry Staw ran 240 undergraduates from the University of Illinois through it in a two-by-two design, published as Knee-deep in the Big Muddy in Organizational Behavior and Human Performance in 1976. Half the participants made both allocations themselves; the other half were told a predecessor had made the first one. Independently, the chosen division either improved or declined.

Three of the four groups behaved sensibly, allocating somewhere around nine million to the division they had watched struggle. The fourth group — the people who had picked that division themselves and then watched it fail — allocated an average of $13.07 million. The interaction was significant (F(1,235) = 5.56, p < .019), and it is the whole point. Bad news alone did not produce throwing good money after bad. Bad news about your own decision did.

The small yes that buys the large one

The mechanism has a well-documented smaller sibling. In 1966 Jonathan Freedman and Scott Fraser published Compliance without pressure: the foot-in-the-door technique in the Journal of Personality and Social Psychology. In their second experiment, researchers asked Californian homeowners to do something trivial — sign a petition, or display a small sign about safe driving. Two weeks later a different person asked the same households to install a large, deliberately ugly DRIVE CAREFULLY billboard on the front lawn.

The control group, asked only once, agreed at 16.7 per cent. The households that had earlier accepted the small, same-issue request agreed at 76 per cent. In the authors' own summary of the pattern:

Whereas fewer than 20% of the controls agreed to put the large sign on their lawn, over 55% of the experimental subjects agreed, with over 45% being the lowest degree of compliance for any experimental condition.
— Freedman & Fraser, Journal of Personality and Social Psychology (1966)
Note the honest framing: 76 per cent is the best cell, not the average — the reliable headline is that a prior small commitment roughly tripled compliance. Now scale it. A pilot budget is a small sign. The steering committee that approved it has taken a public position, and the next request does not arrive to a neutral audience.

What it looks like when it is not a lab

The best-documented organisational case is a world's fair. Jeffrey Ross and Barry Staw studied Expo 86 in Vancouver and published it in Administrative Science Quarterly in 1986 as an escalation prototype. The projected loss did not creep; it multiplied — and the commitment held anyway.

Despite rapidly increasing deficit projections (from a 6-million projected loss in 1978 to over a 300-million projected loss in 1985), the provincial government remained steadfast in its plans to hold Expo.
— Ross & Staw, Administrative Science Quarterly (1986)

Fifty-fold worse, and still going. That is not stupidity, and reading it as stupidity is why organisations keep reproducing it. Every individual decision along that path had a defensible case attached — and each one was being made by people who had already publicly backed the last one.

But isn't this just the sunk-cost fallacy?

This is the objection worth taking seriously, because the two are constantly used as synonyms and they are not. Staw drew the line himself in the Academy of Management Review in 1981:

A salient feature of the preceding case examples is that a series of decisions is associated with a course of action rather than an isolated choice.
— Barry M. Staw, Academy of Management Review (1981)

Sunk cost is a single-decision error: counting money you cannot recover. Escalation is an organisational pattern across a sequence of decisions, in which sunk cost is one driver among several — self-justification, ego threat, agency problems, group cohesion. And the evidence supports that distinction in an uncomfortable way. The 2012 meta-analysis by Sleesman, Conlon, McNamara and Miles in the Academy of Management Journal, covering 166 independent samples drawn from an initial pool of 917 articles, found personal responsibility (ρ = .258) and sunk costs (ρ = .243) to be comparable in size — and the authors noted that the prominence of sunk costs was lower than expected.

Why the usual advice underperforms

"Ignore sunk costs" is aimed at an accounting error. But the strongest pull in the data is not the money already spent — it is the person who spent it needing the decision to have been right. A review process that fixes the arithmetic and leaves the authorship untouched has fixed the smaller half.

The technique: separate the decision from its author

None of this is solved by telling people to be more objective about their own record. It is solved by arranging the review so the record is not on trial.

  • Write the exit criteria before the money moves. "We stop if X by date Y" is cheap to agree while nobody owns the outcome, and nearly impossible to agree once someone does. This is the single highest-leverage move available.
  • Review the case, not the champion. Re-read the original argument tree as written — the claims, the evidence, the assumptions — and ask whether it would be approved today by someone seeing it for the first time. The decision record makes that a document review instead of a personality contest.
  • Rotate who presents the continue-or-kill case. If the person who owns the project also frames its review, the interaction Staw isolated is built into your process by design.
  • Make opportunity cost visible. The meta-analysis identifies de-escalating conditions — among them anticipated regret, explicit opportunity-cost information, and actively acquiring new information. "What else could this quarter's budget buy?" is not rhetoric; it is a documented lever.
  • Separate the person from the position on the record. Rating arguments rather than people means a champion can concede a claim without conceding their judgment — which is the concession escalation actually blocks.

Knee-deep, and the water is rising

Staw took his title from a Pete Seeger song about a captain who marches his platoon deeper into a river, insisting they push on. It is a good image precisely because the captain is not stupid. He has said out loud that this is the way, other people are watching, and turning back means the first announcement was wrong.

Your organisation will fund a failing project again. The question is whether that decision gets made by a room reading the case, or by the room's memory of who signed it — because in Staw's data, the same numbers produced two completely different answers depending on nothing more than that.

Sources &amp; further reading

Every named source in this post, with a link where one exists.

Frequently Asked Questions

What is escalation of commitment?

The tendency to increase investment in a failing course of action across a series of decisions, rather than reverse it. Barry Staw introduced the term in 1976 and defined it structurally in 1981: what distinguishes escalation from an ordinary bad choice is that a series of decisions is attached to a course of action rather than an isolated one. In organisations it looks like additional budget, headcount or time committed to a project whose own evidence has turned against it.

Is escalation of commitment the same as the sunk-cost fallacy?

No, though they overlap. The sunk-cost fallacy is a single-decision error: letting unrecoverable past spending influence a present choice. Escalation of commitment is an organisational pattern across a sequence of decisions, driven by sunk costs plus self-justification, ego threat, agency problems and group cohesion. Sunk cost is one input; escalation is the system-level outcome.

What did Staw's 1976 experiment actually find?

That authorship of a failure, not the failure itself, predicts throwing more money at it. 240 business students allocated R&D funding to a division, then allocated more after seeing results. Participants who had personally chosen the division that subsequently declined allocated an average of $13.07 million to it; the other three conditions clustered around $9 million. The responsibility-by-consequences interaction was significant at F(1,235) = 5.56, p < .019.

Does the research still hold up?

Yes, at moderate effect sizes. The 2012 meta-analysis by Sleesman, Conlon, McNamara and Miles in the Academy of Management Journal covered 166 independent samples and found personal responsibility (ρ = .258) and sunk costs (ρ = .243) to be comparable drivers, alongside factors including ego threat and group cohesion. Notably the authors observed that the prominence of sunk costs was lower than expected — a caution against treating sunk cost as the whole explanation.

How is this related to Cialdini's principles of influence?

It is commitment and consistency operating at organisational scale. Cialdini's principle says that once we take a position, especially publicly, we defend it; the foot-in-the-door studies show a small prior commitment substantially raising compliance with a larger later request. Escalation is what that looks like when the commitments are budgets and the audience is a steering committee.

What actually reduces escalation in practice?

Arrangements that keep the review from becoming a referendum on the champion. Write explicit exit criteria before funds are committed, review the recorded case rather than the person defending it, rotate who presents the continue-or-kill recommendation, and make opportunity cost explicit — the meta-analysis identifies anticipated regret, opportunity-cost information and active information acquisition among the de-escalating conditions.

Is Expo 86 a fair example, given it was a government project?

It is one of the few cases documented longitudinally in a peer-reviewed venue, which is exactly why it is used here rather than the more colourful business anecdotes that circulate without traceable sources. Ross and Staw recorded projected losses rising from $6 million in 1978 to over $300 million by 1985 with commitment intact. The mechanism they describe — public position, personal responsibility, institutional momentum — is not specific to the public sector.

Make the case defensible, not the decider

Record the reasoning when the project is approved, and the review a year later reads a document instead of judging a colleague.

Start Free — No Credit Card

Free forever for individuals

Related Articles