Most design leaders are still doing the job they got promoted from.
The transition from senior designer to design leader is not a seniority upgrade. It is a role change. Most organisations never make that clear — and most design leaders never fully make the shift.
There is a particular kind of design leader that most large organisations are quietly frustrated by. They are technically excellent. They care deeply about the work. They have strong opinions about craft and defend them well. Their team respects them.
And they have almost no organisational influence.
The work they produce is good. The business outcomes it contributes to are largely invisible. Their relationships with product, engineering, and the leadership table are functional but not strategic. They are, operationally, a very experienced senior designer with a larger job title.
This is not a talent problem. It is a transition problem. And it is far more common than most organisations are willing to name.
The promotion that doesn't come with instructions
When a designer becomes a Lead Designer or Head of Design in a large organisation, the implicit assumption is that the skills that earned the promotion are the skills the new role requires. They are not.
Senior design roles reward craft mastery, creative judgment, and the ability to produce excellent work under pressure. Design leadership roles require something structurally different: the ability to build the conditions in which excellent work is possible at scale, sustained over time, inside a complex political environment.
Those are not extensions of the same skill set. They are different disciplines. And the gap between them is where most design leadership careers quietly stall.
The designers who make the transition successfully are not the ones who produce the best work. They are the ones who learn to stop producing and start enabling.
The four domains of design leadership
The Design Leadership Operating Model maps the role across four distinct domains. Most new design leaders operate in one of them.
Craft Governance covers design standards, review processes, system ownership, and quality thresholds. It is where most design leaders feel at home and spend a disproportionate amount of their time. It is important. It is not sufficient.
People Architecture covers team structure, capability mapping, hiring strategy, career frameworks, and the conditions that determine whether talented designers stay or leave. It is frequently neglected until there is a retention problem that has already become expensive.
Stakeholder Strategy covers influence mapping, political capital management, cross-functional relationships, and the ability to communicate design value in the language of business outcomes. It is rarely taught formally. It is frequently the thing that determines whether a design leader succeeds or is quietly moved on.
Evidence Infrastructure covers how the team demonstrates its value, what metrics it owns, how research and design evidence enters business decisions, and whether there is any systematic connection between design output and commercial outcome. This is the domain that separates high-maturity design functions from teams that are perpetually underfunded and overlooked.
A design leader operating only in Craft Governance — however excellently — is still doing a version of the job they got promoted from.
The influence gap
Most design leaders in large organisations will tell you, if asked honestly, that they do not have enough influence over the decisions that determine the conditions in which their team operates. Headcount, tooling, roadmap priority, research budget, access to senior stakeholders.
The standard diagnosis is that the organisation doesn't value design. Sometimes that is true. More often, the organisation doesn't have evidence that design delivers outcomes it cares about — and nobody has built the architecture to produce that evidence.
Design functions that are consistently well-funded and well-positioned inside large organisations share a common characteristic: they have made the value they deliver legible to the people who control resources. Not in design terms. In business terms. Delivery confidence, risk reduction, cycle time, commercial outcomes.
Being right about design is not a strategy. Building the conditions under which being right about design changes decisions — that is a strategy.
The seniority trap
There is a version of this problem that is specific to designers who are exceptionally good at their craft and know it.
The risk is not arrogance. It is relevance. When you have strong craft instincts and a track record of being right, the incentive is to stay close to the work — to remain the person whose creative judgment is the quality benchmark for the team. It feels like leadership because it is influential. But it is a form of influence that does not scale, does not build organisational capability, and does not accumulate the kind of institutional trust that determines long-term operational freedom.
The design leaders who build genuinely high-maturity functions are the ones who have learned to invest their credibility into the team rather than into their own judgment. Whose measure of success is not the quality of the work they personally shaped, but the quality of the work the team produces without them.
That is a different ambition. It requires a different daily practice. And for designers who built their careers on craft excellence, it is often the hardest transition to make.
What changes when the model shifts
Design leaders who operate across all four domains — not equally, but intentionally — tend to describe a specific shift in how their organisations relate to them.
They stop being the person who advocates for design and start being the person whose judgment about organisational investment is trusted. They are consulted earlier. Their team's work is better contextualised in business outcomes. Headcount decisions go in their favour more consistently. Research findings change things.
None of this happens because the organisation suddenly starts valuing design. It happens because the design leader has built the architecture that makes the value visible, credible, and defensible in terms the organisation already uses to make decisions.
That is not a soft skill. It is an operational discipline. And it is one that most design leaders in large organisations were never explicitly taught.
→ The Design Leadership Operating Model and a complete framework for leading design in enterprise environments.