You Launched It. So Why Aren’t They Using It?

You’ve spent months preparing for the launch of a new technology. The business case was approved, the system was selected and configured, and employees received the necessary training and communication. Everything went according to plan, and you were confident that the investment would deliver the expected results.

Initially, there were encouraging signs. Some employees logged in, explored the platform and started using it, and you believed that others would soon follow. But a few months later, usage had started to decline. The same five people seemed to account for almost all the activity, while many of the employees you expected to come on board had never logged in at all. Despite a successful implementation, the technology wasn’t being adopted in the way you’d anticipated. So what had gone wrong?

I’ve spent much of my career trying to understand why this happens. Back in 2015, I was leading Learning for the Financial Services division of a large retailer. We had a constant demand for new joiner training, and I became convinced that digital learning could help us deliver training in a more sustainable and scalable way. As I researched what it would take to make online learning successful, I came across a statistic suggesting that only around 10% of people adopted these types of systems. Whether that number was accurate or not, it raised a question that has stayed with me ever since: if organisations were investing so much time, money and effort into technology, why were so few people actually using it?

A few years later, I founded a digital learning consultancy and spent almost a decade helping organisations take their training online. Across different industries, technologies and employee groups, I encountered the same challenge repeatedly. Organisations could successfully implement technology without achieving the sustained adoption needed to realise its value. That experience fundamentally changed how I think about technology implementation.

Why technology adoption is harder than we think

I believe three assumptions frequently undermine our efforts to achieve sustained technology adoption.

1. We assume that if something is beneficial, people will use it.

We tend to approach technology adoption as a rational decision. If a new system makes someone’s work faster, easier or more efficient, surely they’ll choose to use it. But knowing something is beneficial doesn’t automatically translate into behaviour change. Consider exercise. Most of us understand its benefits, yet that knowledge alone doesn’t guarantee that we’ll exercise consistently.

The same is true in the workplace. Employees may recognise that a new technology offers advantages while continuing to rely on familiar tools and processes. Established habits are powerful, and changing them requires more than presenting a compelling reason to do something differently. We need to recognise that the decision to adopt a new technology isn’t always driven by a rational assessment of its benefits.

2. We assume that proving the value will convince people.

When communicating the benefits isn’t enough, organisations often try to demonstrate the value more convincingly. We conduct time studies, calculate efficiencies and produce evidence showing that the new technology is objectively better. Imagine replacing a manual process involving spreadsheets and emails with a system designed to make the work faster and easier. The analysis demonstrates measurable time savings, yet employees continue using their spreadsheets.

The problem isn’t necessarily that the technology lacks value. It’s that objective value and perceived value aren’t always the same thing. A process might be faster according to the data, but if it feels more complicated or unfamiliar to the employee, they may not experience it as an improvement. We can demonstrate the value of a technology, but we can’t assume that employees will perceive that value in the same way. Until they experience the benefits for themselves, the evidence may do little to change their behaviour.

3. We assume the working environment will support the change.

Perhaps the most significant oversight is assuming that once a new technology is launched, the organisation will naturally adapt around it. Consider a dashboard that gives leaders real-time access to information. The organisation invests in the technology, trains employees and encourages its use. Yet leaders continue asking their teams to prepare spreadsheets. Similarly, a new system might be introduced to streamline a process while the old reports, templates and approval processes remain in place.

Employees quickly recognise these contradictions. Although the organisation is communicating one expectation, its everyday practices are reinforcing another. People pay attention to what leaders ask for, what gets measured and what gets rewarded. When those signals contradict the intended change, established behaviours are likely to persist. People don’t simply follow what gets communicated. They follow what gets reinforced.

These three assumptions point to a common problem: organisations often focus on introducing technology without giving equal attention to the conditions required for people to adopt it.

Four conditions for sustained technology adoption

Across the technology implementations I’ve worked on, I’ve found that sustained adoption depends on creating four conditions. People need to understand the value of the technology, know where it fits into their work, experience its benefits and operate in an environment that reinforces continued use. I use four questions to guide this thinking.

1. Why would I use it? — Value

Most organisations communicate the benefits of new technology. The challenge is that we often describe those benefits from the organisation’s perspective rather than the employee’s. We talk about improving efficiency, increasing productivity and streamlining processes. These may be compelling business outcomes, but they don’t necessarily explain why an individual employee should change how they work. Employees are asking a more personal question: What does this mean for me?

