An IT department rolls out a new collaborative tool. The communication is polished, training is planned, the executive sponsor is clearly identified. Six months later, the tool is under-used, teams have returned to their old practices, and no one really understands why — since, on paper, everything had been done by the book.
This scenario repeats, with variations, in a majority of digital transformations. And it points to a recurring diagnostic error : treating a relational problem as if it were a tooling problem.
The tool is never the real subject
A collaborative tool changes nothing on its own. It makes visible — or impossible to ignore — the way a team already works together. If the existing culture rests on protected silos, on information hoarding as a mode of power, or on an old distrust between two departments, no tool dissolves these dynamics. It circumvents them, at best; it reproduces them, most often.
This is why transformation plans limited to training on features almost systematically fail to produce a lasting change in usage. Training addresses competence. It never addresses the relationship.
What roadmaps don’t see
A digital-transformation roadmap lists milestones, deliverables, adoption metrics. It makes — and can make — no room for what actually decides success or failure : the invisible relational loops that already structure the organization before the tool arrives.
These loops often look like this : a business team that has learned, through past experience, to distrust initiatives from IT. A department that has an interest, consciously or not, in remaining the mandatory gateway for a piece of information — because that’s what legitimizes its place in the organization. An executive who champions the project on the surface but who, in practice, keeps validating decisions through the old channels.
As long as these loops aren’t identified and worked on for themselves, the most powerful tool on the market will produce the same result : a façade of adoption, which collapses as soon as the sponsor’s pressure eases.
The real lever: make what blocks visible, before deploying
The systemic approach applied to a digital transformation doesn’t replace classic change management — it precedes it, and guides it. Before defining a communication plan or a training schedule, it asks a different question : what, in the organization’s current functioning, has good reasons to resist this precise change?
This question, asked with the right people and at the right level, surfaces resistances that no adoption survey reveals — because they’re not a matter of competence, but of loyalty, informal power, or trust.
What it changes concretely
A digital transformation that integrates this relational diagnosis upstream isn’t faster on paper. But it lasts — because the tool becomes part of a system that has been prepared to receive it, rather than a system that will silently keep doing as before.