And it has nothing to do with the technology.
You selected the right system. The vendor passed your evaluation criteria. The contract is signed, and the go-live date is in the calendar.
Three months later, half your team is still working from the old spreadsheets.
This is the most common and costly pattern in technology project delivery. The software works, the implementation technically succeeded, but the people who were supposed to use it every day never adopted it. A system nobody uses is just an expensive subscription.
The instinct is to blame the technology, the timeline, or the vendor. The evidence points somewhere else entirely.
Prosci’s Best Practices in Change Management research, drawing on responses from more than 2,600 change practitioners, found that projects supported by excellent change management meet or exceed their objectives 88% of the time. Projects with poor change management succeed only 13% of the time. That gap has nothing to do with the quality of the software. It has everything to do with whether the people inside the organisation were genuinely brought along.
“Projects fail largely because stakeholders aren’t engaged, communications aren’t appropriate or regular, and change isn’t managed. People fear change, and if you don’t get them on board and keep them on board, they become anti the change.” — Mark Birkinshaw, Tango
Why Resistance Is Not a Character Flaw
When employees push back on a new system, the temptation is to label them as difficult or stuck in their ways. That framing misses what is actually happening and makes the problem significantly worse.
For many experienced employees, competency in existing systems is tied directly to their professional identity. When a new platform arrives, that hard-earned expertise is reset overnight. The anxiety this produces is a predictable human response to a genuine threat that requires management.
Among employees experiencing high change fatigue, only 43% intend to stay with their organisation — compared with 74% of those whose organisations manage change well. (Source: Gartner, 2022.)
You Cannot Manage What You Have Not Mapped
Not everyone in an organisation experiences change the same way, holds the same influence over how a project lands, or needs the same type of communication. Treating the workforce as one audience is one of the most common mistakes in project delivery.
Tango starts every change engagement by mapping stakeholders, identifying who holds formal decision-making power, who holds informal influence over their colleagues, and who will feel the impact most directly in their daily work. Each group gets a different approach, a different messenger, and a different level of involvement.
In almost every organisation, there is someone highly experienced and openly sceptical about the new system. Their colleagues watch them carefully before forming their own views. The instinct is to manage them from a distance. The better approach is the opposite.
“A good change manager identifies the troublemakers and gets close to them. If they’re negative, they’re making life hard for the person they’ve just become friends with. And when they convert, and they do, everyone else follows.” — Mark Birkinshaw, Tango
Bring the most vocal resistor in early as a pilot user, a tester, or a genuine sounding board. When they come around, their endorsement carries more weight than any all-staff communication ever could.
The Most Important Conversation Is the One Nobody Has in the Meeting
In almost every technology project, the all-staff update goes out, the town hall is held, and the project board marks communications as complete. A significant portion of the workforce sits with questions they will never ask in a formal setting, because admitting you do not understand something in front of colleagues carries a social cost most people are not willing to pay.
Those questions do not disappear. They become errors, workarounds, and the reason someone quietly reverts to the spreadsheet three weeks after go-live.
Awareness of a change is not the same as willingness to embrace it. Willingness is built through direct, personal conversations that address what the change means for that specific person in their specific role. One honest conversation with an apprehensive team member is worth more than a hundred all-staff updates.
It is also why in-person presence at critical project moments matters in ways that video calls cannot replicate. On a video call, you cannot see the hesitation that signals someone has lost confidence, and you cannot have the quiet corridor conversation after the meeting ends. Remote delivery is efficient, but the moments that determine whether a project actually lands almost always happen in person.
When the System Goes Live, Be in the Room
Go-live is the moment of maximum anxiety. The new system is live, the old one is gone, and the support available to most users is a helpdesk queue. Under those conditions, many people do not push through the friction. They find a workaround, the habit forms within days, and the organisation ends up running two systems instead of one.
Tango’s approach at go-live is to have change managers physically present and moving through the workspace, observing how people interact with the system under real-world conditions and catching moments of hesitation before they become embedded patterns.
One of Tango’s change managers recently led a go-live for a team of fifteen experienced, opinionated, and sceptical professionals. She was on site one day a week throughout the project, because that team needed a physical, trusted presence to feel safe enough to ask the questions that mattered. The system was adopted, and the project delivered.
One caveat worth noting: physical presence only works if the identified problems are actually resolved. Turning up and failing to act on what you find creates more cynicism than not turning up at all.
Before Your Next Project Goes Live
Most organisations scrutinise the technology side of a project carefully. The human side rarely gets the same attention. Before your next deployment, ask honestly:
- Does every stakeholder group have a tailored communication plan?
- Have you identified the informal influencers in each team and engaged them early?
- Is your change and communications plan running parallel to the technical timeline?
- Is there someone whose specific job is to be physically present at go-live?
- Are any underlying HR or cultural issues being addressed separately, rather than left for the new system to resolve?
The difference between a project that delivers and one that quietly deteriorates is rarely found in the software. It is found in whether the people who had to change were given the support and presence to do so.
