← All reads
Innovation·May 11, 2025

How to adopt new technology without scaring your team

New tools don't fail because of the technology, but because of how they're introduced. Four proven frameworks to get your team to embrace change instead of resisting it.

How to adopt new technology without scaring your team
Imagen: Unsplash

You bought a new tool. It works, it's good, it'll save you hours. And yet, two weeks later, nobody uses it. Your receptionist is still on the notebook, your stylist "prefers the old way," and you wonder if you threw the money away.

You're not alone, and it's not the technology's fault. Decades of change-management research say the same thing: tools don't fail because they're bad, they fail because of how they're introduced. The good news is there are proven ways to do it right.

Why people resist

The consultancy McKinsey sums up the field's most-cited figure: "70 percent of change programs fail to achieve their goals, largely due to employee resistance and lack of management support." Take that number with a grain of salt (it's a debated estimate, not a law), but the lesson holds: most changes trip over people, not software.

And why do they resist? Almost always fear. Fear of looking bad, of not understanding the tool, of "the machine" taking their job. If you don't name those fears, they win.

It's worth taking that 70% with a grain of salt: a 2011 academic study found no empirical evidence behind the exact figure. But the underlying pattern is real and shows up across all the serious research: most changes trip over people. So you don't need to believe in a magic number to take the practical lesson that the human side is where you win or lose.

ADKAR: change happens person by person

The ADKAR model, from the firm Prosci, starts from a simple idea: an organization doesn't change until its people do, one by one. It's five steps in order.

  • Awareness: each person understands why the change is needed, not just that it's happening.
  • Desire: they want to take part, rather than feeling forced.
  • Knowledge: they know how to use the tool, with real training.
  • Ability: they can actually do it, practicing until they master it.
  • Reinforcement: something sustains the change so no one drifts back to the notebook.

For a small business, ADKAR is practical because it tells you exactly where people get stuck. If no one uses the tool, ask yourself: is awareness missing (they don't know what it's for)? Desire (they don't want to)? Knowledge (they don't know how)? Each blocker has a different fix.

Kotter: the leader's 8 steps

If ADKAR looks at each person, John Kotter's 8-step model looks at the leader and the organization. It's the sequence you, as the owner, should follow.

  • Create a sense of urgency.
  • Build a guiding coalition.
  • Form a strategic vision.
  • Enlist a volunteer army.
  • Enable action by removing barriers.
  • Generate short-term wins.
  • Sustain acceleration.
  • Institute change.

Kotter warns about something valuable for anyone in a hurry: "skipping steps creates only an illusion of speed and never produces a satisfying result." It's tempting to install the tool Monday and demand its use Tuesday, but that shortcut almost always ends in abandonment.

For a small business you don't need to apply all eight steps to the letter or set up committees. The essence, translated to your reality, is this: make sure people understand why it's urgent, get your trusted people on board, set a clear direction, remove the obstacles (bad wifi, an old phone, a password no one remembers), and make the first win show up soon and get celebrated.

What to do in practice

Translating both models to a service business leaves a concrete, manageable recipe.

  • Explain the why first. Before you touch a button, tell them what problem the tool solves for them, not just for you.
  • Involve them early. Ask the people who'll use it for input. Whoever helps decide defends the result.
  • Start small, with a pilot. Try it with one person or one shift before forcing it on everyone.
  • Train for real. A real session, patience with mistakes, and someone to ask.
  • Celebrate the first wins. When the tool saves the first afternoon, say it out loud.
  • Address the fear of layoffs head-on. Explain that the tool takes the tedious work so they can do the valuable work.
Skipping steps creates only an illusion of speed and never produces a satisfying result. — John Kotter, Harvard Business Review

The most common fear: "I'll be replaced"

When something like an AI that books appointments shows up, the team's first thought is usually "so what am I here for?" Ignoring that question is the most expensive mistake. The honest answer is almost always that the tool eats the repetitive tasks, not the person: less copying data by hand, more quality attention for the customer already in front of them.

When you position technology as relief rather than threat, the team stops hiding from it and starts leaning on it.

One gesture that helps a lot is giving them a voice from the start. Ask your receptionist which part of her day she hates, which tasks feel like a waste of time. When the tool arrives to solve exactly what she pointed out, it stops being something you imposed and becomes something she asked for. That difference in origin, between "it was forced on me" and "I asked for it," completely changes whether she defends it or sabotages it.

Takeaway

New technology isn't won by force. It's won by explaining the why, involving people early, training with patience, and celebrating the first wins. ADKAR tells you where each person gets stuck; Kotter gives you the order of the steps. And above all: name the fear before it beats you.

Sources

  • Kotter International — https://www.kotterinc.com/methodology/8-steps/
  • Prosci — https://www.prosci.com/methodology/adkar
  • Harvard Business Review — https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2
  • McKinsey — https://www.mckinsey.com/featured-insights/leadership/changing-change-management
  • McKinsey — https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/how-to-double-the-odds-that-your-change-program-will-succeed
Share