Business leaders like to think that they have control over the structure and organization of their business, but in reality, most of them simply approve architectural diagrams, transformation plans, and operational models. They examine slides and roadmaps that give them a sense of control, but this is only an illusion: to be precise, what they are approving is not the design, but the configuration. They manage the structure without having formulated any intention, and this is how they have allowed the enterprise design to fade into the background behind its technical execution.
In short:
- Leaders often confuse configuration and design, validating structures without clear intent, which relegates enterprise design to the background.
- Enterprise design should precede architecture by expressing a vision, whereas architecture merely formalizes it, and this reversal weakens the meaning of transformations.
- Management focuses on structures and models, to the detriment of understanding the system and the collective purpose.
- Enterprise design is a management act that consists of formulating an intention and ensuring consistency between identity, experience, and operations, before any technical modeling.
- Restoring design to its rightful place makes it possible to recreate a common language between managers, business lines, and architects, and to align vision and systems in the service of a coherent project.
When form takes precedence over intention
Enterprise design precedes business architecture, or at least it should. The former expresses a vision of how the organization wants to function, learn, decide, and serve, while the latter translates that vision into structures, processes, and systems. One designs, the other formalizes. But over time, the order has been reversed and leaders, under pressure from increasingly complex systems, have ended up confusing modeling with designing, translating with inventing.
This is not without consequence; it has profoundly changed the nature of management.
When we think architecture before design, we get organizations that are flawless on paper but incapable of making sense of what they do. We draw the pipes before understanding the logic of the flow, we install frameworks, platforms, and organizational charts, and then we hope that they will eventually embody the vision and, worse still, sometimes create it. However, architecture cannot produce meaning: it only distributes it.
In many businesses, this disconnect has become the norm. We first model dependencies, roles, and the scope of responsibilities before even discussing the purpose. More time is spent designing workflows and coordination and control interfaces than clarifying intentions, and in the end, the structure ends up taking the place of the project, and more time is spent perfecting the diagrams than questioning what they represent.
Ultimately, we confuse a well-structured organization with a well-understood organization that is consistent with its purpose and DNA.
An illusion of control
Leaders reassure themselves with representations, models, and tables, and in doing so, they believe they are steering the transformation because they validate the map. But a map remains a representation: it shows how things fit together, not how they interact, and what they control are the connections, not the dynamics of the system.
Business architecture gives the impression of rational control because everything seems to be in its place, every dependency identified, every flow modeled. And yet, the more companies perfect their architectures, the less energy they devote to designing what they really want to do, why, and how. Management then becomes the manager of structures whose initial logic it no longer understands (How management let systems do the thinking for them).
Ultimately, the impression of control gradually replaces understanding of the system.
This confusion between design and architecture partly explains the exhaustion of major transformations. Organizations invest heavily in structuring programs without asking themselves whether these architectures still reflect a collective intention. We talk about agility, modernization, and platforms, but we no longer talk about work, decision-making, or how individuals contribute to the common project and the functioning of the business. The business becomes a well-wired system but without clear direction. The illusion of control is to believe that technical consistency can replace managerial consistency and that a business can be well-architected without being well-designed.
Design as an act of leadership
Enterprise design is not a discipline parallel to architecture: it is a prerequisite for it. Indeed, it does not describe the organization as it is, but conceives it as it should become. It formulates the intention before the construction, the promise before the blueprint. It is an act of leadership and in no way a form of documentation. The role of the leader in this context is not to check that the blocks are aligned, but to ensure that what is aligned makes sense.
Taking back control of design means regaining the power to say “this is how we want our business to work” before asking “how are we going to model it”. It means refusing to delegate responsibility for consistency to technology.
Design does not seek structural perfection, but consistency between identity, experience, and operations. Architecture serves this consistency but does not define it.
But in many organizations, the order has been reversed. Systems decide how we work, processes dictate how we cooperate, and tools end up governing behavior. Management has become an exercise in constant alignment, when it should be an exercise in design.
The problem is not with the tools, but with the fact that we have forgotten to design what they are used to hold together.
Restoring a common language
Taking control of design again does not mean erasing or denying architecture, but rather giving it a new direction.
The challenge is to enable managers, business lines, and architects to speak the same language: that of intention (EDGY: a common language to align identity, experience, and operations). As long as we continue to talk about structure without talking about design, we will continue to pile up solutions that solve nothing.
Enterprise design is not just another method, but a space for dialogue between what we want to do and what we are capable of doing, between vision and systems.
Bottom Line
A business is not the product of its architecture, but of its design. Architecture is the translation of this design, but it is by no means the decision-maker, or rather, it should not be.
When the two are confused, we lose our bearings and build businesses that function well but not necessarily efficiently or consistently with their promise and DNA and, above all, that no longer really know why they function that way.
Restoring corporate design to its rightful place means giving managers back responsibility for consistency and relearning how to design before configuring.
To answer your questions…
Leaders often validate models and diagrams without formulating a clear intention. They believe they are designing, but they are merely configuring. Architecture gives the illusion of control because everything seems to be in its place, when in fact it creates no meaning. Design, on the other hand, defines the vision and purpose. Without it, businesses become technically coherent but managerially empty.
Enterprise design expresses an intention: it imagines how the organization wants to function and learn. Architecture then translates this intention into structures and processes. When this order is reversed, businesses lose their compass: they model before understanding what they really want to do.
By prioritizing architecture over design, leaders end up with well-designed but meaningless organizations. Structures are perfected rather than questioned for their usefulness. Management then becomes an exercise in control rather than design, and major transformations run out of steam due to a lack of shared purpose.
A common language allows executives, business units, and architects to align around a shared goal. Without it, everyone talks about structure instead of purpose. This shared vocabulary connects identity, experience, and operations, ensuring that the architecture truly reflects the business’s vision.
In this series:
| 1 | To manage is to design |
| 2 | How management let systems do the thinking for them |
| 3 | Enterprise design before architecture: putting the company back the right way up |
| 4 | Taking back control of enterprise design: intention before tools |
| 5 | A poorly designed enterprise is illegible and incomprehensible to employees and customers (Coming soon) |
Related articles:
A poorly designed enterprise is illegible and incomprehensible to employees and customers
How management let systems do the thinking for them
EDGY: a common language to align identity, experience, and operations
Efficiency vs. uniqueness: the false dilemma of operations
The AI-first company: the origins of an ambiguous concept that grew too quickly
A business can be born “AI first”, but can it become one?
