Dead Horses and the Escalation of Commitment
Last updated: July 21, 2024 Read in fullscreen view
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 430/2193 - 13 Apr 2024
Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 103/1144 - 02 Nov 2021
What is Terms of Reference (ToR)? 67/1615 - 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 57/1134 - 19 Oct 2021
Software development life cycles 56/729 - 03 Apr 2022
Microsoft Solutions Framework (MSF) 54/1339 - 13 Oct 2021
Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 53/510 - 31 Aug 2022
What are the best practices for software contract negotiations? 46/301 - 13 Dec 2020
Move fast, fail fast, fail-safe 45/355 - 12 Oct 2022
14 Common Reasons Software Projects Fail (And How To Avoid Them) 45/596 - 01 Oct 2020
Fail fast, learn faster with Agile methodology 41/1077 - 06 Feb 2021
Why fail fast and learn fast? 37/487 - 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 36/900 - 02 May 2022
What Is RAID in Project Management? (With Pros and Cons) 34/853 - 18 Aug 2022
What are the consequences of poor requirements with software development projects? 32/289 - 05 Sep 2023
The Cold Start Problem: How to Start and Scale Network Effects 31/220 - 12 Aug 2022
What is End-to-end project management? 30/480 - 07 Jul 2022
Managing Project Execution Terms 29/434 - 18 Dec 2023
The Cone of Uncertainty in Scrum & Requirement Definition 29/729 - 07 Oct 2025
Case Study: Using the “Messaging House” Framework to Build a Digital Transformation Roadmap 28/99 - 04 Oct 2021
Product Validation: The Key to Developing the Best Product Possible 28/331 - 01 Mar 2023
Bug Prioritization - What are the 5 levels of priority? 27/247 - 03 Jan 2023
Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) 27/406 - 23 Jun 2024
Best Practices for Managing Project Escalations 26/226 - 10 Apr 2024
The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 25/508 - 26 Sep 2024
Successful Project Management Techniques You Need to Look Out For 24/414 - 05 Jun 2023
Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 24/160 - 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 24/497 - 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 24/472 - 08 Oct 2022
KPI - The New Leadership 24/616 - 28 Oct 2022
Build Operate Transfer (B.O.T) Model in Software Outsourcing 24/420 - 28 Jul 2022
POC, Prototypes, Pilots and MVP: What Are the Differences? 23/734 - 18 Oct 2021
Key Elements to Ramping Up a Large Team 23/1239 - 28 Dec 2021
8 types of pricing models in software development outsourcing 23/454 - 04 Oct 2022
Which ERP implementation strategy is right for your business? 23/339 - 05 Mar 2021
How do you minimize risks when you outsource software development? 22/343 - 13 Jan 2020
Quiz: Test your understanding project cost management 22/635 - 12 Dec 2021
Zero Sum Games Agile vs. Waterfall Project Management Methods 22/429 - 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 22/444 - 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 22/325 - 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 22/238 - 05 Jan 2024
Easy ASANA tips & tricks for you and your team 22/217 - 20 Jul 2022
Software Myths and Realities 21/927 - 19 Oct 2021
Is gold plating good or bad in project management? 21/840 - 17 Oct 2021
Does Fast Tracking increase project cost? 21/387 - 09 May 2022
Build one to throw away vs Second-system effect: What are differences? 21/331 - 07 Dec 2023
12 project management myths to avoid 20/206 - 02 Nov 2022
Difference between Change Management and Project Management 20/244 - 06 Mar 2024
[SemRush] What Are LSI Keywords & Why They Don‘t Matter 20/198 - 18 Feb 2026
"Hit and Run" Project Management: Balancing Speed with Sustainability 20/33 - 19 Apr 2021
7 Most Common Time-Wasters For Software Development 20/562 - 22 May 2022
What are common mistakes that new or inexperienced managers make? 20/297 - 14 Jun 2022
Example and Excel template of a RACI chart in Software Development 20/849 - 24 Nov 2023
The project management paradox: Achieving MORE by doing LESS 19/236 - 06 Jun 2022
Change Management at the Project Level 19/321 - 02 Dec 2021
3 Ways to Avoid Scope Creep in IT Consulting 18/223 - 27 Jan 2020
Should a project manager push developers to work more hours due to mistakes of manager schedule setting? 18/446 - 18 Jul 2021
How To Ramp Up An Offshore Software Development Team Quickly 18/602 - 31 Oct 2021
Tips to Fail Fast With Outsourcing 17/400 - 01 Dec 2023
Laws of Project Management 17/322 - 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 17/274 - 30 Nov 2023
Project Managers, Focus on Outcomes — Not Deliverables 16/174 - 01 Aug 2022
Is planning "set it and forget it" or "set it and check it"? 16/293 - 12 Mar 2024
How do you create FOMO in software prospects? 16/181 - 10 Jan 2024
Like for Like – how to preserves existing business and leverage technological advancement 15/401 - 12 Aug 2024
Understanding Google Analytics in Mumbai: A Beginner's Guide 14/107 - 01 Mar 2024
10 Project Management Myths 13/156 - 14 Mar 2024
Why should you opt for software localization from a professional agency? 13/149 - 06 Nov 2019
How to Access Software Project Size? 13/259 - 02 Jun 2024
Reviving Ancient Wisdom: The Spiritual Side of Project Management 12/245 - 15 May 2022
20 Common Mistakes Made by New or Inexperienced Project Managers 10/291 - 10 May 2022
Levels of Teamwork 9/202 - 01 May 2024
Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 7/211
Organizational Change Management and Behavioral Economics are two fields that intersect when understanding human behavior in the workplace and I love them both! In this post, I will delve into the intricacies of escalation of commitment bias and discuss how we all can fall victim to entrapment problems. The Escalation of Commitment bias is one of the most critical behavioral biases that can impact technical change management efforts.
Learn more: Best Practices for Managing Project Escalations
The Escalation of Commitment Bias
The Escalation of Commitment bias is the tendency for individuals to continue investing time, resources, and effort into a project or decision based on the amount they have already invested rather than evaluating the current and future value of the project. This bias can have severe consequences in the context of change management, as it can lead to organizations investing in failing projects, overlooking more viable alternatives, and stifling innovation. It also drives teams to over-rely on GRIT, in the hopes that things are about to improve.
Looking at the impact on change management efforts, the bias can manifest in several ways:
- Resistance to change: Employees may resist new technologies or processes due to their attachment to the time and effort invested in the existing systems. "Email works great for all my needs" is often said, but probe a little deeper, and you will find how many hours a day they spend working on emails.
- Overlooking alternatives: Managers may become overly committed to a specific technology or approach, ignoring or downplaying other viable options. Is an opportunity to introduce the concept of Red Teaming - even just a mini red-team exercise can help.
- Prolonged investment in failing projects: Organizations may continue to invest in projects with diminishing returns, reluctant to admit that their initial investment could have been better.
- Stacks of patches/band-aids have been implemented to keep an old process or add-in working.
Jeffrey Rubin's Story and Entrapment Problems
Jeffrey Rubin was a Psychology and Adjunct Diplomacy Professor at Tufts University. He was also a Senior Fellow in the Program on Negotiation at Harvard Law School and the author of more than a dozen books on interpersonal and international conflict. He was an expert in the escalation of commitment problems. He was also an experienced hiker who tragically perished while hiking in the mountains. Despite encountering adverse weather conditions and being warned by a graduate student that conditions were too rough and the student was turning back, Rubin continued his ascent and unfortunately perished. (Obituary)
His story serves as a powerful example of entrapment problems, where individuals become so committed to a course of action that they fail to recognize the warning signs or make rational decisions. We can all be victims of entrapment problems. In change management, entrapment can occur when organizations become so committed to a particular technology or project that they fail to recognize and adapt to changing circumstances, ultimately leading to, team stress, a complex solution architecture, over-time, over-budget, and poor outcomes.
Awareness is NOT enough
I love this quote from Anne Duke; "Knowing Isn't the Same as Doing" from the HBR podcast, Grit is Good. But Quitting Can Be, Too. Anne's quote underscores the importance of recognizing and mitigating the escalation of commitment bias. It is not enough to merely be aware of the bias; organizations must actively take steps to counteract its effects.
To prevent the Escalation of Commitment bias from hindering your efforts:
- Implement a culture of learning and adaptability, encouraging your team to embrace change and new technologies.
- Re-Journey Map! I emphasize the "re" part because, in many projects, we start with a gap assessment which would include time and effort to map the users' journey, but we need to reevaluate or update our maps regularly to make sure that minor decisions have not significantly altered the course for our users.
- Regularly evaluate and reassess projects, ensuring that decisions are based on current data and future prospects rather than past investments.
- Lead by example, open communication and feedback, enabling team members to hear concerns and highlight potential issues from across the project members.
Dead Horse Theory
The theory is derived from an old saying, "If you find yourself riding a dead horse, the best strategy is to dismount." The Dead Horse Theory is a metaphor that highlights the importance of recognizing when a situation or project is no longer productive, viable, or worth investing in and knowing when to move on.
If you find yourself riding a dead horse, the best strategy is to dismount.
I like the Dead Horse Theory because it is easily translatable to many issues in projects. The art is finding the balance for when more GRIT is needed to push through and when to change horses and find a different path to success.
The Escalation of Commitment bias can significantly impact technical change management efforts, often leading to bad outcomes. By understanding this bias, learning from stories like Jeffrey Rubin's, and heeding Anne Duke's advice, we can make more informed decisions and successfully navigate the complexities of change.
Frequently Asked Questions
What are the main causes of escalation of commitment?
Escalation of commitment arises due to several factors. These include a need to be perceived as competent by others and failure to admit when one is wrong. Another factor that causes escalation bias is a need to remain consistent with the previous action.
What is escalation of commitment in negotiation?
Escalation of commitment is a common mistake made by negotiators. It refers to the irrational escalation of negotiators' commitments to their past course of action. Due to a desire to be consistent, negotiators always tend to avoid changing their actions.
What leads to escalation of commitment?
Escalation of commitment arises when people fail to admit that one is wrong. It also occurs when people do not want to accept defeat. When people have an established routine, they continue following it due to a need to remain consistent.
| About the Author | Timothy Lynch | Senior Organizational Change Management Consultant | I help people as they go through technology changes |










Link copied!
Recently Updated News