Winning Support Before You Launch
- Paul Every
- 4 days ago
- 4 min read
Part 2 of 4: Why successful change starts long before the technology arrives
In the first part of this series, I looked at why change so often stalls even when the technology itself is sound. (TL;DR Successful change starts with a clear understanding of the problem you're solving, not with the platform you've chosen.)
My guide on The 3 Disciplines Behind Successful Change, can really help get that clarity.
Once that clarity exists, the next challenge emerges.
How do you bring people with you?
This is where many technology initiatives begin to drift. Not because the platform is unsuitable or the project poorly managed, but because the people expected to use the new system never fully buy into the change. By the time resistance becomes visible, the project is usually well underway; contracts signed, implementation started, deadlines agreed. At that point leaders are focused on delivery, and winning support is much harder once the change is already happening.
The organisations that manage this well understand that change management starts before implementation. In most cases, the quality of the implementation is largely determined by the quality of the preparation.
Why People Resist Change
When leaders talk about resistance, it's often framed as a problem to be overcome. In reality, it's a normal human response.
Most people have spent years building routines that let them do their job efficiently. They know where information lives, how processes work, who to ask when something goes wrong. Even imperfect processes are familiar, and familiarity is worth something.
A new CRM, a new way of collaborating, an automation tool or an AI system may offer real long-term benefit, but in the short term it introduces uncertainty. Uncertainty about workload, competence, and whether mistakes made while learning will be held against them.
One of the more useful lessons I've taken from project work is that resistance is often feedback, not obstruction. I recently worked with a financial services business, partway through a case management rollout, where staff pushback had been written off internally as "people don't like change."
When someone actually sat down with the team, the real issue was more specific: nobody had explained what would happen to the work that didn't fit neatly into the new system's workflow. The resistance wasn't an attitude problem, it was pointing directly at a gap nobody had designed for yet. Once that gap was addressed, the pushback largely disappeared.
Ignoring resistance rarely makes it go away. Understanding what it's telling you usually does.
People Need a Reason to Change
Many technology projects begin with a conversation about features and functionality — what the system can do, how it compares to competitors, what efficiencies it might create. Whilst useful, it rarely answers the question that matters most to the people who'll actually use it: why are we doing this?
People support change more readily when they can see how the proposed future is better than the current one. It might be faster customer response, less time lost to manual admin, information that's actually findable. When the problem is clearly named, the benefit of solving it becomes more obvious. Without that connection, a new system just feels like change for its own sake.
This is especially relevant as businesses explore AI tools. Many are introducing AI because they feel they should, rather than because they've identified a specific problem it addresses, and employees notice this difference immediately.
A clear purpose creates engagement. A vague aspiration creates scepticism.
Communication Is Not a One-Off Activity
Organisations often treat communication as announcing the project, then providing occasional updates.
Effective communication is more than that. People absorb information differently and at different speeds. Some grasp the benefit immediately, others need time to process, ask questions, and understand what it means for them personally, which means leaders need to communicate repeatedly and consistently through the whole lifecycle, not just at the start.
The content matters too.
Employees are usually less interested in technical specification than in practical outcomes: what's changing, why, what support looks like, and what success actually means for them and for customers.
The simplest messages tend to travel furthest.
Why AI Faces Exactly the Same Challenge
Much of the current conversation about AI focuses on the technology itself; new capability appearing weekly, businesses keen to explore what's possible. But from a change perspective, AI presents the same challenges organisations have faced for decades.
People still need to understand why it's being introduced, still worry about the effect on their jobs, and still need training, support, and confidence that it will help rather than simply add work.
The organisations getting the most from AI are rarely the ones deploying the most tools. They're usually the ones best at helping people see where it genuinely adds value. The technology is new. The human dynamics aren't.
Winning Support Is a Leadership Responsibility
Suppliers, consultants and project teams can all help facilitate change, but winning
support ultimately sits with leadership. Employees look to leaders for direction during uncertainty, and want confidence that the organisation has thought through the impact on the people involved, not just the delivery timeline.
Every significant change hits obstacles — systems behave unexpectedly, timelines slip, new ways of working take longer to bed in than planned. When people trust the leadership team and understand why the change is happening, those obstacles are far easier to work through. When they don't, a technical hiccup can turn into a credibility problem for the whole programme.
Final Thoughts
Technology change often fails long before a new system goes live. Not because the software is wrong, or the plan is flawed, but because too little was invested in building understanding and support before implementation began.
For a regulated or client-facing business, that's not just wasted spend. It's disruption without progress, and the kind of failure that's harder to recover from than an obvious one.
The strongest projects are built on clear purpose, consistent communication, and genuine engagement long before the first login screen appears.
Get the free guide
Many change initiatives succeed or fail before implementation even begins, so if you are planning a significant business or technology change, download my free guide:
It provides a practical framework to help leaders define value, create focus and establish accountability before investing time and money in the wrong solution.
Comments