Why People Resist Change at Work—and What Leaders Often Miss

Introduction: When a Good Change Meets Human Reality

Organizations spend considerable time planning change. They evaluate technology, redesign processes, develop implementation plans, and communicate what needs to happen next. But the people expected to navigate those changes experience something different. They experience what the change means for their work, their responsibilities, their relationships, and sometimes their sense of value. And when their response doesn't match what leadership expected, we often reach for a familiar label: resistance. But what are we actually seeing?

In architecture, engineering, and construction (AEC), change is part of everyday work. New technologies, evolving project delivery methods, shifting workforce expectations, and changing client needs continually challenge how organizations operate. And we're good at solving complex problems. We develop plans, manage risk, coordinate teams, and build systems to deliver results. But implementing change introduces another kind of complexity. The people expected to adopt a new process or technology bring their own experiences, assumptions, concerns, and established ways of working. A change that makes sense from an organizational perspective may feel very different to someone responsible for making it work.

Sometimes the response is hesitation. Sometimes people ask difficult questions, challenge the direction, or continue relying on familiar ways of working. Other times, they say very little. It's tempting to interpret these reactions as resistance to change. But that label doesn't tell us much about what's actually happening. Are people questioning the decision itself? Are they concerned about what they might lose? Do they see risks that haven't been addressed? Or are they simply unsure how they're supposed to participate? These are different experiences, and they deserve different conversations. Because change management isn't only about implementing a new direction. It's also about understanding how people experience the transition.

Why People Resist Change—Even When They Understand It

When people question a change, one of our first instincts as leaders is to explain it again. We revisit the reasons behind the decision, reinforce the expected benefits, and try to help everyone understand why the change is necessary. And sometimes, that additional clarity is exactly what's needed. But understanding why a change makes sense doesn't necessarily mean someone is ready to experience it. A person can agree with the direction an organization is taking and still have legitimate concerns about what it means for their work, their responsibilities, or their ability to succeed.

Consider a project manager whose organization is introducing a new project management platform. They understand why the company wants better visibility into project performance. They may even agree that the existing system creates unnecessary work. But they also know how to navigate that existing system. They've developed routines, learned its limitations, and figured out how to get reliable information when they need it. Now they're being asked to learn something unfamiliar while continuing to meet deadlines, manage project risks, and support their teams. Their hesitation may have very little to do with whether they believe the new platform is a good idea. They understand the reason for the change. What they're still trying to understand is how they'll navigate it.

When we label someone's response as resistance, we risk ending the conversation before we understand what's behind it. Sometimes the concern really is about the technology or process. Perhaps the new system introduces unnecessary steps, creates additional risk, or doesn't account for how work actually happens. Other times, the concern is more personal. People may be questioning whether they have the skills, time, support, or influence needed to navigate the transition. And sometimes, both are true. The challenge for leaders isn't to assume every concern is valid or that every decision needs to be reconsidered. It's to remain curious long enough to understand what people are responding to. Because until we understand what's creating the friction, we may find ourselves trying to solve the wrong problem.

The Question Beneath Change: "What Does This Mean for Me?"

Every organizational change has a business rationale. Maybe the goal is greater efficiency, improved coordination, better project outcomes, or a more competitive organization. Those reasons matter. But people don't experience change exclusively through the organization's objectives. They also experience it through their own responsibilities, relationships, capabilities, and expectations.

Imagine an experienced construction superintendent being asked to adopt a new digital reporting process. Leadership sees an opportunity to improve documentation, increase visibility, and reduce communication gaps. The superintendent may see those same benefits while also wondering whether the new process will take time away from the field, create additional administrative work, or change how their performance is evaluated. Neither perspective is necessarily wrong. They're simply looking at the same change from different positions.

Beneath many reactions to change is a personal question: "What does this mean for me?" That isn't necessarily selfishness or an unwillingness to support the organization. It's part of how people make sense of uncertainty. Will I still be effective? What will I need to learn? How will my role change? What happens to the experience I've spent years developing? Leaders don't need to have perfect answers to every question, but they do need to recognize that these questions exist. A business case explains why the organization wants to change. It doesn't automatically help every person understand how to navigate that change.

