In short
Escalation of commitment is the pattern in which a person or an organization responds to bad news about a course of action they chose by committing more time, money or effort to it, rather than less, so that the first decision can still turn out to have been right. It shows up in projects that get a third round of funding after missing every milestone, wars that continue because of the casualties already suffered, software rewrites that nobody will cancel, and careers and relationships that are kept going chiefly because of the years already in them.
How escalation of commitment works
A decision maker who learns that a chosen course is failing has two ways to make the news bearable: stop, and accept that the first decision was wrong, or continue, and keep open the possibility that it was right. Escalation of commitment is the second route, and the explanation Staw proposed for it is self-justification. Having chosen publicly, and often having argued for the choice, the person is motivated to show that it was sound, and the clearest way to show that is to make it succeed. More resources go in, and the stake that needs justifying grows with them.
Staw's design separated this motive from the plain economics of the case. Every student in the 1976 experiment saw the same financial data for the second decision; what varied was whether the first decision had been theirs. Those who owned a failing choice gave it the most money. Those who inherited the same failing choice from a predecessor did not. The numbers alone could not produce that gap, because the numbers were the same.
Later accounts added other engines. Brockner's 1992 review set self-justification alongside three more: the way prospect theory predicts people will gamble to avoid a sure loss once they are in the domain of losses, the pull of a decision rule that says to finish what has been started, and the fear of how others will judge a public reversal. Staw's own 1981 review added the organizational layer, where a project acquires defenders whose reputations depend on it and where stopping becomes a political act. Sleesman and colleagues' 2012 meta-analysis of the laboratory literature found that no single factor explains escalation; the sunk costs already incurred, how close a project is to completion, and the decision maker's personal responsibility for the original choice all push in the same direction, among many others.
How large the responsibility effect is on its own is a fair question. Staw's result rested on one cell of a two-by-two design, and later studies have found it in some settings and not others. The meta-analytic picture is that personal responsibility is one real determinant among several, and that features of the project often matter as much as who chose it.
The original study
Barry Staw published "Knee-deep in the big muddy: A study of escalating commitment to a chosen course of action" in Organizational Behavior and Human Performance in 1976.
The participants were 240 undergraduate business students at the University of Illinois. Each worked on the "A and S Financial Decision Case," which described the Adams and Smith Company in 1967, a large technology firm whose profits had been slipping. The case asked the student, as financial vice president, to put 10 million dollars of extra research funding into one of two divisions, Consumer Products or Industrial Products, and to write a paragraph defending the choice. A second part of the case then moved to 1972 and gave five years of sales and earnings figures for both divisions. This time 20 million dollars was available and could be split in any proportion. The amount given to the previously chosen division was the measure of commitment.
Two things were manipulated. Half of the students saw figures showing that the chosen division had deteriorated while the other recovered; half saw the reverse. And half of the students made the first decision themselves, while the other half received only the 1972 part of the case and were told that an earlier financial officer had made the 1967 choice. That produced four groups of 60.
Students who had made the choice themselves gave the previously chosen division 11.08 million on average; students who inherited the choice gave it 8.89 million. Negative results drew more money than positive ones, 11.20 million against 8.77. The important finding was the interaction: students who had made the choice personally and then watched it fail allocated 13.07 million to the failing division, and that group was the only one that differed significantly from the other three. Owning a bad decision, not merely seeing one, was what moved the money.
Read the diagram and evidence as text
A chooser’s circular badge stays on the selected division. A downward arrow on a result sheet feeds a returning money path to that same division. The new allocation is labeled $13.07 million from a $20 million pool. Geometry is illustrative and does not encode a financial time series or an increase over the initial allocation.
Bad news about your own decision
Millions of a new 20 million dollars; amounts are labels, not bars
The first choice was yours: You put the research money into one division and defended the choice
The division declines: Your division deteriorated while the other recovered
More money to the same division: 13.07 million of the new 20 million, on average
If a predecessor had chosen: Across all conditions, 8.89 million went to that division, against 11.08 million when the first choice was the student's own
The first choice was yours → the results come in → The division declines
The division declines → put more in, so the first choice can still turn out right → More money to the same division (error transition)
The division declines → the same case, but a predecessor chose → If a predecessor had chosen
| Condition | Value and unit | Evidence quote |
|---|---|---|
| All participants | 240 business students | 240 business students |
| New funds available to split | 20 million dollars | of a new 20 million dollars |
| Chose the division personally; it then declined (60 students) | 13.07 million dollars, average | the 60 who had personally chosen a division that then declined allocated an average of 13.07 million of a new 20 million dollars to that same division |
| Made the first choice themselves, all conditions | 11.08 million dollars, average | students who had made the first choice themselves gave the previously chosen division 11.08 million |
| Predecessor made the first choice, all conditions | 8.89 million dollars, average | against 8.89 million when the case said a predecessor had chosen it |
Everyday examples
Escalation needs three things: a decision somebody owns, bad news about it, and a chance to put more in. The rows below are illustrations, not findings from the studies cited on this page.

