The technology is not the transformation

The system was live. The value was not.

A little over a year ago, I was working with a client in the pharmaceutical sector whose CRM platform had already been implemented. Adoption was poor even at the level of basic system use. Unsurprisingly, the value delivered, and therefore the return on investment, was well short of expectations.

As we explored what was happening, the underlying problem quickly became clear: the platform had been implemented, but the transformation it was meant to enable hadn’t taken place. I have seen this repeatedly across ERP and CRM programmes: the technology goes live, while the organisational and behavioural changes needed to create value are left undone.

Implementing technology and creating value from it are not the same. We have known that for years, yet familiar beliefs and delivery behaviours keep pulling leadership attention back towards the platform, the plan and go-live, as if the benefits will follow automatically.

Four leadership failures repeatedly widen the gap between implementation and value. I’ve explored each one in more detail below:

1. Treating implementation as the result: a successful go-live can still leave most of the value untouched.
2. Assuming people will share the organisation’s view of what is useful: you cannot tell people what should matter to them.
3. Allowing leadership decisions and behaviours to contradict the stated purpose: your transformation story is only as credible as your decisions and behaviours.
4. Mistaking interest or compliance for adoption: interest is not adoption; changed behaviour is.

If you are accountable for the return on a significant technology investment, recognising these failures matters. They can determine whether your organisation builds valuable new capability or simply installs expensive software.

For this client, the salespeople understood what the CRM was and what they were being asked to do, but they couldn’t see how it would help them do their jobs better. From where they stood, the change could easily be understood in terms of what they were losing: more administration, pressure to share valuable contacts and information they had built up over many years, and another management system that might be used to monitor what they were doing. Those concerns weren’t necessarily unreasonable because the costs felt immediate and personal, while the benefits felt distant and largely organisational.

Yet most of the salespeople cared deeply about doing a good job. They wanted to bring genuine value into conversations with their customers and were often frustrated when they couldn’t do more to help. Further along that chain were people whose lives could be improved through better health outcomes, and that was the transformation the CRM was meant to support. The technology could help salespeople understand their customers better, make more relevant connections and bring the right information into important conversations, helping the company serve those customers more effectively and ultimately make a more meaningful difference to people’s lives.

When that connection began to emerge, people started leaning in and becoming curious because the change had become relevant to them and their world. For the Head of CRM, it confirmed something his instinct was already telling him: the challenge wasn’t simply to persuade people to use the system, but to make its purpose relevant to the people whose behaviour would determine whether it created any value.

1. A successful go-live can still leave most of the value untouched

Technology matters. It may create capabilities that were previously impossible, provide better information, remove waste or allow people to work in fundamentally different ways. None of those possibilities, however, creates value simply because the system is available. The chain from implementation to value is straightforward but too often compressed: implementation creates capability, adoption turns that capability into changed behaviour, and changed behaviour creates the possibility of better organisational outcomes. If you treat the first step as the finished result, the gaps between them become much harder to see.

An ERP platform can enable better decisions, but the transformation happens when people trust the information and use it differently. A CRM can enable stronger customer relationships, but the transformation happens when people share knowledge, improve conversations and make those relationships less dependent on individual black books. AI can enable people to analyse, create and decide more quickly, but the transformation happens through the way work, judgement and capability are redesigned around it. A review of digital-transformation research describes this as organisational change triggered by digital technologies, bringing together both a technology-centred and an actor-centred perspective. (Management Review Quarterly) The distinction is important because it stops us treating installation as transformation.

Go-live tells you the technology is available. It does not tell you that the investment is creating value.

2. You cannot tell people what should matter to them

Leaders often describe transformation through the technology at its centre. They talk about the ERP programme, the new CRM, the data platform, the AI implementation or the approaching go-live date, all of which makes perfect sense to the people responsible for delivery. Elsewhere in the organisation, those descriptions may mean very little. Even people close to the programme can see it as “just a new system”, something replacing something else, and miss the wider transformation completely. Some will never use the platform directly, while others will experience it mainly through changes to processes, decisions, responsibilities or working relationships.

When people understand what is being implemented but cannot see what should become better, they create their own explanation from the signals around them. They may see additional administration without any corresponding benefit, greater management control or a route to lower headcount. This is particularly acute with AI, where a message about efficiency may sound positive in a board presentation while being heard elsewhere as a warning about jobs and future relevance.

Research into technology acceptance has long recognised the importance of perceived usefulness. Fred Davis’s original studies found that people’s perception of whether a system would improve their job performance was more strongly associated with intended and reported use than perceived ease of use alone. (MIS Quarterly) The important word is perceived. Usefulness cannot simply be declared by the programme team because it has to become credible from the perspective of the people being asked to change. A leadership team might see a CRM as a route to better information, stronger customer relationships and a healthier business, while a salesperson initially experiences it as extra work and the loss of something that has previously helped them succeed. Both perspectives can be true.

