Do people hate change… anymore?

“People hate change.”
It’s one of those business assumptions that gets repeated so often it starts to feel like a fact. We use it to explain why employees won’t adopt a new platform, why customers might struggle with a redesigned website, or why an organization keeps working around a process everyone agrees is broken.
Lately, though, I’ve been wondering whether that explanation still holds up.
In conversations at Mile6, I’m hearing more people update us on changes they’re already making. They’re reconsidering their marketing technology, reorganizing their teams, shifting priorities, and adjusting to different buying habits. These aren’t always changes we’re recommending. Often, our clients are bringing them to us.
The conversation seems less focused on whether something should change and more focused on how to make the next change work.
That’s an observation, not a scientific conclusion. But it raises an interesting question:
Are people becoming more open to change, or have we been misunderstanding what they resist?
Being used to change isn’t the same as loving it
I think it helps to separate three things: experiencing change, choosing change, and having the capacity to handle it.
Those aren’t interchangeable.
Consider someone who happily experiments with a new tool that makes a frustrating task easier. That same person might be exhausted by another departmental reorganization that changes their responsibilities without giving them more support.
There’s no contradiction there. One change offers relief. The other might create more work and uncertainty.
Research gives us a reason to take that distinction seriously. Qualtrics’ 2026 Employee Experience Trends study, based on responses from more than 33,000 employees across 24 countries, found that changes involving new technology and tools were associated with higher engagement. Restructuring, leadership turnover, and layoffs were associated with lower engagement. The type of change mattered, not simply the presence of it. Those associations don’t establish that the changes caused the engagement differences, but they challenge the idea that all change produces the same reaction. qualtrics.com
There’s evidence of strain, too. Gallup’s 2024 research found that employees experiencing disruptive organizational change were less engaged and more likely to report burnout and an intention to leave. Gallup.com
These studies measure different things. They don’t give us a clean, historical verdict that people now embrace change more than they used to.
They do suggest that “people hate change” is too blunt an explanation to be useful.
Is this a millennial thing?
The generational angle is tempting, especially with millennials making decisions about budgets, teams, technology, and customer experience.
Perhaps people whose careers have involved repeatedly learning new platforms are less attached to the idea that one system should last forever. Perhaps revisiting a tool or process feels less like admitting a mistake and more like part of the job.
That’s a reasonable hypothesis. It isn’t a personality trait we should assign to everyone born within a particular set of years.
Pew Research Center cautions that generational labels can exaggerate differences, obscure similarities, and confuse the effects of age with the effects of the period people are living through. Experiences that reshape work can affect several generations at once. Pew Research Center
Deloitte’s 2026 global survey illustrates the complexity. Roughly three-quarters of surveyed Gen Z and millennial respondents reported using AI in their day-to-day work. At the same time, the research described respondents prioritizing stability, sustainable career progression, and well-being. Adopting new technology and wanting a more predictable life can coexist. Deloitte
So I’m less interested in declaring one generation more adaptable than another.
I’m more interested in asking what someone’s experiences have taught them to expect from change.
Have previous changes made their work easier? Have they been included in decisions? Have promises been kept? Or have they repeatedly been handed new responsibilities under the cheerful heading of “an exciting opportunity”?
A birth year won’t answer those questions. A conversation might.
The change you choose feels different from the change you inherit
Imagine two versions of a technology rollout.
In the first, a team identifies a repetitive task that is eating up time. They help evaluate alternatives, test a proposed solution, and see how it could remove unnecessary work. They know what they’ll need to learn and what they’ll no longer have to do.
In the second, the team receives an announcement that a new platform is launching Monday. The benefits are described in company-wide terms, the training is a recording, and the old process still has to run alongside the new one.
Calling both situations “resistance to change” misses nearly everything that matters.
The question isn’t just whether the technology is better. It’s whether the people using it can understand the benefit, influence the transition, and realistically absorb the work.
I also have to acknowledge whose perspective I’m hearing in my own conversations. The person updating an agency on a new organizational direction may be helping lead that change. They may not be the person entering the same information into two systems while the transition gets sorted out.
An enthusiastic decision-maker is not the same thing as an enthusiastic organization.
That doesn’t invalidate the momentum I’m seeing. It means we should stay curious about what’s happening beyond the planning meeting.
Changing buying habits doesn’t mean customers want every new experience
The same distinction applies outside the organization.
A customer might be willing to switch brands, try a different way of buying, or use a new service. That doesn’t necessarily mean they want a company to redesign every familiar interaction.
PwC’s 2025 U.S. Customer Experience Survey found that 29% of consumers had stopped using or buying from a brand because of a poor customer experience. Meanwhile, 58% said they were only somewhat or not at all comfortable using AI tools to engage with brands. Willingness to leave an unsatisfying experience clearly isn’t the same as enthusiasm for every new technology. PwC
That’s where I think this becomes especially interesting for marketers and product teams.
Maybe the change we’re noticing is not simply a growing appetite for novelty. Maybe, in some situations, people are deciding that the familiar option no longer deserves their loyalty.
Consider a customer choosing between learning a different checkout process and continuing to use one that repeatedly fails. Or an employee comparing the effort of learning a new tool with the effort of maintaining a spreadsheet workaround indefinitely.
In those situations, staying the same has a cost, too.
Familiarity is a benefit. It should not be the entire value proposition.
“Our users won’t like it” should start a conversation, not end one
When someone says their users won’t accept a change, my next question would be: Which part?
Are they concerned about losing a familiar workflow? Having to learn something under pressure? Losing access to a person who helps them? Discovering that the replacement does less than the original?
Those concerns deserve different responses.
A usability problem calls for design work. A lack of confidence might call for clearer guidance and a chance to practice. A legitimate loss of functionality might mean the proposed solution needs to change.
None of those problems gets solved by deciding the audience is stubborn.
But the opposite assumption is just as unhelpful. We shouldn’t decide that people are so accustomed to change that we can skip research, move everything around, or replace a useful human interaction without asking.
User research should test both assumptions: that people will resist and that they will welcome what we’re proposing.
For a website, that might mean watching people complete their most important tasks before and after a proposed redesign. For an internal application, it might mean understanding the workarounds employees depend on before removing them. For an AI-enabled experience, it might mean identifying where users welcome assistance and where they want control.
The audience doesn’t need us to predict its attitude from a distance. We need to give people an opportunity to show us.
Make the change earn its place
For me, the practical takeaway is not that businesses should change faster.
It’s that we should get better at explaining, designing, and evaluating the changes we ask people to make.
Start with the problem rather than the announcement. Before introducing another platform, identify the specific difficulty it is supposed to address. What takes too long? Where does information get lost? What are customers struggling to accomplish?
“We’re modernizing” is an intention. “You’ll no longer have to enter the same information three times” is a benefit someone can evaluate.
Then account for the transition itself. Training, migration, testing, and temporary inefficiency belong in the plan. Ask what the team can stop doing to make room. An improvement that only works when everyone contributes an invisible second shift needs more thought.
Communication matters here, too. Gallup found that, among employees experiencing significant disruption, trust in leadership and effective communication were associated with substantially higher engagement and less burnout. Announcing a change is not the same as helping people understand what it means for them. Gallup.com
Where it makes sense, create smaller opportunities to learn before making larger commitments. Test a workflow with one team. Let users try a prototype. Establish a milestone that gives everyone a chance to review what is working and what needs adjustment.
Not every change can happen gradually. But even a major transition should have clear expectations, visible progress, and a way to surface problems.
Finally, measure something beyond completion. A launch date tells us when something became available. It doesn’t tell us whether the change was worthwhile.
Are people completing tasks more easily? Is the team spending less time fixing errors? Has support demand changed? Are users more confident? Did the promised benefit actually arrive?
Those are the questions I’d rather use to judge success.
Sometimes progress means changing less
This is an important distinction for an agency that helps organizations improve their technology.
A recommendation to evolve should not automatically become a recommendation to replace everything.
Sometimes the right answer is a new platform. Sometimes it’s connecting two systems the organization already owns. Sometimes it’s simplifying a form, removing a redundant approval, or making an existing feature easier to find.
A new login is not a strategy.
At Mile6, our approach is to understand the people, the problem, and the existing environment before deciding where to intervene. That might lead to strategy work, a design improvement, custom development, or ongoing iteration. It doesn’t require every organization to start over or follow the same path.
The goal should be a better experience, not a more impressive list of things that changed.
That is also how I think we earn permission for the next improvement: by making the current one useful.
So, do people hate change anymore?
I’m not convinced we can say people have broadly become more enthusiastic about change.
But I am increasingly skeptical of using resistance as our default explanation.
In the conversations I’m having, there seems to be more willingness to revisit assumptions, reconsider tools, and acknowledge that yesterday’s answer might not fit today’s problem. I think that’s encouraging.
It doesn’t mean people have unlimited patience, energy, or trust. It means we have an opportunity to meet that willingness with something better than another rollout.
Maybe people are more open to change.
Maybe they’re more practiced at it.
Maybe they’re simply less willing to keep working around things that should have been fixed.
Whatever the explanation, I think we should spend less time asking whether people hate change and more time asking a better question:
Is the change we’re asking them to make worth it?




