your team doesnt hate change

Your Team Doesn't Hate Change. They Hate How You Roll It Out.

October 14, 2026•12 min read

I've seen business owners spend months building a new strategy, only to roll it out to their team and immediately face resistance.

And I've been on both sides of that experience.

Here's what I've learned:

Your team doesn't necessarily resist change. They resist losing control over something they already know works.

As leaders, we've had weeks or months to get excited about a new direction. We've built the plan, worked through the challenges, and envisioned the outcome.

Our teams haven't.

And yet, we expect them to be just as committed to executing it as we are.

That's where a lot of leaders get it wrong.

There's a better way to create genuine buy-in, and it starts with understanding the psychology behind resistance.

I recently explored this topic on my podcast, Scale It with Hilary Russell. Listen to the full episode here →

Why Employees Resist Change (Even When It's Good for the Business)

When you're building and scaling a business, change is inevitable.

New processes. New systems. New products. New team structures. New expectations.

As business owners, we see these changes through the lens of opportunity.

We see how a new system could improve efficiency, how a new strategy could increase revenue, or how restructuring a department could create a better experience for our customers.

But our employees often see something different.

They see the routines they've become comfortable with potentially disappearing.

They see processes they've mastered being replaced.

They see uncertainty about whether they'll be as successful in the new environment as they were in the old one.

And even if they understand that the change could ultimately benefit the company, that doesn't automatically eliminate their hesitation.

There are two psychological concepts that help explain why.

1. Loss Aversion: People Feel the Loss Before They See the Gain

Psychologists Daniel Kahneman and Amos Tversky helped establish the concept of loss aversion, which describes our tendency to experience losses more intensely than equivalent gains.

Think about how this plays out when you're implementing a new process.

You might see a system that will save your team several hours each week once it's fully implemented.

Your team might see several weeks of learning something unfamiliar, giving up their current workflow, and potentially making mistakes along the way.

You're focused on the future gain.

They're focused on the immediate loss.

Neither perspective is necessarily wrong.

But if we fail to recognize the difference, we can unintentionally create resistance before the change has even begun.

2. The IKEA Effect: People Value What They Help Build

Another fascinating psychological concept is the IKEA effect.

Research suggests that people often place greater value on things they've personally helped create.

This has significant implications for leadership.

Imagine your leadership team has spent three months developing a new operational strategy.

They've been involved in the discussions, the problem-solving, the planning, and the decision-making.

By the time the strategy is ready to launch, they're completely invested in its success.

Then they introduce it to the rest of the organization.

And they're surprised when everyone isn't immediately as excited as they are.

But why would they be?

Your leadership team isn't necessarily more committed because they care more. They've simply had the opportunity to help build the plan.

The people responsible for executing that plan haven't had that same experience.

Which raises an important question:

How do we create that same sense of ownership for the people who didn't help develop the original strategy?

The Leadership Framework I Use: Own the What, Share the Why, Hand Over the How

One of the most effective approaches I've found for introducing organizational change is a simple three-part framework:

Own the What. Share the Why. Hand Over the How.

It creates clarity around leadership responsibilities while giving your team meaningful ownership over execution.

Step 1: Own the What

As the leader, it's your responsibility to establish the direction.

What are we trying to accomplish?

What needs to change?

What does success look like?

What are the non-negotiables?

Your team needs clarity about the outcome.

Vague direction creates uncertainty, and uncertainty can quickly turn into anxiety.

I've seen leaders announce major organizational changes with very little context, assuming everyone will naturally understand what needs to happen next.

But that's rarely the case.

Be clear about the desired outcome, the expectations, the timeline, and what will be different once the change is implemented.

You don't need to have every detail figured out.

But your team should understand where you're going and what you're asking them to help accomplish.

Step 2: Share the Why

Most leaders understand that explaining the reason behind a change is important.

But I think there's a critical distinction that often gets overlooked.

Don't just explain why the change is important to the business. Explain why it's important to the people responsible for making it happen.

How will this improve their role?

What problem will it solve for their department?

How does their expertise contribute to the outcome?

What opportunities might this create for them?

People want to feel that their work matters.

They want to know that their skills, contributions, and efforts are valuable.

When you connect the larger business objective to the individual people executing it, you create an entirely different conversation.

You're no longer simply announcing a new process.

You're helping your team understand why they're an important part of what comes next.

Step 3: Hand Over the How

This is the step I believe many entrepreneurs struggle with the most.

Letting go of control.

As business owners, we're often accustomed to being the ones who figure everything out.

We identify the opportunity, develop the strategy, create the process, and determine how it should be executed.

But that approach becomes increasingly difficult to sustain as a company grows.

At some point, we have to trust the people we've hired to do what they're good at.

Handing over the how means giving your team meaningful ownership over execution.

That doesn't mean removing accountability or abandoning structure.

You can still establish deadlines, milestones, performance expectations, and guardrails.

But within those parameters, allow your team to contribute their expertise and determine the most effective path forward.

Instead of saying:

"Here's the new process. Follow these instructions exactly."

Try:

"Here's the outcome we're working toward. Here are the expectations and milestones. I want your input on the best way for your team to accomplish this."

That shift gives people an opportunity to participate in building the solution.

And when people feel ownership over the process, they're often more invested in the outcome.

Two Things I Recommend Doing With Every Major Rollout

Beyond the framework itself, there are two practices I've found particularly helpful when introducing new initiatives.

Subtract Before You Add

One of the easiest ways to overwhelm your team is to continually introduce new initiatives without acknowledging the workload they're already carrying.

As leaders, we're thinking about everything a new process will eventually improve.

But our employees may simply hear:

"Here's another thing I have to do."

Whenever possible, identify what the new initiative will eliminate, simplify, or improve.

Maybe it reduces duplicate work.

Maybe it eliminates unnecessary meetings.

Maybe it creates a better client experience that ultimately results in fewer support issues.

Whatever it is, communicate it.

And if the benefits won't be immediate, acknowledge that too.

Your team should understand that you're not simply adding more work for the sake of growth.

You're working toward a better way of operating.

Create a Visible Win Within the First Two Weeks

Research associated with Teresa Amabile's progress principle highlights how meaningful progress can contribute to motivation at work.

I've seen this play out in organizations I've worked with and helped lead.

When people begin seeing results from their efforts, something changes.

They gain confidence.

They become more invested.

And the momentum starts building.

That's why I recommend creating an opportunity for a visible win within the first two weeks of implementing something new.

It doesn't have to be a massive accomplishment.

Sometimes the most valuable thing you can do is simply make progress visible.

For example, I've used dedicated Slack channels where team members can share wins associated with a particular initiative.

It might be a positive customer response.

A milestone completed ahead of schedule.

A process improvement that saved someone time.

Those wins were likely going to happen regardless.

But creating a place where the entire team can see them helps reinforce that their efforts are making a difference.

Early progress builds confidence. And confidence creates momentum.

The Part of Leadership We Don't Talk About Enough

There's another piece of implementing change that I think deserves just as much attention as the strategy itself.

And that's how we show up for our people.

As entrepreneurs, it's incredibly easy to become consumed by everything we're building.

We're thinking about new opportunities, solving problems, managing deadlines, and trying to keep everything moving forward.

Sometimes we're so focused on what needs to happen next that we forget to consider what the experience feels like for the people helping us execute it.

I had a moment recently that reminded me of this.

My business partner and I have been working on several new business initiatives.

We have an incredible operations director who plays a major role in helping bring those ideas to life.

After one of our team meetings, I realized that I'd been so focused on deliverables, timelines, and expectations that I hadn't really taken the time to acknowledge how much we were asking her to take on.

And I didn't love that.

Because while the businesses we're building are important to me, the people helping us build them are just as important.

So I reached out.

I acknowledged that we had a lot happening, expressed how much I appreciated her, and made sure she knew that I recognized the weight of everything we were working through.

She reassured me that she was doing great and was excited about what we were building.

But she also appreciated the acknowledgment.

It wasn't some complicated leadership strategy.

It was simply taking a moment to recognize the person behind the work.

And I think those moments matter more than we sometimes realize.

Your team notices when you're distracted.

They notice when meetings become purely transactional.

They notice when expectations increase but support decreases.

And over time, those small moments can create distance between leadership and the people responsible for executing the vision.

You don't have to be a perfect leader.

But you do need to be intentional about how you show up.

The Psychology of Creating Lasting Team Buy-In

There's another psychological concept that connects many of these ideas.

Self-determination theory, developed through the work of psychologists Edward Deci and Richard Ryan, identifies three fundamental psychological needs associated with motivation:

Autonomy: Feeling a sense of ownership and choice.

Competence: Feeling capable and effective.

Relatedness: Feeling connected to others and a meaningful purpose.

Now think about how those three principles apply to implementing organizational change.

When you give your team ownership over how they execute, you're supporting autonomy.

When you acknowledge their expertise and create opportunities for early wins, you're reinforcing competence.

When you explain why their role matters and remain genuinely present throughout the transition, you're strengthening connection.

This is why I believe successful change management is about much more than getting people to follow a new procedure.

It's about creating an environment where people feel equipped, trusted, and motivated to help move the business forward.

And as your business grows, that becomes increasingly important.

Because the larger your organization becomes, the less sustainable it is for every decision, every process, and every initiative to depend entirely on you.

Six Questions to Ask Before Your Next Major Change

The next time you're preparing to roll out a new process, system, strategy, or organizational change, ask yourself:

  1. Have I clearly defined the outcome? Does everyone understand what we're trying to accomplish and what success looks like?

  2. Have I explained why it matters to the team? Not just the business benefit, but how this impacts the people doing the work?

  3. Have I given the right people ownership? Am I leveraging their expertise or simply expecting them to follow instructions?

  4. Have I identified what this change will simplify or eliminate? Am I acknowledging the workload it creates?

  5. Have I created an opportunity for an early win? How will we recognize and communicate progress?

  6. Am I showing up as the leader my team needs? Am I present, supportive, and aware of how this change impacts them?

You don't need perfect answers.

But I believe asking these questions can dramatically improve the way you lead your team through growth.

The Bottom Line: Make Change Happen With Your Team, Not to Them

Scaling a business requires change.

New systems. New strategies. New people. New responsibilities. New ways of operating.

Those things are inevitable.

But the resistance, resentment, and unnecessary friction that sometimes accompany them don't have to be.

As leaders, we have an opportunity to approach growth in a way that doesn't just improve the business.

It also empowers the people helping us build it.

Your team doesn't have to love every decision you make.

They don't have to agree with every change.

But they should feel respected, informed, supported, and trusted throughout the process.

Own the what. Share the why. Hand over the how.

Because the goal isn't just to get your team to accept change.

It's to build a team that's capable of helping you lead it.


Want to Go Deeper? Listen to Scale It with Hilary Russell

I recently explored this topic on my podcast, Scale It, where I share practical leadership strategies, business growth frameworks, and perspective shifts to help entrepreneurs build stronger, more scalable businesses.

In this episode, I break down the psychology behind employee resistance, how to create genuine buy-in, and why the way we lead through change matters just as much as the change itself.

Listen to How to Get Your Team to Embrace Change (Instead of Resisting It) →


About the Author

Hilary Russell is an entrepreneur, business growth strategist, and host of Scale It, a podcast focused on helping business owners build stronger teams, develop scalable systems, and grow businesses that don't depend on their constant involvement.

Drawing from her experience building and scaling businesses, Hilary shares practical leadership principles, growth strategies, and frameworks that help entrepreneurs move from doing everything themselves to building organizations designed for sustainable growth.

Hilary Russell

Hilary Russell

Hilary Russell is a growth strategist, business owner, and executive leader who helps founders build scalable businesses through better strategy, systems, marketing, and leadership.

Back to Blog