I have been trying to put clearer language around something that has increasingly defined how I work as a designer. What I think of as meta level design.
At the meta level, you are not primarily designing screens, flows, components, or even individual user journeys.
You are designing the abstraction layers that make many screens, flows, and journeys possible in the first place. You are designing the organising logic that determines how design decisions scale. You are designing the system of systems that other designers are operating inside of, often without realising it.
A distinction I find helpful is this:
Object level design is about designing things.
System level design is about designing how things relate.
Meta level design is about designing the rules by which systems are formed, extended, and reasoned about.
Why Most Design Work Never Reaches This Layer
Most design work never reaches this level, and that is not a criticism. In many roles, there is no need or incentive to operate here.
Work is usually scoped to a single product area. Success is measured by local outcomes like shipping a feature or improving a flow. Dependencies outside the immediate surface are treated as someone else’s problem. Design systems are treated as libraries of parts rather than theories of operation.
Even horizontal design work often stays shallow. Shared components. Shared patterns. Shared principles.
What is missing is depth across time, scale, and dependency.
Meta level design only becomes necessary when systems start breaking under their own complexity. When local optimisation creates global incoherence. When new capabilities cannot emerge without changing the underlying logic of the system.
The Shift That Happens at Principal Level
This is where the shift happens at principal level and beyond.
Senior designers tend to solve problems inside systems. Principal designers start reshaping the systems that define which problems exist in the first place.
The questions change.
Not “how should this work?” But “what needs to be true for many things to work, now and in the future?”
You start noticing hidden assumptions embedded in the design system. Conceptual gaps that keep reappearing across teams. Things designers repeatedly reinvent because the system does not name them. Missing abstractions that, if introduced, would collapse a lot of complexity.
Thinking Through Systems, Not Just Across Them
Another important aspect of meta level design is depth. It is not just thinking across systems, but thinking through them.
Every system sits inside other systems. Every abstraction has downstream consequences. Every simplification creates constraints somewhere else.
High level experience frameworks may sit above IA, navigation, components, and AI behaviour, but they also depend on role models, task models, permissioning, data maturity, and organisational incentives. Without understanding those dependencies, abstractions stay theoretical.
This is where a lot of vision work falls apart. It imagines an end state without plotting what has to be true for it to exist.
Creating New Axes, Not Just Connecting Dots
A distinction I come back to often is this. Many designers are very good at connecting existing dots. Meta level designers create new axes altogether.
They introduce new ways to reason about intent. New structures for guidance. New evaluative lenses for quality. That is invention, not synthesis.
The same applies to things like taxonomies, ontologies, operating models, canonical vocabularies, evaluative rubrics, and maturity models. These can feel like non design work until you realise how much design work they quietly control.
Gap Detection as a Design Skill
Underlying all of this is what I think is the real superpower at this level: Gap detection.
Seeing where language breaks down. Where systems contradict each other. Where teams talk past one another using different mental models. Where local work keeps failing for the same structural reasons.
Instead of patching over those gaps, you name them, model them, and create something new that resolves them at the root.
That skill is not common, and it is not taught. It comes from long exposure to complex systems, pattern recognition over years, a willingness to work on things that do not ship immediately, and comfort operating without clear precedent.
A Simple Way to Describe It
If I had to summarise it simply, it would be this. As designers become more senior, the work stops being about designing interfaces and starts being about designing the logic that governs interfaces.
At the principal level, you are no longer just solving problems. You are shaping the abstraction layers, systems, and vocabularies that determine which problems can be solved at all.
Meta level design is the practice of designing the systems that other designers design within. Once you see that, it is hard to unsee it.