Imaginez une maison construite au fil du temps par des équipes différentes, sans architecte pour vérifier l’ensemble. Chaque pièce fonctionne mais les interrupteurs changent de place selon les étages, s’y orienter devient difficile et les portes ne s’ouvrent pas toutes dans le même sens. La maison est habitable mais plus on y ajoute de pièces, plus harmoniser l’ensemble devient coûteux et compliqué. Pour ceux qui y vivent, ces frictions font partie du quotidien, pour quelqu’un qui y entrerait pour la première fois, ce serait désorientant et décourageant.
Digital devices can sometimes look like this house. Adding a tool, creating a new page, upgrading a site without reviewing the existing one: this is the daily routine for many organisations. For the sake of speed, to meet deadlines or because of the massive adoption of AI, they move forward without checking that each addition fits in well with the rest. Pépinia has given this phenomenon a name: coherence debt. This article explains what it is, how it arises and how to assess it.
Qu’est-ce que la dette de cohérence numérique ?
Coherence debt refers to the gradual accumulation of discrepancies within a digital device.. It affects the structure of the pathways, the language used, the behaviour of the interfaces and the way in which the business teams develop the system. It arises when decisions are taken quickly, without an overall vision, creating friction with what already exists.
A new section that uses a different vocabulary. A tool that behaves differently to others. A process that contradicts existing practices. Each deviation seems minor at the time it occurs. Put together, they make the system is increasingly difficult to understand and change.
Inspirée de technical debt - commonly used in IT - consistency debt also has a direct cost. The more it accumulates, the more difficult and costly it is to upgrade the system. An overhaul becomes a work in progress, a simple change has cascading effects and teams spend more time maintaining than improving.
Technical debt refers to the future costs associated with development choices that prioritised speed over code quality. It accumulates and the later it is dealt with, the more expensive it is to correct. Consistency debt follows the same mechanism, but its scope extends beyond the code. It results from decisions taken to go faster, simplify delivery or reduce an immediate cost, without measuring their impact on the overall understanding of the system. Both forms of debt have one thing in common: the more they accumulate, the more they cost to correct.
The debt of coherence does not only arise over time. It can appear from the very first decisions A poorly chosen tool, a poorly structured path from the outset. The age of the system is not the only factor. The initial choices are just as important.
Why organisations accumulate consistency debt
Most digital devices are not built all at once. They grow by successive additions: a new tool, a new section, an additional channel. Each addition follows its own logic, without any review of what already exists. The result seems to work, but the user feels the variations at each stage of their journey.
Changes in teams or service providers also amplify the phenomenon. When design decisions are not documented, new teams reinterpret previous choices in their own way. Variants appear without anyone having decided on them.
Without a common framework, each department goes its own way. Marketing, IT, communications, business: everyone has their own habits and their own tools. No one has an overview. It's the user who experiences it each time they move from one section to another.
It is the accumulation of these discrepancies that poses the problem. The system becomes more difficult for the user to understand. Each correction becomes more expensive than the last.
Why coherent debt always ends up being expensive
The more the consistency debt accumulates, the longer and more expensive it is to correct.
The impact of a consistency debt on the user experience is direct and visible :
- Navigation headings that change from section to section.
- Buttons that behave differently from one page to the next.
- A level of language that varies for no apparent reason.
- And so on.
Users have to make an extra effort to understand: their confidence decreases and abandonment increases.
Strategic impact is harder to measure but just as real. An inconsistent system blurs the messages sent to users. It undermines the clarity of the organisation. It also forces costly choices: creating gateways between tools that were not chosen together, managing systems that do not communicate. These costs could have been avoided.
The impact on teams is also often underestimated. Working on an incoherent system means spending time managing exceptions, dealing with repeated arbitrations and finding temporary solutions. This time is not spent moving the system forward: it's spent keeping it afloat.
The most common diagnostic errors
It is common to attribute the problems of a digital device to isolated causes: an insufficient conversion rate, poorly written content, a technical problem. These partial diagnoses lead to one-off corrections that have no effect unless the root cause is identified. Treating a symptom without identifying the source does not reduce the debt - it may even mask it.
A site can be visually coherent and structurally incoherent at the same time. Dealing with appearance without dealing with architecture does not solve the underlying problem. Nor is it linked to a lack of resources: the best-equipped organisations can accumulate a significant coherence debt, precisely because they have the resources to multiply initiatives without coordinating them. Coherence is a question of governance and method before it is a question of budget..
Let's take the example of an international organisation with several subsidiaries. Each entity has its own teams, its own tools and its own digital practices. There's no shortage of resources, but in the absence of a common framework, each subsidiary builds its system according to its own logic and its own systems. The result: user experiences that break down into multiple languages, non-interoperable tools and coordination costs that soar as soon as a project involves several entities.
Autre exemple : une collectivité territoriale qui lance une refonte de site, un portail citoyen et une application mobile en parallèle – sans cadre commun et avec des équipes qui n’échangent pas ou peu entre elles – produit de la dette de cohérence même avec un budget conséquent.
How do you know if an organisation is accumulating coherence debt?
Évaluer la dette de cohérence ne peut pas se faire en regardant le dispositif numérique section par section. Il faut une grille d’analyse qui couvre l’ensemble, pour faire apparaître les écarts entre ce que le dispositif est censé produire et ce qu’il génère réellement. Pour amorcer un diagnostic, cinq points permettent d’évaluer rapidement la situation.
- Structural coherence - Do the pathways follow a stable and predictable logic from one end of the system to the other?
- Semantic consistency - Are the same terms used everywhere: in the interface, content and communications?
- Behavioural consistency - Do similar components behave in the same way, whatever their location in the device?
- Editorial consistency - Does the content produced by different teams fit into a common framework, regardless of when it was produced?
- Consistent governance - Is there a shared body or framework for arbitrating alignment issues between departments?
These five questions do not constitute a coherent debt audit. They make it possible to identify quickly where tensions are greatest and to decide where to concentrate efforts as a priority.
Dans la plupart des organisations, la dette de cohérence est déjà présente. Une page qui contredit une autre, un formulaire qui renvoie vers un service qui n’existe plus ou un parcours en ligne qui se termine finalement par un appel téléphonique.
These situations are not isolated anomalies. They are the result of an accumulation of decisions taken separately, often to move faster, respond to a constraint or launch a new service without questioning the existing system.
Over time, these gaps add up. The system becomes harder for users to understand, more complex for teams to develop and more costly for the organisation to maintain.
Acknowledging the existence of a consistency debt is the first step. Reducing it then involves gradually realigning what has diverged: the pathways, content, tools and decisions that structure the digital experience.
This work is not just a question of design or technique. It is above all a question of method, governance and overall vision.