Why don’t teams embrace new tech?

Read Time: 4 Minutes

You roll out shiny new software… and your team still sneak back to their spreadsheets. It’s not the tool. It’s the way it was introduced.

Sound familiar?

Most of the time, it’s not that your team won’t use the new tech. It’s that they’re not being led through it properly.

This week, we’re digging into why adoption stalls, and how simple things like digital adoption platforms (DAPs) and smart onboarding can help new tools stick.

Here’s what we’ll cover:

⚙️ People don’t hate software, they hate change

🚀 What actually helps tools stick?

🔑 Real example: From “No thanks” to “Can we get more?”

This week we got the team together for our quarterly strategy day.

We stepped back from delivery and looked hard at our own constraints; tech, model, market, systems, processes.

It’s never comfortable, but it’s always valuable. Because the truth is, the tools aren’t usually the problem. It’s how we use them.

That’s true for us, and it’s true for our clients.

Teams don’t resist new tech because they’re stubborn. They resist because the rollout doesn’t make them feel supported, confident, or clear.

And that’s exactly what this week’s newsletter is about 👇

People don’t hate software, they hate change

The tech might be brilliant. But if using it makes people feel stupid, confused or behind… they’ll find a way around it.

Adoption doesn’t fail because people are lazy. It fails because:

• The onboarding is rushed

• The help is hard to find

• The value isn’t clear (fast enough)

Nugget #1: Tools don’t fail. Onboarding does.

What actually helps tools stick?

We bake this into every build, because we’ve learned it the hard way: tech without a people plan is pointless.

Here’s what works:

✅ In-tool guidance — little nudges that help users do the next step

✅ Lightweight onboarding — a 2-minute video, a click-through tour, or even a cheat sheet

✅ Real-world scenarios — training people how they’ll actually use it, not how it works in theory

✅ Feedback loops — asking “What’s still confusing?” and fixing it fast

These don’t have to be full DAPs (like Whatfix or Pendo); even a basic walkthrough can make a world of difference.

Nugget #2: Adoption happens when people feel guided, not dumped in.

Real example: From “No thanks” to “Can we get more?”

One of our clients rolled out a new workflow system. It was slick, custom-built, and ticked all the boxes.

Two weeks after rollout, the client’s shiny new system was gathering dust. No one was logging in. No one wanted to be the first to get lost.

We jumped in and added:

• Contextual tooltips for common steps

• A built-in “how to” tab with quick answers

• A weekly Slack reminder with one tip or shortcut

Uptake doubled in a month.

By month two, people were asking for more features, because they were finally comfortable with the basics.

Nugget #3: Adoption isn’t an event. It’s a habit you build.

What Can You Do Today?

🔹 Ask your team: “What tools do we have, but barely use?”

🔹 Review the onboarding; is it clear, useful and human?

🔹 Pick one feature and ask, “How could we make this easier to understand?”

It’s not just about the tech. It’s about helping people win with it.

P.S. If you’ve got a system gathering dust, don’t scrap it. Let’s fix the adoption problem before it becomes a write-off.

Need a fresh perspective on your software? I’m here to help. Book a 1-1 call with me, and we’ll figure it out together.

Do you know somebody else who could benefit from The Automation Advantage?

Before You Go…

How did you enjoy this email? I really value your honest feedback.

🔥 It was AWESOME!

🔥 Very good!

🔥 Okay!

🥶 Needs work!