Table of Contents
- Why Employees Resist Change
- Communicating Change to Employees
- How to Get Staff Buy-In for New Initiatives
- Employee Resistance to Change Examples
- Building Leadership Support and Alignment
- Creating a Culture That Embraces Change
- Sustaining Adoption and Reinforcing Change
- Frequently Asked Questions
Last Updated: October 17, 2026
Why Employees Resist Change
When you announce a new initiative, you expect questions, not the quiet resistance that follows: the hesitation, the "we've always done it this way" comments, the slow adoption that feels like pushing uphill.
Staff resistance to new initiatives isn't personal. It's human, your team is responding to uncertainty and genuine worry about what the change means for them.
Understanding why people resist is your first step toward moving them through it.
Fear of the unknown and uncertainty
People resist what they don't understand. A new system puts your team in unfamiliar territory, and that feels risky.
Your educators might be thinking: Will I be able to do this? What if I get it wrong? These are real concerns about competence and confidence, and people naturally pull back from discomfort.
Loss of control and perceived risk
Change takes away something people value: predictability. They've mastered the current way, the shortcuts, the rhythm, and a new initiative puts them back at square one. People feel most confident when they're in control of their environment.
Workload and competing priorities
Sometimes staff resistance isn't about the change itself, it's about workload. Your team is already stretched with children, families, documentation and compliance. If educators feel overwhelmed, they'll resist not because the change is bad, but because they genuinely don't have capacity. They're protecting themselves from breaking.
Communicating Change to Employees
How you communicate a change shapes whether your team embraces it or resists it. The biggest mistake is jumping straight to the "what" without the "why", without it, your team just sees extra work.
Share the 'why' before the 'what'
Start with the reason, and be specific. Don't say "we need to improve communication." Say "we noticed important information wasn't reaching everyone, so some educators were missing updates about children's needs. This system makes sure everyone has the same information at the same time." When people understand the problem you're solving, they can see why their effort matters.
Use two-way communication and active listening
Telling people about a change isn't the same as communicating with them. After you share the why and the what, create space to respond. Ask questions and really listen, not to explain why they're wrong, but to understand their concerns. When people feel heard, they engage; when dismissed, they dig in harder.
How to Get Staff Buy-In for New Initiatives
Buy-in doesn't happen by accident. It happens when people feel involved, heard, and supported through the change.
Involve staff early in the planning process
The best time to build buy-in is before you've finalised everything. Ask for input: What's working now? What frustrates people? What would make the new approach better? People who help design something are far more likely to support it. You don't need to take every suggestion, but show you've listened and that their input shaped the decision.
Create space for feedback and concerns
After you've launched, keep listening. Ask how it's going, what's working, what's hard, what they need. Build regular check-ins into your routine and make it safe to say "this isn't working" without fear of being shut down. When you respond by changing things or providing support, you show their voice matters, and that builds trust.
Employee Resistance to Change Examples
Resistance shows up differently depending on who's resisting and why. The surface behaviour, silence, objections, slow uptake, is rarely the whole story. Respond to the behaviour instead of the cause and you'll usually make things worse, so diagnose first.
A simple diagnostic: match the response to the cause
When you notice resistance, ask yourself: what is this person actually telling me? Most resistance in early learning teams falls into one of four causes, and each needs a different response.
- Skill gap. The educator isn't sure they can do it. Signs: hesitation, avoiding the new task, asking the same question repeatedly, watching others rather than trying. Response: hands-on practice, a buddy, a short demonstration, and permission to be a beginner. Don't confuse a skill gap with attitude, telling someone to "just get on board" when they don't yet know how only deepens the fear.
- Workload and capacity. The educator believes there genuinely isn't time. Signs: "when am I supposed to do this?", comments about being stretched, tasks slipping across the board rather than just this one. Response: look honestly at what can be paused, simplified, or rostered differently. Acknowledge the load out loud before asking for more.
- Distrust or history. The educator has seen initiatives come and go, or felt unheard before. Signs: cynicism, "this will blow over", disengagement in meetings, referencing past changes that fizzled. Response: consistency over time, visible follow-through, and honesty about what happened last time. Trust is rebuilt through repeated small proofs, not one big speech.
A quick way to tell skill from will: offer support and see what happens. If resistance eases once the person feels capable, it was a skill gap.
Common resistance patterns in early learning teams
Some educators go quiet. They nod in meetings but don't engage, keep doing things the old way and wait for the initiative to pass.
Others are vocal. They point out problems and raise worst-case scenarios.
Some worry about their job or role: Will this change what I do? Will I still be good at it?
How to respond when staff push back
When someone pushes back, your instinct might be to defend the change or explain why they're wrong.
A few phrases you can use almost word for word:
- To open the conversation: "I'd really like to understand your concerns before we go further. What's worrying you most about this?"
- To check you've understood: "So the main concern is [repeat back what you heard], have I got that right?"
- To respond to a skill worry: "That's a fair concern. Let's pair you with someone for the first couple of weeks so you're not figuring it out alone."
Then actually respond to the concern. If it's implementation, offer training or support. If it's workload, problem-solve together.
Pushing back against resistance usually creates more resistance. Listening and responding to the real concern often dissolves it.
Building Leadership Support and Alignment
Your team watches how you lead through change. If you're uncertain, they'll be uncertain; if you're committed, they're more likely to commit. But alignment isn't a feeling you announce, it's built through deliberate steps before and during rollout.
Get the leadership team aligned before you announce
Before the initiative goes to the wider team, get your leadership group, room leaders, educational leader, nominated supervisor, anyone with influence, into one room (or one call) and work through three questions:
- What problem are we solving, in one sentence? If leaders can't say it the same way, your team will hear mixed messages and trust will erode.
- What are we genuinely unsure about? Name the risks and unknowns openly. Leaders who feel they have to pretend certainty become stiff and unconvincing; leaders who can say "here's what we don't know yet, and here's how we'll find out" sound credible.
- What will each of us do differently on Monday? Alignment lives in behavior, not agreement. Agree on the specific visible actions each leader will take in the first two weeks.
Write the answers down and share them. A one-page summary of the why, the known risks, and the first actions keeps everyone singing from the same sheet.
Be a visible sponsor, not just a supporter
Visible sponsorship means your team can see, hear, and feel your commitment, not just assume it. In practice that looks like:
- Being first to try it. Use the new process yourself, in front of your team, and talk about how it's going, including the clunky bits.
- Showing up at the point of change. Drop into rooms during the first weeks, not to check up but to help and to hear how it's really going.
- Speaking about it consistently. Mention the initiative in team meetings, in conversations, and in your own planning, so it's clearly a priority, not a passing idea.
Handle leaders who are unsure, honestly
If you have doubts about the change yourself, work through them before you ask your team to embrace it. That doesn't mean faking enthusiasm, it means being clear about what you're confident in and what you're still working out.
If a member of your leadership team is genuinely opposed, don't force them to front the change while unconvinced.
Keep alignment alive during rollout
Alignment drifts. A quick ten-minute leadership check-in each week during the first month, what's working, what's wobbling, what needs adjusting, keeps everyone consistent and catches problems before they reach the wider team. When leaders hear the same concerns from different rooms, that's a signal to adjust, not to push harder.
Creating a Culture That Embraces Change
The way your team responds to this initiative is shaped by your broader culture. If people feel safe, valued and included, they're more likely to embrace change.
Start building this now, even if the change is already underway.
When people feel they belong and their voice matters, they're willing to take risks, try new things and change.
Sustaining Adoption and Reinforcing Change
The first few weeks of a new initiative are exciting. Then reality sets in.
This is where most change initiatives fail.
Build reinforcement into your routines.
Make the new way easier than the old way.
Staff resistance to new initiatives is a signal, not a failure.
When you approach resistance with curiosity instead of frustration, you learn what your team actually needs.
At Child Care Leadership Hub, we work with leaders who are navigating exactly this challenge. If your team is struggling with a new initiative, or if you're finding that staff meetings feel disconnected and your messages aren't landing, the Culture Booster Cards are designed to help you have more meaningful conversations with your team about what's really going on.
Frequently Asked Questions
Why do staff resist new initiatives?
Staff resist new initiatives for several reasons: fear of the unknown, worry about extra workload, concern about losing control, or simply being tired of constant change. In early learning centres, educators often feel stretched thin already. When a new initiative arrives without clear explanation of why it matters or how it will actually work, resistance is natural. The key is understanding that resistance isn't personal, it's usually about uncertainty, not unwillingness.
How can leaders overcome resistance to change at work?
Start by being transparent about why the change matters and how it will benefit the team and children. Involve staff in planning from the start, listen to their concerns genuinely, and give them time to adjust. Provide clear training and support, celebrate small wins along the way, and acknowledge that change takes time. Most importantly, show your leadership team is committed too, staff watch what leaders do, not just what they say.
What should you say to staff who are resistant to change?
Listen first. Ask what their concerns are and why they're hesitant. Then explain the change rationale clearly, acknowledge their concerns as valid, and work together on solutions. Try something like: 'I hear you're worried about the extra time this will take. Let's talk about how we'll manage that' or 'I know change is hard. Here's why we're doing this, and here's how I'll support you.' Avoid dismissing their concerns or forcing compliance, that deepens resistance.
How do you introduce a new process without overwhelming your team?
Roll it out gradually rather than all at once. Start with a pilot group if possible, gather feedback, and refine before full launch. Build in training time and ongoing coaching. Reduce other demands temporarily if you can, so staff aren't juggling ten new things at once. Use your staff meetings to check in regularly about how it's going and what support people need. Small, supported steps beat big, sudden changes every time.
0 comments