Design process is dead… or not?

There’s a lot of talk right now about whether the traditional design process is dead. Lately Jenny Wen’s conversation with Lenny Rachitsky made that clear.

I understand the argument. The old version of process can feel slow: long discovery cycles, polished mocks, stakeholder reviews, and only then a prototype. In a world where AI can help us generate, build, test, and revise ideas much faster, that kind of process can feel outdated.

And some of it is.

Rapid prototyping and iteration are real advantages. We should use them. The distance between an idea and something testable has collapsed. Designers can now explore more directions, make ideas tangible earlier, and learn faster.

But faster making does not eliminate uncertainty.

It just makes it easier to act before we understand what we are doing.

Good designers compress the process

Experienced designers rarely follow process in a perfectly linear way. They sketch while researching. They prototype to understand the problem. They test ideas informally. They rely on intuition. They make fast calls. From the outside, this can look like skipping process. But often, it is not skipping. It is compression.

A senior designer can move quickly because they have internalized years of user patterns, product constraints, business context, failed ideas, and previous research. What looks like intuition is often accumulated process running in the background.

That distinction matters.

“Experienced designers can move faster” is not the same as “nobody needs process.” One is about expertise, because the process was only means to an end.

Process was never the point

The design process was never valuable because it gave us a tidy sequence of steps. It was valuable because it helped teams reduce risk.

Those questions do not disappear because we can build faster. If anything, they become more important. When it becomes easier to generate solutions, it also becomes easier to generate convincing wrong solutions.

A polished prototype can create a false sense of confidence. It can make an idea feel inevitable before anyone has asked whether the idea should exist.

That is why process still matters—not as a rigid checklist or a ceremonial double diamond, but as a way of thinking. Its purpose is to help teams understand problems, explore possibilities, evaluate tradeoffs, and learn from what happens next.

How much structure a team needs, however, depends heavily on its environment.

UX maturity changes the answer

The right amount of process depends on the maturity of the organization.

In a mature product organization, teams may already have strong user understanding, clear product principles, research habits, analytics, and a shared language for decision-making. In that environment, designers can move quickly with lightweight framing and evaluation because much of the foundational work is already in place.

But many teams are not operating in that context.

In lower-maturity organizations, UX work may be inconsistent, under-resourced, or dependent on individual effort. Research may happen only when someone pushes for it. Design decisions may be driven by the loudest stakeholder, the fastest engineer, or the most urgent business request.

In those environments, abandoning process does not create freedom. It creates confusion.

Process provides a shared framework for making decisions. It makes assumptions visible, helps designers explain why something matters, and creates evidence that can survive beyond a single meeting.

Without that foundation, “trust your intuition” can easily become “trust whoever has the most power.”

Speed is not direction

AI is changing the speed of design work. That is exciting.

We can make more. We can test earlier. We can explore ideas that used to be too expensive to try. We can use prototypes not just to validate solutions, but to understand problems more clearly.

That is a real shift.

But speed is not the same as direction.

A team can move incredibly fast and still build the wrong thing. A prototype can be technically impressive and strategically irrelevant. A feature can feel magical and still fail to meet a real user need.

The job of design is not just to produce artifacts. It is to improve judgment.

Sometimes that means doing research before making anything. Sometimes it means making something quickly so people can react to it. Sometimes it means testing one risky assumption instead of debating it for weeks. Sometimes it means skipping formal process because the risk is low and the team already knows enough.

The key is not following every step.

The key is choosing intentionally.

Speed is not direction

I don’t think the future of design is “no process.” I think the future is process literacy.

Designers need to know when to slow down and when to move fast. When to start with a prototype and when to start with a problem statement. When intuition is enough and when evidence is needed. When a lightweight critique will do and when usability testing is necessary.

That judgment is the work.

AI can accelerate the mechanics of design, but it cannot decide which risks matter. It cannot replace the responsibility of knowing what needs to be understood, what needs to be tested, and what can safely be assumed.

So no, I don’t think the design process is dead.

The performative version might be. The rigid, artifact-heavy version probably should be.

But the purpose of process is still very much alive: to help teams understand problems, evaluate ideas, and make better decisions under uncertainty.

AI gives us a faster loop; it does not remove the need to think.