Digital transformation: why some organisations digitise without transforming

In many organisations, digital projects are multiplying. New tools, collaborative platforms, dashboards, and applications are appearing at a rapid pace. However, this momentum does not always lead to improved processes, simplified workflows, or more effective decisions.

This paradox is common: an organisation can invest heavily in digital technology while still facing the same operational difficulties. Projects progress, but the frustrations persist. So, how can we ensure that a genuine digital transformation is being undertaken, rather than a mere «accumulation» of digital projects?

What is digital transformation?

Before evaluating digital transformation, one must first understand what the term actually covers. Digital transformation refers to the fundamental overhaul of an organisation's processes, decision-making methods, and user experiences through digital technologies.

Digital transformation involves a change in operational logic An organisation transforms when digital technology alters how it creates value, not when it digitises existing processes. It's common for any initiative incorporating a digital dimension to be labelled a «transformation». Implementing an intranet, a CRM, or a mobile app is often qualified as digital transformation. However, these projects can coexist without challenging the silos, duplication, or inconsistencies that degrade user experiences. The organisation is then digitalising but not transforming.

Pourquoi certaines transformations numériques échouent-elles ?

Digital transformations rarely fail due to a lack of resources or technology. They fail more often because digital is approached as an IT project rather than a driver of organisational transformation. Tools evolve, projects multiply, but ways of working remain unchanged.

Some practices recur regularly in organisations where transformation struggles to produce results:

• Believing that a technological project can solve everything. Implementing an ERP, CRM, or a new platform does not in itself transform an organisation. These tools can improve what already exists, but they only produce value if they are accompanied by an evolution of processes, governance, and practices. Otherwise, they merely digitise existing dysfunctions.
• The IT department/digital directorate is still perceived as a support function/a fully-fledged department. In many organisations, information systems are involved once decisions have been made. Their role then is to implement business demands rather than contribute to strategic arbitration. This approach limits digital to an execution function, when it should be participating in the thinking about journeys, processes, and operating models.
• Do not re-evaluate its business model. A true digital transformation normally leads to questioning how the organisation creates value, delivers its services, interacts with its customers or users, and makes its decisions. When digital is only used to replicate the existing in a dematerialised form, the transformation remains superficial. The tools evolve, but the organisation continues to operate according to the same logic.

How to recognise a digital transformation that isn't working?

Several signs within an organisation can diagnose confusion between digital transformation and the accumulation of digital projects.

• The lack of a shared vision between departments (lack of a Product Manager or dedicated leadership). Each department launches digital initiatives, but no one can explain how these projects link together or what overall effect they are producing. The organisation is undertaking multiple projects without any coherence being verified.
• The recurrence of similar projects failing. For example, we relaunch a collaborative portal because the previous one didn’t work. We change CRM because adoption remains low. We redesign a website without understanding why the previous one didn’t meet needs. This repetition shows an inability to draw structural lessons: the organisation reacts without reviewing past experiences.
• The gap between rhetoric and reality. The presentations display ambitions for transformation, but employees continue to use Excel files, emails, and manual processes to bypass official systems. This gap reveals that digital initiatives are not meeting real needs: they are imposed rather than integrated.
• The absence of difficult decisions. An organisation that is truly transforming must arbitrate, prioritise and give up. It must agree to shut down systems, simplify processes and question habits. If every project is validated, if no initiative is stopped, if no tool is decommissioned, then the organisation accumulates without transforming.

How to assess the maturity of a digital transformation?

Four observable dimensions can reveal the quality of a digital strategy and allow judgment of the slider level between «simple disruption» and transformation.

• Clarity of vision. Ask three managers at different levels what the organisation's digital strategy is. If the answers are very different, if they are vague or if they simply list projects, then the vision is not shared. An organisation that is transforming itself knows how to explain simply what it is trying to change and why digital technology is a lever for achieving this.
• The coherence of initiatives. List the five main digital projects currently underway. Identify their objectives, their managers and their target users. If these projects are not coordinated, if they create redundancies or if they involve the same teams without coordination, then the organisation is acting without orchestration. Transformation requires an overall approach in which each initiative reinforces the others.
• The ability to arbitrate. Identify the projects stopped or refused over the last twelve months. If this number is zero or very low, if all the proposed projects are validated, then the organisation is accumulating without prioritising. Transforming implies giving up, concentrating efforts on what really counts, accepting not to do everything at once.
• User impact. Directly question end-users, whether they are customers, employees, or partners. Has their experience genuinely been simplified? Have deadlines decreased? Have pain points been reduced? If the answers remain negative despite digital investments, then the projects are not transforming the experience. They are adding tools without solving problems.