Why Great Product Design Starts with Subtraction

There's a moment in almost every product design project where the instinct kicks in to add something. Another feature. Another option. Another screen to explain the thing that wasn't quite clear on the last one. It feels productive — like progress. But more often than not, it's the opposite.

Some of the best design advice I've come across isn't about design at all. It's a phrase from industrial designer Dieter Rams: "Weniger, aber besser." Less, but better. It sounds simple, almost too simple, but after more than a decade of designing digital products, I've come to believe it's one of the few principles that actually holds up under pressure — deadlines, stakeholder requests, shifting requirements, all of it.

The Feature Trap

Every product starts lean. A clear problem, a focused solution, a handful of screens that do exactly what they need to do. Then comes user feedback. Then comes a competitor analysis. Then comes a stakeholder who "just wants one more thing" added before launch. Individually, these requests almost always make sense. Collectively, they slowly turn a focused product into a cluttered one.

The danger isn't any single addition — it's the accumulation. Each new feature adds a small amount of cognitive load, a few more decisions the user has to make, a bit more surface area for something to break or confuse. Multiply that over months or years of "just one more thing," and you end up with a product that's technically more capable but practically harder to use.

Subtraction as a Design Skill

Editing is a skill, just like generating ideas is. Knowing what to remove — a redundant step, an unnecessary setting, a screen that exists "just in case" — takes just as much design judgment as knowing what to build in the first place. It requires stepping back and asking a harder question than "does this add value?" The better question is: "does this add enough value to justify the complexity it introduces?"

In practice, this means treating every screen, field, and feature as something that has to earn its place, not something that gets included by default. It means being willing to say no to good ideas because they're not the right idea for right now. And it means trusting that a smaller, clearer product often outperforms a bigger, more "complete" one — because people can actually use it without friction.

What This Looks Like in Practice

When I start a new product design engagement, one of the first things I do is map out the absolute minimum path a user needs to take to get real value — not the ideal, fully-loaded version, but the leanest version that still solves the core problem. Everything else gets set aside, not discarded, just deprioritized until there's real evidence it's needed.

This approach tends to surface a lot of uncomfortable questions early: Does this onboarding step actually reduce drop-off, or does it just feel thorough? Does this settings panel serve 80% of users, or is it there for an edge case that could be solved another way? Those questions aren't always fun to ask, but they're almost always worth asking before development starts, not after.

The Payoff

Products designed with restraint tend to feel calmer to use. They load faster, because there's less to load. They're easier to explain, because there's less to explain. They're easier to maintain, because there's less surface area for bugs and inconsistencies. And counterintuitively, they often end up feeling more premium — not because they do more, but because everything they do, they do well.

Less, but better isn't about doing less work. It's about being disciplined enough to do the right work, and confident enough to leave the rest out.