The project was delivered on time. The budget was respected. The features are all there. And yet, six months after go-live, teams are barely using the new tool \u2014 or using it so poorly that the expected benefits remain out of reach.<\/p>\n\n\n\n
This scenario, far from being the exception, is one of the most common outcomes in digital transformation projects : 70% of those projects fail to meet their objectives<\/strong>, and the primary cause identified is not technical: it is human.<\/p>\n\n\n\n Adoption is the weakest link. And it is almost always the last item to be budgeted \u2014 when it is budgeted at all.<\/p>\n\n\n\n IT projects are traditionally measured at delivery: were the features developed? Were deadlines met? Was the budget consumed? What happens after deployment \u2014 how users actually take ownership of the tool \u2014 is rarely included in project success metrics.<\/p>\n\n\n\n In the majority of projects, change management accounts for 3 to 5% of the total budget<\/strong>, whereas best practice recommends investing 15 to 20%<\/strong>. The result: a few hours of training on go-live day, a PDF user guide, and teams left to fend for themselves with a tool they did not choose.<\/p>\n\n\n\n Changing working habits is one of the most complex challenges in management. Even when faced with an objectively better tool, employees tend to revert to previous practices if the change is not accompanied, explained and recognised.<\/p>\n\n\n\n How can you tell whether your IT project is heading for an adoption problem? Here are the most common signals:<\/p>\n\n\n\n Adoption starts long before deployment. Integrating representatives of future users into the project design \u2014 through workshops, user testing, validation committees \u2014 builds a sense of ownership and reduces resistance at go-live.<\/p>\n\n\n\n In each department, identify employees who are enthusiastic and confident with technology to become internal champions. These “change champions” play a key role in spreading good practices and providing day-to-day support to their colleagues.<\/p>\n\n\n\n Forget generic classroom training. The most effective training sessions draw on the real use cases of each team, in their own business context. A field technician has very different needs from a financial controller \u2014 their training should reflect that.<\/p>\n\n\n\n Measuring adoption goes beyond login rates. Relevant indicators include: the usage rate of key features, support ticket volumes, internal Net Promoter Score, and changes in targeted business behaviours.<\/p>\n\n\n\n Adoption is not a one-off event: it is a continuous process. Plan follow-up checkpoints at 1 month, 3 months and 6 months after go-live, adjust the support programme based on field feedback, and maintain regular communication around the benefits observed.<\/p>\n\n\n\n At L\u00f9kla, change management is not an option: it is a pillar of every project we support. Our Change & Adopt<\/a><\/strong> offering covers the entire adoption cycle, from digital maturity assessment through to post-deployment follow-up, including training, ambassador network facilitation and impact measurement.<\/p>\n\n\n\n Because a well-adopted tool is worth infinitely more than a well-delivered one.<\/p>\n\n\n\n The success of an IT project is not measured on go-live day, but by the value it creates six months, one year, two years later. That value does not happen automatically: it must be managed, supported and nurtured. Adoption is not an additional cost \u2014 it is what makes your investment worthwhile.<\/p>\n\n\n\n Looking to structure your adoption approach?<\/strong> Contact our L\u00f9kla experts<\/a> for a personalised assessment.<\/em><\/p>\n<\/div>\n\n\nWhy adoption is systematically underestimated<\/h2>\n\n\n\n
A culture of deliverables, not usage<\/h3>\n\n\n\n
A change management budget that is often token<\/h3>\n\n\n\n
Resistance to change is underestimated<\/h3>\n\n\n\n
Warning Signs of a Failed Adoption<\/h2>\n\n\n\n
\n
The levers of successful adoption<\/h2>\n\n\n\n
1. Involve users from the scoping phase<\/h3>\n\n\n\n
2. Appoint digital ambassadors<\/h3>\n\n\n\n
3. Train contextually<\/h3>\n\n\n\n
4. Track adoption with dedicated KPIs<\/h3>\n\n\n\n
5. Sustain the support over time<\/h3>\n\n\n\n
L\u00f9kla’s Change & Adopt Offering<\/h2>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Contact our team<\/h2>\n\n\n\n