The Design Process is Failing Designers

Why the frameworks we rely on no longer match how products are built.

Photo by picjumbo.com: https://www.pexels.com/photo/white-printer-paper-196645/

The design process was optimised for an era when building was expensive and change was costly.

When writing code took months, when shipping the wrong thing could sink a company, when experimentation was slow and unforgiving, it made sense to slow everything down. To define the problem carefully. To gate progress through workshops, artefacts, and alignment rituals. To treat design as a protective layer between the business and catastrophic and costly mistakes.

That world no longer exists.

In an AI-enabled environment where prototyping is cheap, iteration is instant, and learning happens in days rather than quarters, the very processes that once protected teams have become a constraint and cause friction.

---

The process was built for scarcity, this is a time of abundance.

The dominant design frameworks we still use (double diamond, design thinking, problem-first discovery etc…) were shaped by a single underlying assumption: building is expensive, so let’s make sure we’re right.

A PM with AI can go from idea to interactive prototype in an afternoon. An engineer with Cursor can ship multiple variants of a feature in the time it takes to schedule a design critique.

Meanwhile, designers are often still asked to:

• write problem statements

• facilitate workshops

• align stakeholders

• produce artefacts that justify why building should begin

The result is a widening mismatch between how fast teams can build and how slow design processes allow decisions to move.

---

Design is important but it’s increasingly bypassed.

This is the uncomfortable truth: design hasn’t become less valuable, but the process we use to deploy design skill increasingly looks disconnected from how modern teams actually want to work.

AI tools now allow teams to:

• build working MVPs in hours

• test dozens of hypotheses in parallel

• analyse thousands of user interactions in days

• generate multiple journey maps or framings instantly

In this context, spending weeks perfecting a single problem definition feels misaligned, and not because understanding users doesn’t matter, but because learning by building is now faster than learning by planning.

Design education taught us to “fall in love with the problem, not the solution.”
That advice made sense when testing solutions was slow and expensive.

Today, it often produces the opposite outcome: teams delay learning in order to preserve process purity. That’s not to say that solving the right problem doesn’t matter, but that we can parallelise a lot of these activities.

Maybe a reframe for the AI era is “Fall in love with learning, not being right.”

---

The most dangerous shift: teams working around design

A design director recently told me their PM shipped a new checkout flow before design finished discovery. Used Claude to prototype three variants, tested them, shipped the winner. Design found out when they saw it in production. The PM wasn't being malicious, they were doing the right thing.

In AI-forward organisations, a pattern is emerging.

1. PMs are prompting their way to “good enough” UX
   They’re not better designers but they’re moving faster. In many environments, good enough shipped today beats perfect shipped later.

2. Engineers are building interfaces without waiting for design
   AI-generated UI is accessible, responsive, and usable. Not beautiful (yet) but functional.

3. Executives are questioning design ROI
   When engineering velocity accelerates and design timelines remain unchanged, design becomes the obvious bottleneck.

The most painful part is they’re often not wrong to work around design and not because designers lack skill, but because the process has become misaligned with the pace of modern product development.

---

Here’s What They’re Missing

Those PMs and engineers shipping without design are also shipping:

• Inconsistent experiences that erode brand trust - Every feature feels like it came from a different product

• Solutions that solve surface symptoms instead of root problems - They’re answering the question asked, not the problem that matters

• Features that technically work but miss emotional resonance - Functional but forgettable

• Systems that scale horizontally but don’t scale conceptually - Each new feature makes the product harder to understand

The skills that made designers valuable are more critical than ever:

• Systems thinking that sees how pieces connect

• Empathy that understands unstated user needs

• Taste that elevates from functional to delightful

• Strategic thinking that solves the right problem

The problem is the process we’re using to deploy design skills, the same process taught in universities, on UX courses and at play in many teams.

---

When process becomes the product, design value erodes

Over time, design has accumulated a thick layer of ceremony:

• workshops as default

• artefacts as proof of progress

• frameworks as signals of rigour

• alignment as a deliverable in its own right

What began as scaffolding has slowly hardened into dogma.

In many teams, design is now evaluated less on outcomes and more on whether the process was “followed correctly.” This is why design often feels simultaneously busy and sidelined: producing work, but not always shaping direction.

---

Something has broken and it isn’t design

The skills that made designers valuable: empathy, synthesis, systems thinking, taste…are more important than ever.

The processes designed to protect and amplify those skills were built for a different technological reality.

The design process we’ve defended for years no longer fits the environment we’re operating in.