Process can’t tell you if it’s good
Early in my career, I was sure good design came out of good process. I followed the latest frameworks and spent hours on diagrams and walls of sticky notes, mapping every step from research to handoff. The artifacts looked rigorous. The work was fine.
Then I stepped back. I spent those hours sketching and prototyping instead, with more freedom and more play, and the work got much better. That’s when I realized process becomes a trap when you let it take over.
A framework is a map of the work
Frameworks have real uses. The Design Council’s Double Diamond (discover, define, develop, deliver) gives a team a shared vocabulary for where a project stands. The Stanford d.school’s version of design thinking (empathize, define, ideate, prototype, test) has taught the basics of design to people who never went to design school.
But a map of the work doesn’t do the work. You can complete every phase of a framework and still ship something mediocre, because none of the phases asks whether the result is any good. Pentagram partner Natasha Jen made this case in her 2017 talk, “Design Thinking Is Bullsh*t”. In practice, she argued, the method had shrunk to sticky notes on a wall, with critique and evidence left out.
Process also costs time. Every framework adds meetings and documents, and those hours come out of the time spent making the thing.
Plumbers solve problems too
Most frameworks treat design as problem-solving, and it is. So is plumbing. What a designer adds is judgment about how a solution should look and feel: whether a transition is too slow, whether a typeface reads as trustworthy, whether an empty state feels kind or cold, whether a screen has one element too many.
Those calls don’t come from a phase in a diagram. They come from someone who cares about the answer and has the taste to tell good from almost good. That judgment is what people mean by craft, and you won’t find it as a phase in any framework.
Apple picked the iPhone keyboard by demo
In Creative Selection, Ken Kocienda describes how Apple settled the iPhone’s software keyboard. Scott Forstall had the engineers on the project set aside their work and build competing keyboard prototypes. The team tried them, picked the strongest, and kept refining it in the same loop: make a demo, show it, judge it, make the next one.
That loop is a process too, but a small one, and judging the work is the step it repeats. Kocienda calls it creative selection. It’s about as far from a sticky-note wall as design gets.
Use process, and notice when it takes over
I still use process. Research and design systems earn their place on any project bigger than a weekend. What I watch for is the moment they start replacing the work: more meetings about the design than hours spent designing, a deck where a prototype should be, a checklist that’s complete while the screens are still mediocre.
When I catch that happening, I go back to the part that got me into design: making something and looking hard at whether it’s good.
Spencer Camp






