Why Your Team Resists Change (Even When It’s a Good Idea)
You’ve found better booking software. Or a smarter way to handle client intake. Or a system that will actually save everyone time.
You announce it in a team meeting. Everyone nods.
Two weeks later? Half the team is still doing it the old way. The other half is confused. And you’re wondering why something so obviously better is meeting so much resistance.
Here’s the truth: change is hard – not because your team is stubborn, but because you’re asking them to give up something that works for something uncertain.
And without a clear plan to manage that transition? Most changes stall out, limp along, or quietly die.
Let’s explore why
Why People Resist Change (Even Good Changes)
1. The Old Way Feels Safer
Humans are wired to protect the status quo. We overvalue what we already do and fear losing control, competence, or certainty more than we value potential gains.
Translation: “The way we’ve always done it” isn’t stubbornness – it’s psychology.
2. Hidden Competing Commitments
Your receptionist agrees the new intake form is better – but it slows down her morning rush. She’s committed to being “fast and friendly,” and the change threatens that.
This isn’t an attitude problem. It’s a genuine conflict between two good things.
3. Change Fatigue Is Real
In recent years, employees have faced more simultaneous changes than ever. Research shows willingness to support change dropped from 74% to around 40% – meaning even good changes are hitting tired teams.
The lesson: Your team isn’t resistant. They’re exhausted.
Why “Just Roll It Out” Fails
Here are just some things that can happen when you announce a change without a plan:
❌ You tell people what to do, but not why it matters
❌ Training is shallow or nonexistent
❌ There’s no clear timeline or milestones
❌ Old shortcuts still exist, so people revert
❌ Nobody checks if it’s actually working
Research consistently shows: fewer than one in three change initiatives fully succeed – usually because leaders manage the installation (new software is here!) but not the adoption (people actually using it properly).
A Simple Change Plan for Small Service Teams (Using the ADKAR Model)
I’m certified in the ADKAR change management model – a proven framework used by thousands of organizations worldwide. It breaks change down into five individual steps that people need to move through: Awareness, Desire, Knowledge, Ability, and Reinforcement.
Here’s how to use it when you’re switching booking software, updating intake processes, digitizing checklists, or standardizing client handoffs.
Step 1: Build Awareness – Make the Case in One Page
ADKAR Step: Awareness (of the need for change)
What to include:
- The problem (what’s broken or inefficient now)
- Impact on customers or quality
- Risk of doing nothing
- One concrete goal (e.g., “Reduce double-bookings by 50% in 60 days”) and
- Benefits to them (easier – faster – less double handling etc)
How to share it:
10-minute team huddle. Read it out loud. Invite questions.
Why this matters: People need to understand why before they’ll commit to what. This is the foundation of ADKAR – without awareness of the problem, people won’t see why change is necessary.
Step 2: Create Desire – Identify Who “Loses” What and Offset It
ADKAR Step: Desire (to support and participate in the change)
Change always threatens something: speed, autonomy, tips, preferred routines, established expertise.
Map it out:
- What does this change threaten for each role?
- How can you offset it? (Better tools, training, recognition, schedule flexibility)
- Can respected peers (not just you) advocate for it?
Why this matters: This is where most owners skip ahead. If you ignore what people are giving up, they’ll resist – even if they don’t say it out loud. Desire doesn’t happen automatically just because the idea is good.
Step 3: Provide Knowledge – Show the Path, Don’t Just Tell It
ADKAR Step: Knowledge (of how to change)
Create a simple how-to:
- 5-7 steps with screenshots or a short video
- Two live demos for different shifts
- Clear “where to click” and “done looks like this” examples
Why this matters: Clarity shrinks fear. Vague instructions create anxiety. Knowledge is about giving people the information they need – not just telling them to “figure it out.”
Step 4: Build Ability – Run a Low-Risk Pilot First
ADKAR Step: Ability (to implement required skills and behaviors)
Don’t launch to everyone at once. Instead:
✅ Pilot with one person/team or one day per week
✅ Remove the old shortcuts during the pilot (retire old forms, disable old logins)
✅ Capture issues in a feedback log and fix them fast
Real examples:
Salon switching booking apps: Pilot with two stylists for two weeks. Reception double-enters walk-ins only during pilot. Measure no-shows and turnaround time. Retire old app after week two.
Clinic updating intake process: Start with one practitioner and two front-desk shifts. Use prefilled templates. Move to full roster once the error rate drops 50%.
Workshop digitizing safety checks: Run a new checklist on the first job of each day for 10 days. Once completion hits 90% for a week, expand to all jobs.
Why this matters: Knowledge is knowing what to do. Ability is actually being able to do it. Practice beats promises. A pilot proves it works and builds confidence through real experience.
Step 5: Apply Reinforcement – Lock It In
ADKAR Step: Reinforcement (to sustain the change)
Post a simple scoreboard:
“No-shows down 18%, wait times down 12 minutes”
Recognize the behavior weekly:
Shout-outs in huddles or team chats
Update the system:
Change SOPs, onboarding docs, and performance reviews so the new way becomes the way
Why this matters: This is the most skipped step – and why changes don’t stick. Without reinforcement, people quietly roll back to the old way when you’re not looking. Reinforcement makes the change permanent.
When to Get Help
Consider hiring a change coach or consultant when:
✅ You need structure fast (a coach brings proven frameworks)
✅ You’re mid-rollout and it’s stalling
✅ Your team is exhausted and change fatigue is real
✅ You want ROI, not just activity
A good coach pressure-tests your case, designs the pilot, and sets up reinforcement so the change actually sticks.
Quick Rollout Checklist
Copy this for your next change:
☐ One-page “why” with measurable target
☐ Map who loses what; offer offsets
☐ 5-7 step how-to + two demo
☐ 2-3 week pilot; remove old shortcuts
☐ Scoreboard + weekly recognition
☐ Update SOPs, onboarding, reviews
☐ Stagger changes; kill a low-value task when adding new ones
The Bottom Line
Change doesn’t fail because people are difficult. It fails because we skip the human part – the “why,” the offsets, the practice, the reinforcement.
When you treat change as a transition (not just an announcement), your team moves with you instead of against you.
And that’s when things actually improve – not just on paper, but in reality.
Need help rolling out change without the chaos? Join the waitlist for The Local Edge – where service business owners get frameworks, peer support, and coaching to implement change that actually sticks.