Instead of communicating that a system will improve efficiency, explain how it could save someone 15 minutes each time they complete a particular task. Instead of saying it will streamline a process, explain that they will no longer need to enter the same information in three different places. The difference is specificity and relevance. When people understand how technology will improve their own experience of work, they have a more meaningful reason to consider changing their behaviour.

2. Where does it fit? — Application

This is the condition I believe organisations most frequently overlook. Technology training typically focuses on functionality. We teach employees how to navigate systems, find information and complete tasks. But knowing how to use a feature isn’t the same as knowing when to use it. Technology is built around features, while people work in processes. If we want employees to adopt technology, we need to help them understand how it fits into their existing responsibilities and routines.

Consider the implementation of a performance management system. We might train managers to create goals, capture performance notes and complete reviews, but unless we connect those features to their actual responsibilities, managers are left to work out how the system fits into their existing routines. Should they use it when preparing for a one-on-one, setting goals with an employee, reviewing progress or preparing for a performance conversation? Which existing activities should the system replace, and how should their way of working change?

These questions matter because employees don’t automatically translate system functionality into new work practices. Effective adoption requires us to connect technology to the processes, decisions and activities that make up someone’s working day. Otherwise, we risk creating employees who are competent users of a system but rarely find a reason to use it.

3. Have I experienced the benefit? — Experience

There’s an important difference between understanding the promised benefits of a technology and experiencing those benefits personally. Communication can establish expectations, and demonstrations can show what’s possible, but neither guarantees that employees will believe the technology is genuinely better than their existing way of working. That belief develops through experience. When someone completes a task more easily, saves time or solves a problem faster, the value becomes tangible.

This means our approach to learning and change should extend beyond explaining benefits and teaching functionality. We need to create opportunities for people to experience the benefits through meaningful work. Rather than simply demonstrating how a system operates, help employees use it to complete an actual task or solve a problem they encounter regularly. The objective is to create moments when employees recognise for themselves that the new way of working offers an advantage. Communication creates expectation. Experience creates belief.

4. What will make this stick? — Habit

Initial adoption is one challenge; sustaining it is another. Organisations sometimes turn to incentives, competitions and leaderboards to encourage technology usage. These activities may increase engagement temporarily, but they don’t necessarily establish lasting habits. Sustained adoption requires an environment that consistently reinforces the desired behaviour. In my experience, three elements are particularly important.

Leadership plays a critical role in reinforcing new behaviours. Leaders need to demonstrate the behaviours they expect from others. If they’ve introduced a new reporting dashboard, they should use it to access information rather than continuing to request spreadsheets from their teams. Their actions signal whether the new technology is genuinely part of how the organisation expects people to work.

The working environment must also support the change. Organisational processes, measures and routines need to reinforce the new way of working. If old templates, reports and approval processes remain in place, employees may have little reason to abandon them. The systems and processes surrounding the technology need to evolve alongside it.

The technology itself needs to be accessible, intuitive and genuinely useful. Even strong leadership and effective change management cannot compensate indefinitely for technology that makes people’s work unnecessarily difficult. When these three elements reinforce one another, the technology gradually becomes embedded in everyday work. Employees no longer think of it as a new system they’re expected to use; it simply becomes how work gets done.

It’s time to rethink what successful implementation means

For L&D and HR professionals, achieving sustained technology adoption requires us to think differently about our role in implementation. Delivering training, communicating benefits and supporting a successful launch are important contributions, but they are not the outcomes we’re ultimately trying to achieve. Our responsibility extends to helping the organisation realise the value of its investment by ensuring that technology becomes embedded in how people work.

The four questions I’ve outlined provide a practical way to approach this challenge. We need to ensure that employees understand why they should use the technology, know where it fits into their work, have opportunities to experience its benefits and operate in an environment that reinforces continued use. These conditions are relevant whether we’re implementing a learning platform, a performance management system, an HR solution or new AI technology.

I also believe we need to reconsider how we measure implementation success. Launching on schedule, delivering training and achieving initial login targets may tell us whether we’ve implemented the technology effectively, but they tell us very little about whether we’ve achieved meaningful adoption. To understand whether our investment is delivering value, we need to look beyond initial activity and examine whether the technology is changing how work gets done.

Next time you introduce a new piece of technology, my challenge to you is this: instead of asking whether the implementation was successful, check whether people are working differently six months later. That will tell you if you’ve been successful or not.

About the author

I’m Sheree Comninellis. I work in corporate Learning & Development, with a focus on building enterprise capability. I write and speak about learning, leadership and change.

Have a perspective to share or want to continue the conversation? Connect with me on LinkedIn or get in touch through my website.