Back to Articles

Picture the scene. Your organization has just rolled out a new electronic health record system. Or a new donor management platform. Or a "revolutionary" project tracking tool that the executive team is very, very excited about. The vendor demo was slick. The sales rep was charming. There were slides with upward-pointing arrows. Everyone nodded along.

Then came the actual rollout. And now, three months later, your best nurse is still scribbling on paper and photographing her notes with her phone. Your most experienced fundraiser is running the entire donor database out of a personal Excel file she keeps in a folder called "DO NOT DELETE LISA." Your operations manager has found seventeen creative ways to avoid logging into the new system without technically refusing to log into the new system.

You are not alone. This is, in fact, one of the most universal experiences in modern organizational life — right up there with "the meeting that could have been an email" and "the printer that only works when nobody needs it." Every year, organizations across healthcare, nonprofits, and business invest enormous sums in new technology, only to watch it quietly gather digital dust. The tool usually isn't the problem. Neither are the people. The problem, almost always, is how the whole thing gets introduced.

The good news: this is fixable. Here's how.

First, Let's Be Honest About Why This Happens

Before we can solve the problem, it helps to understand what's actually going on inside the heads of the people who are resisting. Because it's almost never what it looks like on the surface. It doesn't look like much. It looks like someone "just prefers the old way." But underneath that? There's usually a tangle of completely reasonable human feelings.

Take competence. Your veteran ER nurse has spent twenty years developing the kind of skill that looks like instinct — she can chart, triage, and hold a conversation with a frightened family member simultaneously without breaking a sweat. She is excellent, and she knows it, and her colleagues know it. Now you're asking her to feel like a confused intern again while she figures out where the button went. That's not a small thing to ask.

Or take your longtime fundraiser at a nonprofit. She has cultivated donor relationships for a decade using a system that, yes, runs on software from the early Obama administration and occasionally makes the IT person wince. But she knows it cold. Every workaround, every quirk, every field that says one thing but means another. Asking her to abandon that for something new is asking her to trade expertise she's proud of for beginner's frustration — at least temporarily.

Psychologist Guy Winch has written about how for many people, the fear of failing in front of others is powerful enough to override even their desire to succeed. The result isn't dramatic defiance. It's quiet avoidance. Suddenly there's always a reason to deal with the new system tomorrow.

There's also a quirk of human psychology that behavioral economists call hyperbolic discounting — which is a very academic way of saying that our brains are terrible at caring about future rewards when present pain is involved. The efficiency gains promised by the new EHR system are six months away and feel abstract. The frustration of not being able to find the medication reconciliation tab is happening right now, to a real patient, in real time. The brain votes for familiar every time.

And then there's the fear people rarely say out loud: "Is this technology eventually going to replace me?" This anxiety has grown considerably in the age of AI, and it cuts across every sector. Nurses worry about clinical AI. Social workers worry about automated case management. Grant writers worry about AI-generated proposals. A Gallup survey found that 22% of U.S. workers now worry about technological obsolescence — up from 15% just a few years ago. When leadership rolls out a new system without ever addressing this concern, the silence doesn't read as reassurance. It reads as confirmation.

Strategy One: Answer the Question Everyone Is Too Polite to Ask

There is a question sitting in the back of every employee's mind during every technology rollout, and it goes like this: "Okay, but what does this mean for me? Specifically. On my actual Thursday." Not for the organization's strategic objectives. For me.

This is not selfishness. This is how human beings work. And yet most technology announcements are written in a language that speaks almost entirely to the organization and almost not at all to the person reading it.

Compare these two announcements: "We are implementing a new integrated care coordination platform to improve outcomes data, reduce redundant documentation, and align with upcoming regulatory requirements." Versus: "We're rolling out a new system that will cut your end-of-shift charting from 45 minutes to about 15. Yes, we checked. Yes, that math is real."

Both describe the same software. Only one of them will get a nurse's attention. Before any announcement goes out, make a list of every group of people who will be affected. Then ask, for each group: what specific annoyance goes away? What gets genuinely easier? Lead with that. The strategic benefits can go in paragraph three.

Strategy Two: Say the Quiet Part Out Loud

A community health center in the Midwest rolled out a new AI-assisted documentation tool. The technology was solid, the training was thorough, and adoption was... polite. Technically people were using it. But just barely, and with the energy of someone eating a salad they didn't order.

A consultant brought in to assess the situation did something simple: she asked the staff, one on one, what was really going on. The answer, almost universally, was some version of: "I'm worried this is the beginning of the end for my position." Nobody had said this in a meeting. Nobody had sent an email. It was just there, quietly poisoning the rollout.

Once the medical director held an open forum — here's what this tool does, here's what it doesn't do, here's how we see your role evolving, and here's our commitment to your development — adoption jumped dramatically within weeks. Same technology. Same training. Completely different conversation.

Silence on job security doesn't communicate "there's nothing to worry about." It communicates "we'd rather not discuss it." Those land very differently. Gallup data shows that 48% of American workers say they'd switch employers for one that offered better skills training. People aren't afraid of growth. They're afraid of being left behind while growth happens around them. There's a difference, and it matters.

Strategy Three: Let People In Before the Decision Is Final

Here is a tale of two hospital systems going through almost identical EHR transitions at the same time. Hospital A did it the traditional way: selected the system, negotiated the contract, configured the build, and then announced it to clinical staff about six weeks before go-live. Training was provided. A help desk was staffed. The rollout was, technically, successful. Nurses used the new system. They also complained about it continuously for the better part of a year and developed a rich vocabulary of colorful phrases reserved specifically for the medication ordering workflow.

