Digital transformation, AI, and process redesign are often treated as engineering projects, but in reality, they are design trajectories. Their success depends less on technical perfection than on people embracing them. Adoption is emotional before it is rational. People therefore need to trust a solution before they start using it, and they need to love working with it before it becomes part of their daily operations.
In that sense, designing a digital solution resembles designing a comfortable chair or a well-tailored dress. The product must function, certainly, but functionality alone is never enough. Comfort, elegance, familiarity, and emotional resonance determine whether people truly adopt it.
Every serious design trajectory therefore starts with three essential principles.
1 Separate problem space from solution space
Too many digital projects jump immediately toward technology choices, dashboards, or AI tools before understanding the underlying tensions, frustrations, and ambitions of their company. The discipline of the double diamond therefore remains essential: first diverge to understand the real problem, and only later converge toward solutions.
2 Determine clear design objectives for your ambitions
Ask yourself: “What exactly are we trying to maximize?”, as efficiency alone is rarely sufficient. In our approach, three dimensions matter simultaneously: business impact, love, and trust. Business impact ensures that the solution creates measurable value. Love determines whether people willingly engage with it. Finally, trust determines whether your employees dare to depend on it. Make all three of them explicit targets for the team.
3 Determine explicit design constraints
This third principle is often forgotten, design constraints are the hidden conditions that determine whether a design can survive inside an organization. In many transformation projects, these constraints remain implicit until late in the trajectory, where they suddenly appear as resistance, delays, or rejection. Making them explicit early is therefore one of the most important responsibilities in digital transformation.
Many of these constraints are deeply human. Teams operate according to unwritten rules, informal power structures, and social habits. A solution that violates these invisible norms may be technically excellent, and yet still fail completely. If a system threatens the identity of a team, bypasses established rituals, or removes autonomy without sensitivity, the emotional contract breaks. Trust may erode, and adoption can stall.
Other constraints tend to be organizational and technological by nature
They relate to cybersecurity rules, integration standards, governance processes, procurement practices, or simply “the way we do projects here.” These may appear bureaucratic, but they are often the accumulated memory of previous failures and risks. Ignoring them could create friction that eventually undermines the initiative.
Important design constraints often concern the architectural and IT choices an organization is willing or unwilling to make. These choices shape not only the technical landscape, but also the speed of transformation, the room for innovation, and the level of organizational trust. Typical questions include:
- Do we build everything ourselves, buy configurable SaaS solutions off the shelf, or choose something in between? This is not merely a technical decision. It reflects the balance between uniqueness and standardization; between flexibility and maintainability; between control and speed.
- Do we dare to renovate our single source of truth, or do we treat it as untouchable?
Many organizations depend on a fragile but critical core system. Sometimes innovation is allowed only around the edges, while the heart remains frozen. The question is therefore not only technical, but political and emotional: who dares to modify the system everyone depends on? - Do we
replace legacy systems or continue to coexist with them?
Legacy systems are rarely just old software. They contain years of embedded processes, exceptions, habits, and institutional memory. Replacing them means redesigning part of the organization itself.
These constraints strongly influence what kind of transformation is realistically possible. They define the boundaries within which designers, architects, and business teams can operate. Ignoring them leads to elegant concepts that never survive implementation. Respecting them, while still challenging them when necessary, is what makes a digital solution adoption ready.
The essential role of the IT manager
This is why the IT manager plays a critical role in transformation. Not merely as a technical authority, but as the guardian of IT-related design constraints. Their responsibility is threefold:
- make the architectural and IT design constraints explicit;
- communicate them clearly and early in the process to all stakeholders;
- and ensure they are respected throughout the project, either directly or through governance and project gates.
When constraints remain invisible, they become traps. When they are explicit, they become design material. Good designers do not complain about constraints; they use them to their advantage. Constraints create direction; they force clarity and transform abstract ambition into solutions that organizations can actually adopt. And in the end, adoption is the only metric that matters.
If you’re interested in diving deeper into the details, you can order the book on Bol.com (Dutch) or on Amazon (French).
If you would like a more personal and tailored guidance for your business, you can request a meeting with the authors through the following link: https://www.sustain.brussels/contactus
Previous Article: Love and Trust: The Way to your User’s Heart
Design Constraints