Good Design Starts with What You Leave Out

When people picture product design, they picture things being added — new features, new screens, new interactions. But a lot of the work that actually matters is the opposite: the stuff that never makes it in.

Designers spend most of their time surrounded by ideas. Stakeholders have requests, users have needs, every meeting turns up another thing that seems worth building. Left alone, products only ever get bigger. Finding things to add was never the hard part. Deciding what to leave out is.

More features rarely means a better product

There's a common assumption that more functionality equals more value. In practice, every feature has a cost — it's one more decision for the user, one more thing for the team to maintain, one more edge case to handle. Each one might be useful on its own, but stacked together they turn into something nobody can navigate. Cutting features isn't about making the product do less. It's about keeping it legible.

I saw this play out on a logistics platform I worked on. Everyone in the room had a feature they wanted — dashboards, options, configurability, the usual pile. Then the CEO said something that reset the whole conversation. The drivers using this thing don't want software. They've been on the road all day; they want to finish the job and get home to their families. So the question stopped being 'what can we add' and became 'how do we get a driver through this as fast as humanly possible so they can put the phone down and leave.' Half the features people were excited about didn't survive that question — not because they were bad ideas, but because every extra tap was one more thing standing between a tired person and their front door.

The smallest version that still works

Not every good idea belongs in the first release. In planning sessions, feature lists grow fast, especially when everyone's excited about where the product could go. Instead of trying to fit it all in, the question I keep coming back to is: what's the smallest version of this that still does the job?

That one question tends to change the room. It moves the conversation from "what could we build" to "what do we actually need first" — which are very different discussions.

On an AI content creation project called Virtual Studios, the discovery phase left us with about forty features on the table. With a fixed deadline and limited resources, building all of them wasn't an option — so we forced the hard conversation and ranked them. Twelve made the cut: the ones the platform genuinely couldn't run without. Everything else went to a parking lot to revisit later. That cut wasn't about calling the other ideas bad — it was about admitting that a focused product that ships beats a complete one that doesn't.

Simplicity is a decision, not a default

The products we all admire feel effortless, and that's exactly the trick — what you don't see is the hundreds of small calls about what got removed, postponed, or never built. Effortless is expensive. It almost never happens by accident; it's the residue of a lot of people repeatedly choosing restraint over "sure, let's add it."

Part of a designer's job is to be the person asking whether something needs to exist at all. Every feature competes for attention, every screen asks for someone's time, and once it's in, it's hard to take back out. Saying no to a genuinely good idea is uncomfortable — but it's often the thing that keeps the good ideas from drowning each other.

Good design doesn't start with what you add. It starts with being honest about what you can do without.