Design is often confused with what you see: colours, typography, layout. That's not wrong — but it's incomplete. What you see is the result of a series of decisions that go far beyond the visual. Behind every coherent interface lies a structural logic: a system of rules, components, and dependencies that determines how the visual emerges and how it scales.
What design is supposed to achieve
Design communicates. It creates perception, directs attention, conveys tone and trust. A well-designed interface signals to the user within milliseconds what they're dealing with — and whether it's worth continuing.
This communicative function is not decorative. It is functional. Design that fails to communicate is not less design — it is bad design. The measure of good design is not aesthetic preference, but the quality of the perception it generates.
What systems are supposed to achieve
A system is the structure that enables and scales design. It defines how decisions are made — not once, but repeatedly and consistently. A design system contains typography rules, colour values, component libraries, interaction principles, spacing systems. It ensures that what applies to one page also applies to twenty — without every decision needing to be made anew.
Systems are the foundation on which design lives. Without a system, design remains fragile: dependent on the consistency of manual decisions, susceptible to drift, difficult to maintain, and expensive to scale.
The conflict between the two
In practice, a false opposition often arises: design should be free and expressive, systems should be structured and constraining. The consequence is that both suffer. Design without a systemic foundation loses consistency. Systems built without design intention lose expressiveness.
The error lies in the sequencing: either you design first and then try to derive a system from it — or you build a system first and then constrain design within it. Both paths create friction.
The right sequence
Design and system must be developed simultaneously — or more precisely: both emerge from the same foundational decisions. Establishing typography simultaneously establishes the type system. Developing a component language simultaneously develops the rules for its application.
This simultaneity is not an efficiency measure. It is a quality decision. Only when design and system emerge in dialogue does something result that fulfils both in their strongest form: perceptual quality and structural robustness.
Practical implications
Concretely, this means: design decisions are tested for their systemic transferability from the start. Is this rule generalisable? Does this decision work in twenty places or only one? Does this exception create systemic debt, or is it justified?
Conversely, every systemic decision is tested for its design effect. Does this spacing system produce the right visual hierarchy? Does this colour logic support the intended perception?
The result is not a compromise between design and system. It is both — in a form that endures.