Why Teams Struggle With Change (Even When They Buy the Right Technology)
- Paul Every
- Jul 30
- 5 min read
Part 1 of 4: Creating the Conditions for Success
A few years ago, the big technology conversation was about moving to the cloud. Today, it is about AI, automation and digital productivity tools. The technology has changed, but the underlying assumption often hasn't: if we buy the right tool, the work will improve.
It rarely works that way.
After many years, supporting technology-enabled change across different organisations, I've watched teams invest real time and money in new systems, only to find that months later, many of the original problems are still there. The technology itself is usually not the issue. More often, the team never created the right conditions for success before the project began.
That might sound surprising at a time when technology is advancing so quickly. New platforms promise greater efficiency and better collaboration. AI tools offer the prospect of saving hours of work every week. But technology, on its own, does not create value. Value comes from solving a real problem and helping people work differently. Technology is simply the enabler.
Start With the Problem, Not the Technology
One of the most common mistakes is starting with the solution rather than the problem. A competitor has adopted a new platform. A demo looked impressive. An AI tool appears capable of transforming productivity. Before long, the conversation is all about products, features and rollout plans.
What often gets less attention is the reason for the investment in the first place.
What problem is this actually solving? What outcome are we trying to achieve? How will the people doing the work, or the people you serve, benefit? And how will you know, once the novelty has worn off, whether it was worth it?
These questions can feel obvious, but they're frequently skipped. When that happens, teams can end up running new technology while making little real progress towards what they set out to achieve.
Why AI Makes This Easier to Get Wrong, Not Harder
AI adds a wrinkle the cloud migration wave didn't have.
Nobody accidentally provisioned a cloud server over lunch. But almost anyone can open an AI tool and start "using it" without ever answering the problem question. The barrier to entry has dropped so low that experimentation can look like progress, even when nothing is actually being solved.
If the answer to "what problem are we solving" is unclear, there's a real risk of a team ending up busy with technology rather than making progress with it. People pick up new tools, but without a clear line back to a genuine outcome, the benefits tend not to show up.
Clarity still comes first. Know the problem, know what success looks like, and let that guide the choice of tool, not the other way round.
Technology Change Is Really People Change
Another lesson worth repeating: technology projects are rarely technology projects. They're people projects that happen to involve technology.
Every meaningful change asks someone to work differently. New systems bring new processes and unfamiliar habits. Tasks that were once automatic can suddenly take concentration and effort again. Even when the change is genuinely for the better, there's usually a stretch of discomfort while people adjust.
This is where teams often underestimate the challenge.
Leaders can get frustrated when people seem to resist a change that looks obviously positive. But most resistance isn't irrational. People are trying to work out how it affects them, whether they'll get the support to do their job well during and after the change, and what happens if it doesn't go to plan.
Addressing those concerns early, and honestly, is one of the better investments a team can make. People support change more readily when they understand its purpose and feel confident they can still do good work once it lands.
A Short Example
I once worked with a business that automated a large chunk of its accounting process, expecting to remove most of the manual work within a quarter. Eighteen months on, the software was live and doing what it was built to do. What hadn't changed was that nobody had agreed, in operational terms, what "done" would actually look like, so nobody could say with confidence whether it had worked.
The tool had delivered. The business hadn't yet worked out what it meant by success.
That gap, between something going live and something delivering value, is where most of these projects seem to go wrong.
Leadership Still Matters More Than Software
Leadership plays a critical role here. Vendors bring expertise and implementation partners bring guidance, but neither can substitute for visible, engaged leadership from inside the organisation.
People look to their leaders for reassurance and direction. They want to know why the change is happening and why it matters.
When leaders actively champion the change, communicate consistently and stay involved throughout, the odds of success go up a lot. When change gets delegated entirely to a project team, an IT function or an external supplier, it quickly starts to feel like somebody else's initiative rather than a shared priority.
The teams that get the most value from technology aren't usually the ones with the biggest budgets or the newest tools. They're the ones who take time to get clarity before the project starts. They know the destination, and they treat technology as the way of getting there, not the point of the exercise.
A Few Questions Worth Asking
Before committing to a new CRM, process automation, cloud migration or AI programme, it's worth stepping back and asking:
What specific outcome are we trying to achieve?
How will this improve things for the people we serve?
How will it help our people do their jobs better?
What evidence will tell us, six or twelve months from now, that it was worth doing?
None of these are technical questions. They're often the difference between change that sticks and change that quietly disappoints.
Final Thoughts
As the pace of technological change keeps accelerating, the fundamentals stay remarkably stable.
AI may change how work gets done. New software may reshape a process. Automation may remove repetitive tasks. But successful change still starts with a clear understanding of the problem, a genuine picture of what better looks like, and a commitment to helping people make that journey.
Technology can support change. It can't create it on its own.
In Part 2, I'll look at why defining the problem is only the first step, and what it actually takes to turn it into requirements your team can work with.
Get the free guide
Most technology changes succeed or fail because of a handful of decisions made right at the start.
As a Rainwater Growth reader, you can get my guide, The 3 Disciplines That Make or Break Change, free. It sets out the three simple disciplines I use to keep technology change focused and delivering value.
Comments