Good product design isn't about Figma
I've been thinking about this for a while and it keeps getting clearer: good design isn't about making things complicated. It's definitely not about the Figma file.
And I'm not saying this from the outside. I spent about two years being very good at exactly the part that doesn't matter.
The three weeks I'd like back
At one company I built a design system before we needed one. Twelve components, every variant, every state, naming convention documented, a page explaining the naming convention.
Three weeks. It was the best-looking file I had ever made.
Nobody used it. Not out of hostility, the team was four people, they were shipping fast, and the system solved a problem we didn't have yet. A design system exists to stop the same decision being made twice, differently. We had not made most of those decisions once.
What we actually needed that month was for someone to sit with the sign-up flow, which was losing about half the people who started it. I didn't do that, because the design system was the kind of work that looks like seniority.
That's the whole essay, really. The rest is what I took from it.
Design isn't a performance
Design has often turned into a performance. Processes, workshops, tokens, ideation sessions, double diamonds, feedback loops, and meanwhile nobody is solving anything. It becomes theoretical, perfect on the surface, and disconnected from the product.
You don't need to bring out the double diamond every time somebody speaks. You don't need four weeks of research to move a button. You don't need to justify every decision as if it were going to be peer reviewed.
You need to think clearly, talk to your team, understand the context, and design something that works. Nothing more.
The useful version of “how much process” isn't a rule, it's a question: how expensive is it to be wrong? Moving a button is a reversible decision — decide it this afternoon and change it tomorrow if it's wrong. Choosing who the product is for isn't, that one earns the fortnight. Most process arguments are really arguments about a cost nobody has bothered to estimate.
Stop designing for the file
The cult around Figma is the same mistake in a different costume. Spotless file, perfect auto-layout, endless variants, carefully named components, and then the person on the screen has no idea what to do.
Everything can be immaculate inside the file and still be wrong about the product, because the file isn't the product, it's a drawing of the idea. If the idea is bad, a beautiful drawing just means it takes longer for anybody to notice.
We aren't designing to get likes from other designers. We design so somebody understands what they can do, how to do it, and why it's worth it. That doesn't come from making it pretty. It comes from making a decision and being able to say why that one and not another.
What I actually look at now
Can they tell what to do? Not “is it discoverable”, can a real person, at speed, with something else on their mind, tell what to do. This is unglamorous and it's where most of the value is.
Why this and not the other one? If I can't answer that in a sentence, I haven't designed anything, I have arranged things. Anybody can make a screen. The hard part is saying why that one.
What does it cost the team? A design that's right and takes six weeks can be worse than one that's 80% right and takes six days, depending on what else is on fire. Designers are bad at pricing their own work in team time, and I include myself.
The honest caveat
Everything above comes from small teams, two to forty people, mostly startups, mostly with less time than the plan needed. In a large organisation with twelve squads touching the same surface, the design system I mocked isn't overhead, it's the only thing preventing chaos, and the person who built it was right.
So I'm not saying process is bad. I'm saying it's a cost, it should be paid deliberately, and the most common way to get this wrong is to buy the process of a company forty times your size because that's the process you read about.
Design isn't about you. It's about the team, the product, and the person on the other side of the screen. If you can do that without overcomplicating it, better.
Questions people ask about this
01Is Figma necessary to be a product designer?
You need a way to show people what you mean, and Figma is the current best one. What isn't necessary is the craft around the file, the naming conventions, the variant matrices, the immaculate auto-layout. Those help a team when the team is large enough to need them, and cost you time when it isn't.
02What actually makes product design good?
Whether the decision inside it was right, and whether the person using it can tell what to do. A screen that's beautiful and wrong is worse than a plain one that's right, because being pretty means it takes longer for anybody to question it.
03How much research does a design decision need?
As much as the cost of being wrong. Moving a button is reversible in an afternoon, so decide it in an afternoon. Choosing what the product is for isn't, so spend the fortnight. Most process arguments are really arguments about a cost nobody has estimated.
04Do design systems slow teams down?
They do when they arrive before the repetition does. A system solves the problem of the same decision being made twice differently. If that hasn't happened yet, you're maintaining an answer to a question nobody asked — I've built exactly that, and it took three weeks.