That is why involvement cannot be reduced to presenting a finished answer and inviting comments. A systematic review of employee participation in digital transformation found that the quality of the process, the time and information available, and whether people’s contributions are genuinely taken up all matter. (Journal of Organizational Change Management) People can usually tell the difference between helping to shape a better way of working and being asked to validate a decision that has already been made.

If you talk only about what the organisation will gain while people experience only what they may lose, the official story will not win by default.

3. Your transformation story is only as credible as your decisions and behaviours

A change or communications team can help develop the narrative, organise engagement and make complex information easier to understand, but it cannot make the transformation meaningful on your behalf. People pay attention to what you repeatedly discuss, the questions you ask, the decisions you make and the trade-offs you are prepared to defend. You may describe a programme as an investment in better customer service, but if every decision points towards cost reduction, people will form their own judgement about the real priority.

This is where motive matters. Ideally, the intention is to take talented people and magnify their impact with better tools. Technology can remove repetitive work, make expertise more accessible and allow people to spend more time on the judgement, relationships and creativity through which they create the greatest value. Where that is your ambition, you have to make it visible: what work will people no longer need to do, where will their time and capability be redirected, and how will the organisation help them succeed?

Sometimes market conditions or the economics of the investment mean roles will change or fewer people may be needed. If that is the genuine intention or a credible possibility, you need to open the conversation rather than trying to disguise it. People will already be reading decisions, budgets and behaviour for clues, so silence doesn’t prevent them reaching the conclusion; it simply leaves them to do so without context, often assuming the worst. A thoughtful conversation, handled at the right time and within the appropriate legal, employee-relations and confidentiality boundaries, may be uncomfortable, but it is far more credible than talking about empowerment while every other signal points towards headcount reduction.

That doesn’t mean you need to have all the answers. People don’t expect you to know everything about the future, but they do expect you to be honest about what is known, what remains uncertain and what is driving the decisions being made.

You make the transformation credible when you connect everyday choices to the longer-term outcome, explain why a short-term compromise is necessary and remain open about what you are learning. An experimental study involving 815 participants found that people-oriented leadership helped buffer some of the unfavourable employee responses associated with a strongly task-oriented approach to digital transformation. (Journal of Business Research) That doesn’t mean softening every message. It means treating people as participants in an organisational transformation rather than users who need to comply with a technical implementation.

4. Interest is not adoption. Changed behaviour is.

When people begin to see how a change connects with something they care about, the conversation often feels different. They lean in, become curious and start exploring what the change might mean for their customers, colleagues and work rather than focusing only on what is being imposed on them.

That shift is useful, but you should not mistake it for the result. A positive conversation doesn’t prove that people will use the technology consistently, change established habits or improve organisational performance. Even compliance can disguise the gap: people may attend training, complete required fields and follow a process while the system remains separate from how they think about doing good work.

The test is what becomes different afterwards. Are people using the information to make better decisions? Are customer conversations improving? Are old workarounds disappearing? Is knowledge being shared where it was previously held by individuals? Are the expected operational or customer outcomes beginning to move?

Those measures will vary by programme, but the principle does not. If the evidence stops at attendance, system access or positive feedback, you know that activity has taken place. You do not yet know that transformation has occurred.

Start with the value, then work backwards

Before your next programme update or go-live communication, remove the platform name and ask what is genuinely meant to become better. The answer needs to be more specific than “improved efficiency” or “better customer experience” because broad aspirations give people little to recognise and give you little to measure.

Make the intended value observable. Which customer conversation should improve? Which decision should become easier or better informed? What recurring frustration should disappear? What work should people no longer need to do, and what should become possible with the time, information or capability released?

Then work backwards through the conditions required to create that value:

1. Define the changed outcome. Describe what customers, colleagues or the organisation should experience differently.
2. Identify the behaviour behind it. Be clear about what people will need to start, stop or do differently for that outcome to become possible.
3. Explore the change from where people stand. Understand what currently helps them succeed, what gets in their way, what they fear losing and where the technology could genuinely improve their work.
4. Align leadership decisions and signals. Make sure priorities, trade-offs, investment and behaviour reinforce the purpose being communicated.
5. Measure movement towards value. Track changes in behaviour, working practices and outcomes, not only implementation activity.

Technical communication still matters. Around go-live, people need precise information about what will happen, what they need to do, what they should avoid and where they can get help. The problem begins when implementation language becomes the whole transformation story.

The argument is simple. A system can be delivered without the organisation becoming more capable, customer relationships improving or the expected value being realised. Closing that gap requires you to distinguish implementation from outcome, earn relevance from the perspective of the people involved, make the purpose credible through your decisions and judge progress through changed behaviour. Technology creates potential; leadership and adoption determine whether that potential becomes value. The technology may be essential, but it still isn’t the transformation.