The real reason design gets brought in too late and why it’s not a design problem
Written by Luke James Taylor, Design Sprint X Co-Founder
Design thinking. Design sprints. Human-centred design.
Whatever language an organisation uses, the same pattern keeps showing up: by the time designers are in the room, the most important decisions have already been made.
This is not a new observation. It has been written about, presented on, and discussed for over a decade. And yet, despite all of that awareness, it continues to happen with remarkable consistency. Teams still build first and question later. Products still ship before they are properly understood. Retrospectives still include the same quiet admission: we should have involved design earlier.
The more interesting question, then, is not whether this happens. It’s why it keeps happening anyway.
The loop teams can’t seem to break
Most teams have lived through some version of the same cycle.
A product is defined, scoped, and built over months. It launches. It underperforms. Users don’t engage in the way anyone expected. At some point, the team realises that earlier input — from users, from research, from design — might have changed the outcome.
The insight lands. It feels obvious. Then the next project follows the same path.
When people say “design comes in too late”, they’re usually describing one of three realities:
design is treated as delivery, not thinking — brought in to execute, not shape direction
design is included in discovery, but only within a pre-defined solution
design is present in the process, but absent from real decision-making
Most organisations aren’t dealing with just one of these. They’re dealing with all of them at once.
We already know this so why hasn’t it changed?
Our 2026 State of Design Thinking survey (still open to new responses) reinforces how consistent this pattern is. Across industries, teams describe the same tension: design is expected to improve outcomes, but is rarely positioned early enough to influence the decisions that determine those outcomes.
The organisations seeing the most impact from design aren’t doing radically different work. They’re doing something simpler and harder.
They’re involving design at the moment where problems are still being defined.
This aligns with years of research. Organisations where design operates at a strategic level consistently outperform those where it’s treated as a production function.
So the issue isn’t awareness.
It’s that the system hasn’t adapted to what that awareness requires.
The system wasn’t built to include design
To understand why this keeps happening, you have to look at how decisions are made.
Product direction is typically owned by product managers, executives, or commercial leads. They define priorities, shape roadmaps, and decide where investment goes. These decisions happen in specific rooms, at specific moments.
Design is rarely in those rooms. This isn’t usually intentional. It’s historical.
Product management as a discipline was formalised long before UX or design thinking. The structures that exist today reflect those origins. Design was added later and placed downstream.
So even in organisations that value design, the default flow still looks like this:
Direction → then design
And once direction is set, design’s influence is naturally limited.
Changing that isn’t about better collaboration. It’s about changing who is involved, when decisions are made.
Design is still misunderstood at the top
There’s another layer to this.
At leadership level, design is still often seen as:
making things look better
improving usability
refining outputs
Not as:
shaping problems
testing assumptions
reducing risk before decisions are made
If design is seen as polish, late involvement makes sense.
If design is understood as a decision-making capability, late involvement becomes a liability.
Most organisations are still operating somewhere between those two views.
The value is real but it’s not being translated
There’s also a responsibility on the design side.
Design has historically been better at explaining ideas like empathy and user-centredness than it has been at linking its work to business outcomes. Those ideas matter, but they don’t always influence how organisations allocate time, budget, or attention.
What tends to land more clearly are outcomes like:
reduced rework
faster time to market
stronger decision-making confidence
These are often the direct result of involving design earlier. But they are rarely measured or articulated in a way that makes that connection obvious.
Without that translation, the case for early involvement remains compelling in theory, but weak in practice.
The real cost shows up in places you don’t measure
Late design involvement is often framed as a rework problem. That’s true — but it’s the most visible and least interesting cost.
The bigger costs are harder to see.
There is the cost of solving the wrong problem. If design had been involved earlier, the team might have reframed the challenge entirely. Instead, time and resources are invested in something that performs adequately, without ever revealing what a better version could have looked like.
There is the cultural cost. When designers are consistently positioned as executors, the role narrows. The most strategically minded people either leave or stop pushing. Over time, this reinforces the belief that design is a delivery function.
And there is the speed cost. When research happens after direction is set, it creates friction. If it challenges the plan, it’s disruptive. If it supports it, it adds little value. The same work done earlier improves decisions without slowing progress.
This isn’t a design fix, it’s a leadership shift
If this were a design problem, the solution would be straightforward. Better tools. Better training. Better workshops.
But the persistence of this issue suggests something else.
The real work sits at the organisational level.
It requires:
changing when design is included in decision-making
redefining design as a strategic capability, not a delivery function
making the impact of early design involvement visible in business terms
These are not small adjustments. They involve shifting habits, expectations, and in some cases, power.
Where change actually starts
For organisations that do want to evolve, the shift is not theoretical. It usually starts small.
One project where design is involved before direction is set.
One moment where assumptions are challenged early instead of defended later.
One sprint run at the right time, with the right people in the room.
From there, the value becomes visible. And once it’s visible, it becomes repeatable.
Until the system changes, nothing else will
Design is not being brought in too late because designers lack capability.
It is being brought in too late because the system was never designed to include them early enough.
Until that system changes, the pattern will continue.
At Design Sprint X, we’re building the clearest picture of how design thinking actually works in 2026.
If you’ve seen that firsthand, you’re part of this story. We’re running a short survey to understand:
where design thinking is working
where it’s breaking down
and how teams are actually making decisions today
It takes less than 10 minutes.