Design failed designers before the org did.

Design education is excellent at teaching designers to design. The tools, the process, the craft, the research methods, the principles that separate good work from forgettable work. That foundation matters and I'm not arguing against it.

What it doesn't teach is what the job becomes when you get senior enough for it to matter.

Nobody tells you that the most important decisions about a product are made before anyone opens a design tool. Nobody teaches you to question the brief before you execute it. Nobody explains that your influence as a design leader will be determined less by the quality of your work and more by where you sit in the decision-making process and whether you had any say in how you got there.

Design has defined professional progression as moving from junior execution to senior execution. Better craft, bigger scope, more complex problems. The trajectory is clear and the destination looks like mastery.

What it doesn't look like is upstream.

The conditioning nobody names

This part doesn't feel like conditioning, it feels like doing your job well.

Early career, you get rewarded for delivery. You learn that the brief is the starting point, not a negotiation. You develop instincts around execution, around moving things forward, around being the person who figures out how to make it work. Those instincts serve you and they get you promoted.

By the time they start working against you, they're a decade deep.

I spent years becoming good at designing things. Nobody told me the more important skill was deciding whether the thing was worth designing. Not because they were hiding it. Because the discipline never defined it as part of the job. So I arrived at senior roles equipped for everything that happens after a direction is set and almost nothing for what happens before.

The tension nobody warns you about

There is a moment most design leaders hit, usually somewhere in the middle of a role they thought they were doing well, where something becomes clear.

The more senior you get, the more the job moves away from craft and into how decisions are actually made. Who sets priorities, who is in the room before the brief exists, what gets funded and what gets deprioritised and why. These things determine what design can and cannot do more than any design decision ever will.

But you are still judged on the craft.

So you become responsible for outcomes shaped upstream, measured on what happens downstream. And when you try to fix that, by pushing earlier into the process, by questioning the direction before it is locked, by getting into rooms you were not invited to, it can be read as difficult. As misaligned. As not understanding how the business works.

Sometimes it turns political. Not because the idea is wrong, but because design was not expected to show up at that level. And the designer was not trained to navigate what happens when it does.

The few who get upstream anyway

There are designers who figure this out. They show up earlier, they shape briefs instead of receiving them and they have influence that does not appear to come from their title.

It looks like talent. It usually isn't, it is clarity about what the job actually is.

They understand that design's leverage comes from how problems get defined, not just how they get solved. That the most valuable question is not how do we design this well but is this the right thing to design. That the brief is a starting point for a conversation, not an instruction.

That should be basic, it should always be taught. It isn't.

The two failures reinforce each other

Organisations put design downstream. That is a structural failure and it is real.

The discipline produced designers who arrived pre-shaped to accept being downstream. That is the other failure and we do not talk about it enough.

Both reinforce each other. The org does not invite design upstream because it has never seen design operate there. Design does not push upstream because it was never trained to expect to. The conditions stay broken because both sides are running on the same assumption.

The assumption is that design is an execution function.

Until the discipline challenges that assumption, in how it trains designers, in how it defines what progression means, in what it tells emerging leaders the job actually is, the org failure will keep looking like the whole story. It isn't.

What actually needs to change

Not a course, not a framework. Not another conference talk about influence.

The discipline needs to redefine what progression means. Not from craft to strategy, as if strategy is just craft at a higher altitude. From making things to understanding how things actually move. Who decides, how authority works, what it takes to become structurally indispensable rather than structurally exposed when the budget gets cut.

That produces a different kind of designer. One who arrives at a senior role already asking the right questions, not spending the first three years figuring out they have been asking the wrong ones.

I spent longer than I should have looking at org structures and blaming them for the conditions design kept inheriting. Those conditions are real, but the designer who already understands that their leverage comes from upstream is harder to put downstream.

That is not the org's job to fix, it's the discipline's.