Hospital B took a different approach. Eight months before launch, they pulled together a "clinical advisory group" — a mix of nurses, physicians, a social worker, a unit clerk, and two people who were known skeptics and weren't going to pretend otherwise. This group helped configure the system, tested workflows, broke things in useful ways, and got to complain productively during the build rather than powerlessly after launch.

On go-live day at Hospital B, those eight people were the ones walking the floors, answering questions, reassuring nervous colleagues. They'd helped build this. They were proud of it. Adoption was faster, complaints were fewer, and the medication ordering workflow was actually designed to make sense — because a bedside nurse had told the implementation team, very clearly, what the previous design was doing wrong.

Strategy Four: Train People Like Adults, Not Like Software Users

The gold standard of bad technology training goes something like this: a two-hour Zoom call, a slide deck with 94 slides, a walkthrough of every single feature the system offers, and the phrase "feel free to reach out if you have questions" delivered to 200 people who are all secretly hoping this is all a bad dream.

People learn new tools the same way they learn most things: a bit at a time, when it's relevant, with enough room to make mistakes privately before the stakes are high. The best training programs start with what people will actually do on day one — not the full feature set, just the basics needed to function. They use real scenarios pulled from the actual work: not "Imagine you need to update a patient record" but "Here is exactly how you document a medication change for a patient who's being discharged this afternoon."

One organization's communications tool launch featured a "Guess Who?" game where staff used the new platform to post clues about a mystery colleague. Adoption happened almost by accident, while people were busy having fun. And always, always offer something people can come back to — a short video, a one-page reference card, a colleague who has volunteered to be the "go-to person." Because six weeks after training, when someone can't remember how to run a specific report, no one is reopening that 94-slide deck.

Strategy Five: Reward the Brave Ones

Let's be straightforward about what you're actually asking of your staff when you introduce new technology. You are asking them to be slower, more confused, and more frustrated than usual — for a period of time that nobody can specify with precision — in exchange for benefits that are mostly theoretical until they aren't. That is a real ask. It deserves real acknowledgment.

Incentives help close the gap between present pain and future reward. They don't have to be elaborate. A gift card, a half-day off, a genuine public thank-you from someone senior — these small gestures signal something important: we see what you're doing, and we're not taking it for granted. Public recognition, it turns out, often works better than money.

One nonprofit created a "Digital Champion" program — a voluntary designation for staff who adopted the new system early and helped their colleagues do the same. No extra pay. Just recognition, a small badge on their internal profile, and the general understanding that they were doing something admirable. The waiting list to join eventually grew longer than the original cohort.

Strategy Six: Make It Okay to Be New at Something

Here is a hidden barrier that almost never makes it into the change management literature: a lot of people resist new technology not because they can't learn it, but because they're embarrassed to be seen learning it. This is especially pronounced in high-stakes environments. A physician who is accustomed to being the most competent person in the room does not love feeling confused about where the ordering screen went.

When the culture around a rollout is one of quiet judgment — where struggling signals weakness — people fake competence. They find workarounds. They avoid the new system in the ways that are least visible. The fix is remarkably simple and requires exactly one brave act from leadership: go first.

When a department chief says, in a team meeting, "Honestly, I spent fifteen minutes yesterday trying to find the lab results tab and finally had to ask someone — here's what I learned," something shifts in the room. Suddenly the social cost of not-knowing drops for everyone else. Suddenly it's safe to raise your hand. Celebrating small wins — a team that figured out the new reporting feature, a staff member who helped three colleagues in one afternoon — builds momentum in a way that no training deck ever will.

Strategy Seven: Keep Talking After the Ribbon Is Cut

The single most reliable way to derail a technology rollout is to treat launch day as the finish line. It isn't. Launch day is more like the opening night of a play that will run for years.

Before launch, communicate early and often. Tell people what's coming, why it's coming, and — crucially — be honest about the fact that there will be a learning curve. "This will be seamless" is a promise that technology almost never keeps. "This will be an adjustment, and here's how we're going to support you through it" is a promise you can actually keep, and people will remember that you did.

During rollout, share wins as they happen. Not invented wins. Real ones. The billing team that cut their processing time in half. The program officer whose grant report took two hours instead of six. The floor nurse who says she's actually leaving on time now. Real stories from real people make the promise feel tangible to the people who aren't there yet.

After launch, keep asking "what's still hard?" — and then actually do something with the answer. Organizations that sustain high adoption long-term are the ones that treat the rollout as the beginning of an ongoing relationship with the technology, not a project to close out and move on from.

The Actual Point of All of This

None of the strategies in this article are particularly complicated. You don't need a change management certification or a consulting budget to use them. What they all have in common is something much simpler: they take seriously the fact that the people using the new technology are human beings with expertise, anxieties, busy days, and a reasonable desire to feel like their experience matters.

When people feel that — when they feel like the organization actually cares whether they can do their jobs well, not just whether the system is technically live — something interesting happens. They stop looking for reasons the new thing won't work and start looking for ways to make it work.

That flip is worth more than any feature on the vendor's slide deck. Whether you're running a hospital unit, a community foundation, or a mid-sized logistics company, the same human dynamics apply. People aren't resistant to getting better at their jobs. They're resistant to feeling like they don't matter in the process of change. Give them a reason to matter, and you'll be surprised how quickly "DO NOT DELETE LISA" becomes a folder she's happy to archive.