Informed Isn't the Same as Involved

Communication matters during change. People need to understand what's happening, why decisions are being made, and what is expected of them. But being informed about a decision isn't the same as having a meaningful opportunity to participate in what happens next.

Consider a company introducing a standardized workflow across multiple project teams. Leadership may have good reasons for the decision: inconsistent practices create confusion, make reporting difficult, and introduce unnecessary risk. But the people using those workflows every day may understand details that weren't visible during planning. A process that works well in one office or on one project may create unexpected challenges somewhere else. If those concerns surface only after implementation, they can look like resistance when they may actually be valuable information about how the work gets done.

Participation doesn't mean every decision becomes a vote. Leaders still have responsibilities, deadlines, and decisions to make. Sometimes the direction is already established. But people can still have a voice in how a change is introduced, what support is needed, which risks deserve attention, and how the organization learns along the way.

This is where Choice, one of the 5 Cs of Change, becomes important. People may not get to choose whether a change happens, but they can often make meaningful choices about how they engage with it. When leaders create opportunities for participation, they help people move from experiencing change as something happening to them toward seeing where they can contribute to what happens next.

When Familiar Ways of Working Become Hard to Release

Experience is valuable in the AEC industry. Professionals develop expertise through years of solving problems, navigating uncertainty, and learning what works under real project conditions. Over time, familiar processes become more than routines. They become part of how people demonstrate competence, manage risk, and deliver results.

When an organization introduces a new way of working, it may unintentionally challenge that sense of competence. Someone who has spent years becoming highly effective with an established process is suddenly expected to operate as a beginner again. Even when the new approach promises long-term improvements, the transition can temporarily make work slower, less predictable, and more frustrating.

That helps explain why Control matters during change. Familiar methods provide a sense of predictability. People know what to expect, where problems tend to occur, and how to respond when something goes wrong. A new system may remove some of that confidence before people have developed the skills to work effectively within it.

But releasing control doesn't mean abandoning responsibility. In industries where safety, quality, cost, and schedule matter, some controls are essential. The challenge is recognizing the difference between the controls that protect important outcomes and the familiar habits we hold onto because they make us feel more comfortable.

Leaders can help by acknowledging the experience people bring into a transition rather than treating everything associated with the old way as outdated. Ask what the current process does well, what knowledge needs to carry forward, and what could be lost if the organization moves too quickly. Sometimes the most useful insight about a new approach comes from someone who understands the old one exceptionally well.

Clarity Isn't Certainty: Helping People Take the Next Step

One of the challenges of leading change is that people naturally want answers at the very moment leaders may still be working through the unknowns. A new technology may be selected before every workflow has been tested. An organizational restructuring may be announced before every responsibility is fully defined. A new project delivery approach may require teams to learn and adjust as implementation unfolds.

It's tempting to respond by trying to create certainty. We develop detailed plans, timelines, and presentations that suggest the path ahead is more predictable than it really is. But uncertainty doesn't disappear because we've created a schedule.

Clarity is different from certainty. Certainty suggests we know exactly how things will unfold. Clarity helps people understand where we're going, why it matters, what we know today, and what needs to happen next. It also means being willing to acknowledge what we don't know yet.

Think of clarity as having enough light to see the next part of the path, even if the entire journey isn't visible. People don't necessarily need every answer before they can begin participating. They need enough understanding to make informed decisions, recognize expectations, and know where to turn when questions arise.

For leaders, this means communicating more than the desired outcome. Explain what's changing and what's staying the same. Identify where decisions have already been made and where input is still welcome. Be clear about immediate priorities, available support, and how new information will be shared. When something remains uncertain, say so. Credibility doesn't require pretending to know everything. It requires helping people navigate what is known and unknown.

From Resistance to Curiosity: Navigating the Messy Middle

Most organizational changes have a period when the old way of working no longer fits, but the new way hasn't become comfortable or reliable. Teams are learning unfamiliar processes, discovering unexpected challenges, and adjusting expectations while still being responsible for delivering results. This is the messy middle of change, and it's often where initial enthusiasm encounters operational reality.

