Home IT Basics Psychology in Change Management: 6 Biases That Hinder Adoption (and 6 Countermeasures)

Psychology in Change Management: 6 Biases That Hinder Adoption (and 6 Countermeasures)

IT Change Management

This wiki explores why change rarely fails because of technology, but rather because of psychological patterns, and how to deal with them effectively. Specifically, the authors* explain key phenomena such as the Dunning-Kruger effect, status quo bias, loss aversion, cognitive dissonance, escalation of commitment, and the self-fulfilling prophecy. They present real-world examples from analytics transformations and provide concrete countermeasures, metrics, and a clear roadmap for greater acceptance.

Table of contents

1. Why the Best Tool Alone Isn't Enough

In the previous wiki on the topic of IT Change Management focused on processes, communication, and adoption. The key insight was that IT implementations rarely fail because of the technology itself, but rather because the new solutions aren’t being used.

But even well-planned change initiatives can fail or run into trouble.

Let’s imagine the following scenario:
A company invests several hundred thousand francs in a new analytics platform. The solution works. The data is accurate. The dashboards are available. During the system presentation, everyone nods in agreement.
But three months later, the majority of employees are back to working with Excel, old reports, or their own data extracts. The tool wasn’t the problem.
But then what?

The answer rarely lies in technology. It lies in psychology. People do not always react rationally to change; instead, they follow deeply ingrained patterns of thought and behavior. This article focuses on precisely these patterns.

2. How Resistance Arises and Why It Is Often Logical

Resistance to change is often interpreted as a lack of openness or motivation. In reality, however, it is usually neither irrational nor malicious.

People try to use their existing experiences to navigate habits and decision-making processes. New systems challenge these habits. This can lead to uncertainty, a loss of control, or concerns about losing existing skills.

The good news is that these reactions have been well studied. Anyone who understands the underlying psychological mechanisms can drive change much more effectively.

3. Which psychological behavioral patterns hinder change and how to counteract them

The following subsections explain various behavioral patterns in more detail, illustrate them with real-world examples, and suggest potential countermeasures. Figure 1 also provides an overview of the psychological patterns, their impact during change, and what specifically helps.

Psychological PatternImpact in Times of ChangeWhat specifically helps?
Dunning-Kruger EffectOverestimating one's own knowledge, unwillingness to learnHighlight blind spots, establish benchmarks, and make learning accessible to everyone
Status-quo biasClinging to the Familiar, Resistance to New ProcessesHighlight the concrete benefits of the new system, simplify the onboarding process, and create positive initial experiences
Confirmation errorPeople tend to focus primarily on information that supports their existing viewHighlight counterexamples, test hypotheses, and consider different perspectives
Cognitive DissonanceNew facts threaten one's existing self-image or past decisionsRecognize the context; emphasize learning rather than blame; communicate growth rather than mistakes
Escalation of CommitmentOld solutions are being kept in use because a lot has already been invested in themEvaluate future benefits rather than past costs; consciously reframe decisions
Self-fulfilling prophecyNegative expectations steer perceptions and behavior toward failureHighlight quick wins, share success stories, and create positive case studies

Figure 1: The Invisible Obstacles to Change in Analytics Transformations

3.1. The Dunning-Kruger Effect, or “Our Reporting Works Just Fine!”

The psychological problem:

The Dunning-Kruger effect describes the tendency of people to overestimate their own abilities. Kruger and Dunning demonstrated this in a 1999 study: The bottom 25% of participants on a test estimated their own performance to be in the 62nd percentile. In reality, however, they were only in the 12th percentile. Those who do not recognize their knowledge gaps often see no need for change.

Real-world example:

Before implementing a new analytics solution, people often argue, “Our reporting system already works just fine.” However, a detailed analysis reveals that there is a significant amount of manual work involved, data is entered multiple times, key metrics are inconsistent, and decision-making cycles are long. These problems already existed; they simply went unnoticed.

What helps?

Don't try to convince—show instead:

  • Measuring Time Spent
  • Making Error Rates Transparent
  • Quantifying Process Inefficiencies
  • Document Pain Points

People need to recognize the gap for themselves. Only then will a genuine willingness to change emerge.

3.2. The Status Quo Bias: Why Familiar Tools Like Excel Win Out

The psychological problem:
One might think that people prefer existing solutions because they are of higher quality. In fact, they often prefer them because they are familiar, and change is perceived as uncertain—not because they are objectively better. Samuelson and Zeckhauser (1988) demonstrated this, among other things, in decisions regarding health insurance and retirement planning: Many people stuck with their original choice even though there were objectively better alternatives.

