(Don't) Trust the design process
TL;DR
The design process was built for a slower era. AI's raised the floor on "good enough," so craft and judgment are what actually differentiate now. Sometimes the solution comes before the problem statement, shipping is the start not the finish, intuition is earned pattern recognition, frameworks are tools you bend, and delight counts even when it's not in the brief. Trust your judgment over the ritual.
New quarter, new plan. No problem, you know the drill. Research. Personas. Journey map. Problem statement. Brainstorm. Wireframe. Test. Polish. Ship.
You followed every step. So the outcome should be great, right?
Not necessarily. The world we're designing in has changed. The process hasn't.
The process was built for a different era
"Trust the process" used to be reassuring. It's what gave design a seat at the table, what moved us from "making things pretty" to shaping strategy.
But look at what's changed since. AI can generate a working prototype in minutes, sometimes before a designer's finished the problem statement. Teams are smaller and roles are broader, so there's no time for ceremony. And users were never going to care about your journey map anyway. They care about how the product feels.
The old process rewards documentation. This moment rewards taste.
Craft is the differentiator now
AI raised the floor. "Good enough" is easy to generate. What's hard, and what actually matters now, is judgment.
The products people happily pay for don't feel like they came from a checklist. They feel cared for. And that kind of care rarely shows up in a process artefact.
How the good stuff actually happens
A few things I keep noticing, in my own work and everywhere I look:
Sometimes the solution comes first. Anthropic's Artifacts feature reportedly grew out of a prototype that got people excited internally, before anyone had fully defined the problem it solved. In fast-moving spaces, that order is fine.
Shipping is the start, not the finish. After FigJam launched, the team kept refining for ages: snapping behaviour, selection states, colour, type, the tiny interactions. None of that fits on a double-diamond diagram. Craft isn't a step. It's a habit you keep paying into.
Intuition is pattern recognition, not guessing. You build it by reading feedback, watching sessions, tracking usage, over and over. It just doesn't need a name every time you use it.
Frameworks are tools, not rules. Five-day sprints become three. Documentation gets skipped for prototyping. The point was never the ritual, it was the thinking underneath it.
Delight counts even when it's not in the brief. FigJam's stamps and cursor chat weren't born from a tidy problem statement. They were quick, a little rough, and they made people smile in a meeting. That reaction was the signal.
Trust yourself instead
If great design were just about following steps, anyone could do it.
Our value was never in executing the ritual perfectly. It's in making good decisions under uncertainty, in knowing when to prototype first, when to obsess over a detail, when to trust your gut, when to bend the framework.
There's no single manual anymore. We're writing it as we go. Uncomfortable, sure. But also kind of the point.