| Situation | What the bias does | What helps |
|---|---|---|
| A product launch misses every target for a year | The executive who championed it asks for a bigger marketing budget rather than a review | Set the kill criteria in writing before launch, and have someone who did not choose the project judge them |
| A software rewrite is two years late | The team adds staff because stopping now would waste the work already done | Ask what you would do if the project were proposed fresh today with the money that is left |
| A hiring manager's pick is struggling at six months | The manager extends the probation and gives extra coaching that nobody else would get | Have a colleague who was not on the hiring panel review the performance record |
| A government keeps funding a stalled infrastructure project | Each new overrun is approved because of the billions already spent and the ministers who announced it | Separate the people who review a project from the people who approved it |
| An investor adds to a losing position | Buying more at a lower price feels like proving the original thesis right | Decide the exit rule when buying, and treat the position as a fresh purchase each time |
How to counter it
The strongest counter follows directly from Staw's design: the people who inherited a decision did not escalate it. Separating the person who judges a project from the person who chose it removes the motive to justify.
- Write the stopping rule down before the project starts: the date, the milestone or the budget at which it will be reviewed as if new, and who will do the review.
- Rotate the reviewer. A manager who did not pick the vendor, the hire or the strategy can read the numbers without needing them to come out one way.
- Ask the predecessor question from the demo. If you had just taken over and found this project on your desk, with these results and this much money left, what would you do?
- Reframe the sunk costs as gone. Money and time already spent do not come back under either option, so they belong in neither column of the decision.
- Make reversal cheap in advance. Teams that are praised for stopping a failing project early have less to defend than teams for whom a cancellation is a public verdict.
- Notice the words. Turnaround, momentum, so close, and too much invested to quit are all sentences about the past dressed as sentences about the future.
What it is not
Escalation of commitment is the sequence: a decision, bad news, and a further commitment that defends the decision. Its neighbors share pieces of that sequence.
- It is not the sunk cost fallacy, which is one decision made badly because costs already spent are counted as if they could be recovered. Sunk cost reasoning is one cause of escalation; escalation also runs on reputation, public commitment and the wish not to have been wrong, and it unfolds over repeated decisions.
- It is not irrational escalation, the competitive version that the dollar auction illustrates, where each bid is made to avoid losing the last one to a rival. Staw's students had no opponent; they were defending themselves against their own earlier choice.
- It is not status quo bias, the general preference for the current state over a change. Escalation is more active than inertia: the person does not merely keep a project, they feed it.
- It is not choice-supportive bias, the tendency to remember a past choice as better than it was. That is a distortion of memory; escalation is a distortion of the next allocation.
Tests and tools that use this
Related biases
Escalation of Commitment FAQ
What is escalation of commitment?
It is the tendency to respond to evidence that a chosen course of action is failing by committing more resources to it rather than fewer, so that the original decision can still be vindicated. Barry Staw described it in 1976 after finding that business students who had personally chosen a division that then lost money gave that division far more new funding than students who inherited the same failing choice from a predecessor. Self-justification was his explanation.
What is the difference between escalation of commitment and the sunk cost fallacy?
The sunk cost fallacy is a single decision in which money, time or effort already spent is wrongly counted as a reason to continue. Escalation of commitment is the broader and longer pattern: repeated decisions to invest more in a failing course, driven by sunk costs but also by the wish to justify an earlier choice, by public commitment, and by what a reversal would say about the decision maker. Staw's experiment held the facts constant and varied only who had made the first choice.
How does the demo on this page work?
You chose a division to fund, learned five years later that it had failed while the other recovered, and divided a new 20 million dollars between them. Then you divided the same money as a newcomer whose predecessor had made the first choice. A larger share for the failing division when the choice had been yours counts as the pattern Staw measured; the same split, or a larger share in the predecessor version, does not. Staw compared separate groups; you answered both versions, so this is an illustration.
What did Staw's 1976 study find?
Students who had chosen a division themselves and then seen it decline allocated an average of 13.07 million of 20 million dollars to it, more than students in any of the other three conditions, and that cell was the only one that differed significantly from the others. Across the whole sample, students who made the first choice gave the previously chosen division 11.08 million against 8.89 million when the case said another officer had chosen it, and divisions with negative results drew more money than divisions with positive ones.
Why do people escalate commitment to a failing plan?
Staw's explanation was self-justification: having made and defended a choice, a person wants it to have been right, and more investment keeps that possible. Brockner's 1992 review added the pull toward gambling to avoid a sure loss that prospect theory describes, a rule of finishing what one starts, and concern about how others will judge a reversal. In organizations, Staw argued in 1981, projects acquire defenders whose standing depends on them. The 2012 meta-analysis by Sleesman and colleagues found that sunk costs, closeness to completion and personal responsibility all contribute.
How can organizations prevent escalation of commitment?
The most direct lesson of Staw's design is that people who inherited a decision did not escalate it. Separating project review from project ownership, rotating reviewers, and writing stopping rules before a project starts all use that finding. Framing sunk costs as gone under every option, rewarding early cancellation rather than punishing it, and asking what a newcomer would do with the remaining budget are habits that individual managers can adopt without changing the organization.
References
- Staw, B. M. (1976). Knee-deep in the big muddy: A study of escalating commitment to a chosen course of action. Organizational Behavior and Human Performance, 16(1), 27-44. doi.org
- Brockner, J. (1992). The escalation of commitment to a failing course of action: Toward theoretical progress. Academy of Management Review, 17(1), 39-61. doi.org
- Staw, B. M. (1981). The escalation of commitment to a course of action. Academy of Management Review, 6(4), 577-587. doi.org
- Sleesman, D. J., Conlon, D. E., McNamara, G., & Miles, J. E. (2012). Cleaning up the big muddy: A meta-analytic review of the determinants of escalation of commitment. Academy of Management Journal, 55(3), 541-562. doi.org
- Arkes, H. R., & Blumer, C. (1985). The psychology of sunk cost. Organizational Behavior and Human Decision Processes, 35(1), 124-140. doi.org
Cite this source
Psychology.com. (2026, October 21). Escalation of Commitment. Psychology.com. https://psychology.com/biases/escalation-of-commitment