It's also where Commitment becomes more meaningful. Commitment isn't simply agreement during a kickoff meeting or enthusiasm following an announcement. It develops through the experience of working through uncertainty, making adjustments, and deciding to continue participating even when the process is uncomfortable.

Leaders sometimes interpret frustration during this period as evidence that people aren't committed. But frustration can also mean people are trying to make the change work and encountering problems they don't yet know how to solve. The distinction matters because it changes the conversation. Instead of asking why someone isn't getting on board, we might ask what they're experiencing and what would help them move forward.

This is where Curiosity can change how leaders relate to resistance. Curiosity doesn't require agreeing with every concern or reconsidering every decision. It asks us to become interested in what we don't yet understand. What is making this difficult? What assumptions did we make during planning? What are people noticing that leadership may not be seeing?

These questions don't eliminate the need for accountability. Leaders still need to set expectations, address performance issues, and make difficult decisions. But curiosity creates an opportunity to distinguish between unwillingness to participate, uncertainty about how to proceed, and legitimate problems with the change itself.

Taken together, the 5 Cs of Change—Choice, Control, Clarity, Commitment, and Curiosity—offer a way to explore the human experience of change. They aren't five sequential steps or a formula that guarantees adoption. They're different dimensions of how people relate to change, and they can help leaders recognize where a transition may feel less navigable than intended.

What Leaders Can Do Differently When People Push Back

When someone pushes back against a change, the first response doesn't have to be another explanation or a stronger directive. It can be a question. Not a question designed to persuade someone toward a predetermined answer, but one intended to understand what they're experiencing.

For example, if a team is struggling with a new digital workflow, ask what the previous process allowed them to do that the new one makes more difficult. Ask where the transition is creating additional work, which expectations remain unclear, and what support would make the next step more manageable. These questions help uncover practical barriers while also giving people an opportunity to contribute their experience.

Leaders can also be more intentional about creating opportunities for feedback. Not every concern will surface during a formal meeting, particularly when people are unsure how their questions will be received. Making it safe to raise concerns means responding without immediately becoming defensive, acknowledging useful information, and following through when issues need attention. It also means being transparent when a decision cannot change and explaining why.

Another important responsibility is recognizing the cost of learning. Adopting a new process takes time and attention, especially when people are expected to maintain existing performance standards throughout the transition. Training alone may not be enough if workloads, deadlines, and expectations leave little room to practice. Leaders need to consider whether they've created the conditions for people to develop competence, not simply communicated that competence is expected.

Finally, pay attention to what happens after implementation begins. Where are people finding better ways to work? What assumptions have proven incorrect? What feedback is helping improve the process? Recognizing these contributions reinforces the idea that participation matters beyond the initial announcement.

None of this guarantees that everyone will embrace a change. Some decisions will remain unpopular, and some resistance will require direct conversations about expectations and accountability. But approaching these situations with curiosity gives leaders a better chance of responding to what's actually happening rather than relying on assumptions.

Conclusion: What Might Resistance Be Telling Us?

We spend a great deal of energy trying to make organizational change more predictable. We build plans, establish milestones, define responsibilities, and measure progress. Those efforts matter, particularly in industries where uncertainty can carry significant consequences. But even the strongest implementation plan can't account for every aspect of how people will experience a transition.

People bring more than technical skills to their work. They bring experience, relationships, expectations, and a sense of what helps them succeed. When change challenges those things, their responses may not fit neatly into the categories we've created to manage the process.

That's why resistance deserves more curiosity than judgment. Not because every concern is justified or every decision should be reconsidered, but because the response may contain information we need to understand.

The next time someone questions a change, consider what might happen if the conversation began somewhere other than trying to convince them. What might you learn about the work, the person, or the change itself?

What might resistance be telling us that we haven't been curious enough to ask?

Activating Curiosity® explores the human side of change, leadership, and the ways we navigate uncertainty together. Explore the podcast for more conversations about what becomes possible when we approach familiar challenges with different questions.