Every organisation that embarks on a digital transformation has, at one time or another, formulated the same ambition: streamlined interfaces, fluid paths, tools that users understand without training. The gap between this intention and the result delivered is one of the most constant challenges of digital projects, not because of a lack of will, but because the organisational conditions to achieve it are rarely in place from the outset.
Managing a digital project means dealing with complexity from the outset: multiple stakeholders, heterogeneous systems, diverse uses. So why is it so difficult to keep digital projects simple and, above all, how do you go about it?
Why complexity sets in and why it's difficult to see from the inside
In a digital project, the accumulation of functionalities, layers of information and levels of validation is usually the result of locally justified decisions. Each addition satisfies a stakeholder, This is precisely what makes complexity difficult to perceive from the inside. This is precisely what makes complexity difficult to perceive from the inside: it arises through the aggregation of coherent choices, without any of them being clearly wrong in isolation.
This mechanism is amplified when the project involves several teams with distinct logics, such as the marketing department, IT department, business teams and communications. They each contribute to the perimeter from their own perspective but in the absence of shared prioritisation criteria and a stabilised overall vision, contributions add up without being arbitrated.
This coordination complexity is sometimes compounded by another, more structural one: the digital project reveals strategic choices that the organisation had not yet had to make.
An organisation whose business model is based on sales via physical distributors will be faced with a question that digital technology will make inescapable: how do you develop an e-commerce channel without undermining a distribution network that has been built up over time? In this case, the complexity of the digital journey is not a design problem: it reflects an unresolved strategic decision. The digital project is the indicator, not the cause.
This phenomenon affects organisations of all sizes and levels of maturity. It is not a sign of poor governance, but rather of governance that has not yet integrated digital technology as an integral part of the company's strategy and treats it in its own right.
Digital technology makes disorganisation less visible than a physical environment
There is a perception gap A significant difference between malfunctions in a digital device and those that occur in a physical environment.
In a point of sale, workshop or logistics area, inconsistencies are immediately noticeable: an incorrectly referenced product, contradictory labels, an empty shelf. These signals trigger a rapid reaction, precisely because they are visible.
In a digital ecosystem, the same kinds of tensions (redundant data, obsolete processes, interfaces that are gradually moving away from actual use) remain silent for longer. The immateriality of digital technology naturally delays the moment when an organisation perceives the need to act.
Digital technology amplifies what the organisation allows it to do, for better or for worse. The immateriality of data and digital tools offers a false sense of freedom and ease: it masks mistakes, allows individual tinkering and, above all, makes it possible to work together. delays awareness of malfunctions that have nothing to do with digital technology.
How to structure simplicity in a digital project: three organisational levers
Simplicity is sometimes perceived as a constraint: fewer functions, fewer pages, fewer cases covered. This reading underestimates what simplification can achieve: more robust systems that are more widely adopted and easier to develop. On the other hand, it presupposes the development of three specific organisational capabilities for an organisation, which are not related to graphic design but to method, governance and the culture of arbitration.
Formulate a clear intention This tool exists to enable the user to carry out this specific task. This apparently simple formulation is structuring. Its construction upstream of the project conditions the coherence of all the decisions that follow, and in itself constitutes a high added-value framing task.
The ability to prioritise Accepting that not everything will be covered in the same cycle, that consistency is more important than exhaustiveness, and having shared criteria for arbitrating between the contributions of different teams.
Test and adjust testing: subjecting the interface to real users and integrating the feedback as steering data. These UX practices are well known and would benefit from being integrated as essential stages of a project rather than optional extras.
This structure can be put in place gradually, regardless of the organisation's initial maturity.
Digital simplicity is an attainable goal. It presupposes precise organisational conditions - a stated intention, governance of trade-offs, the practice of testing - which can be built up gradually and methodically. The organisations that achieve this are not necessarily those with the greatest resources, but those that have structured their ability to decide and prioritise.
As digital technology plays an increasingly important role in the relationship with users, employees and partners, the ability to produce simple, coherent experiences is becoming a sustainable differentiating advantage. Not because it is rare, but because it is based on trade-offs that few organisations have yet formalised.
Keeping digital simple is demanding. It is also, for this reason, one of the most structuring projects an organisation can undertake - and one where a clear method makes the biggest difference.