Real-world example:

The new analytics platform enables faster analysis, higher data quality, and better visualizations. Nevertheless, many employees continue to rely on their familiar Excel files. Not because Excel is objectively better, but because it seems familiar and predictable. Today, people might not even choose the old solution anymore. Yet they stick with it.

What helps?

Instead of a major upheaval, small, controlled changes are more helpful.

  • Establish pilot groups
  • Conduct testing phases
  • Enabling Positive Experiences
  • A Gradual Rollout Instead of a Big Bang

A gradual rollout lowers the barrier to entry more than making one big decision all at once.

3.3. Loss Aversion: Why Gains Often Take a Back Seat to Losses

The psychological problem:

Psychologically, a loss weighs about twice as heavily as a gain of the same magnitude. Kahneman and Tversky demonstrated this as early as 1979. The fear of what might be lost has a stronger effect than the prospect of what might be gained.

What helps?

The future benefits must be just as tangible as the losses:

  • Show specific success scenarios
  • Communicate Early Successes
  • Highlight Individual Benefits
  • Implementing Change Gradually

People need to realize what they stand to gain, not just what they're giving up.

3.4. Cognitive Dissonance, or When Facts No Longer Help.

The psychological problem:

When behavior and attitudes do not align, an unpleasant sense of tension arises. Leon Festinger described this phenomenon as “cognitive dissonance” as early as 1957. However, people rarely resolve this tension by actually changing their behavior. More often, they adjust their attitudes after the fact to justify their previous behavior.

Real-world example:

Six months after the analytics solution was implemented, the first signs of success are becoming apparent: higher data quality, faster reports, and more data-driven decisions.

Nevertheless, people still say things like: “The data isn’t right.” “Excel is good enough.” “It used to work that way.”

The facts are not rejected because they are false, but because they call previous behavior into question.

What helps?

It helps to make it easier to admit the truth and to take the stigma of failure away from the issue.

  • Recognizing the context of that time
  • Focus on learning rather than blame
  • Communicate Progress Rather Than a Mistake

Not: “The old way was wrong.” But rather: “The demands have grown.”

3.5. Escalation of Commitment: Too Much Invested to Turn Back

The psychological problem:

People and organizations tend to stick to decisions once they’ve been made, the more time, money, and energy they’ve already invested in them. Even when it has long been clear that another solution would make more sense, it’s difficult to stray from the path they’ve chosen. This pattern is known as the escalation of commitment. Previous investments increase the willingness to stick with a decision, even when it no longer proves to be the best option. The reason is not primarily factual, but psychological: a change of course would mean admitting that earlier decisions are no longer viable today. To avoid this admission, people often continue to invest—often in the hope of justifying the original decision after all.

Real-world example:

Over the years, the company has invested significant resources in an existing reporting or BI system.

Although there are now significantly better alternatives, investment in the old solution continues.

Not because it's the best option. But because so much has already been invested in it that making a change would seem like an admission of a bad decision or a loss.

What helps?

It is helpful to consciously separate this decision from past investments and to consistently look ahead.

  • Which solution will create the greatest value in the future?
  • Which option better supports the strategy?
  • Which investment would we make again today?

What matters is not what has already been invested. What matters is which option is better now and in the future.

3.6. The Self-Fulfilling Prophecy: Those Who Expect Failure Will Find Evidence of It

The psychological problem:

Expectations influence what people pay attention to, how they evaluate events, and how they behave. People who expect failure tend to notice, above all, clues that confirm that expectation. In 1948, sociologist Robert Merton coined the term “self-fulfilling prophecy” to describe this phenomenon.

Real-world example:

Even before the go-live, some employees are expressing doubts: “The new tool won’t work anyway.”

After launch, errors, exceptions, or teething problems are immediately noted and interpreted as confirmation of the original assumption. Positive developments or initial successes, on the other hand, go largely unnoticed.

What helps?

It is helpful to first make expectations clear and then focus on creating positive experiences.

  • Highlight Quick Wins Early On
  • Actively Share Success Stories
  • Highlight positive examples of use
  • Establishing Early Reference Cases

Expectations influence perception. Perception influences behavior. And behavior helps to confirm expectations.

4. What does this mean for analytics transformations?

The psychological effects described here make one thing very clear: analytics transformations rarely fail because of dashboards, data models, or technologies.

They fail because people don't change their habits, ways of thinking, and decision-making processes overnight.

That is why communication alone is not enough. Successful change management means building trust, fostering a sense of ownership, providing guidance, and actively supporting behavioral changes.

Successful transformations manage systems first and foremost. They manage human behavior.

5. Conclusion & What to Do Next

From a technical standpoint, the analytics tool in our example could have been the best solution on the market. But that alone would not have changed employee behavior in any way.

The biggest challenges in transformation efforts are rarely technical in nature. They arise when people are expected to change their ways of thinking, habits, and decision-making patterns.

The key question for the next tool rollout is therefore not just: Is the tool good enough?

But above all: Have we gotten the people who are supposed to work with it on board?

Anyone facing an analytics, reporting, or data transformation should therefore look beyond just technology and processes. Sustainable success comes when change is embedded in behavior.

Do you want to ensure that new analytics systems not only go live but are also actually used?

Then talk to us here about IT change management: from stakeholder alignment and communication to adoption KPIs and sustainable integration into everyday work.

List of Sources and Further Reading

1. Kruger & Dunning (1999) – Dunning-Kruger Effect
Kruger, J., & Dunning, D. (1999). Unskilled and Unaware of It.Journal of Personality and Social Psychology, 77(6), 1121–1134.
Unskilled and Unaware of It: How Difficulties in Recognizing One’s Own Incompetence Lead to Inflated…

2. Samuelson & Zeckhauser (1988) – Status Quo Bias
Samuelson, W., & Zeckhauser, R. (1988). Status quo bias in decision making.Journal of Risk and Uncertainty, 1, 7–59.
https://rzeckhauser.scholars.harvard.edu/publications/status-quo-bias-decision-making

3. Kahneman & Tversky (1979) – Loss Aversion
Kahneman, D., & Tversky, A. (1979). Prospect theory: An analysis of decision under risk.Econometrica, 47(2), 263–291.
Prospect Theory: An Analysis of Decision under Risk | JSTOR

4. Staw (1976) – Escalation of Commitment
Staw, B. M. (1976). Knee-deep in the big muddy.Organizational Behavior and Human Performance, 16(1), 27–44.
https://psycnet.apa.org/record/1976-27199-001

5. Merton (1948) – Self-Fulfilling Prophecy
Merton, R. K. (1948). The self-fulfilling prophecy.The Antioch Review, 8(2), 193–210.
The Self-Fulfilling Prophecy | JSTOR

6. Festinger & Carlsmith (1959) – Cognitive Dissonance
Festinger, L., & Carlsmith, J. M. (1959). Cognitive consequences of forced compliance.Journal of Abnormal and Social Psychology, 58(2), 203–210.
Cognitive consequences of forced compliance – PubMed

*Authors: Gabriel Grieder and Adrian Stenger (both of s-peers AG)

Published by:

Gabriel Grieder

author

How did you like the article?

How helpful was this post?

Click on a star to rate!

Average rating 5 / 5.
Number of ratings: 1

No votes so far! Be the first person to rate this post!

INFORMATION

More information

SAP Sapphire 2026 Glossary: Joule, AI Agents, and the Autonomous Enterprise Explained Simply

Joule, AI agents, Autonomous Enterprise, A2A protocol—all the new SAP terms from Sapphire 2026 at a glance. Look them up now in the s-peers glossary.
Wiki Big Query SAP Warehousing

Google BigQuery vs. SAP BW: A Comparison of Two Data Warehouse Solutions

This Wiki article introduces two leading solutions for data management and analysis in today's data-driven world: Google...
AI Transformation and Behavioral Economics: Why People (Often) Don't Want to Change

AI Transformation and Behavioral Economics: Why People (Often) Don't Want to Change

In this wiki, Yvonne uses behavioral economics to explain why change is so difficult in companies. Why do people act...
AI Adoption Success Factors: Change Management

What Really Drives AI Adoption in Companies? 6 Factors That Determine Success or Failure.

This wiki explores why change rarely fails because of technology, but rather because of psychological patterns, and how...
IT Change Management

IT Change Management: Definition, Process, and Best Practices

Companies realize less than one-third of the expected benefits from digital transformations, not because the technology fails, but because...

What Is FP&A? Definition, Core Processes, and the Future of Corporate Management

Companies aren't managed by reports—they're managed by better decisions. FP&A, or Financial Planning & Analysis, is the strategic...

Mission Lakehouse – All Wikis at a Glance

Our Lakehouse mission is complete. In a series of 10...