Good Design Starts with What You Leave Out

When people think about product design, they often think about what gets added—new features, new screens, new interactions, and new capabilities.

But some of the most important design decisions happen when nothing is added at all.

As designers, we're constantly surrounded by ideas. Stakeholders have requests, users have needs, teams have suggestions, and every discussion seems to uncover another feature worth building. Over time, products naturally become more complex.

The challenge isn't finding things to add.

The challenge is deciding what not to build.

More Features Don't Always Create Better Products

A common assumption in product development is that more functionality creates more value.

In reality, every feature introduces a cost.

It adds decisions for users, increases complexity for teams, and creates additional maintenance over time. While individual features may seem useful on their own, the combined experience can quickly become overwhelming.

Good design isn't about reducing capability.

It's about preserving clarity.

The Power of Prioritization

One lesson I've learned across product projects is that not every good idea belongs in the first release.

During discovery and planning sessions, it's common for feature lists to grow rapidly. The temptation is to accommodate everything, especially when stakeholders are excited about the product's potential.

Instead, I prefer asking a different question:

What is the smallest version of this product that still delivers value?

That question often changes the conversation.

It shifts focus from possibility to priority.

Designing the MVP

An MVP isn't about delivering less.

It's about delivering what matters most.

The strongest MVPs focus on solving a core problem exceptionally well rather than solving every possible problem at once.

Features that don't directly support that goal can often wait until later.

This isn't about rejecting ideas.

It's about creating room for the right ideas to succeed.

Simplicity Is a Decision

Many of the products we admire feel effortless to use.

What we don't see are the hundreds of decisions made behind the scenes about what was removed, postponed, simplified, or never built in the first place.

Simplicity rarely happens by accident.

It's usually the result of deliberate choices and constant prioritization.

Clarity Through Restraint

Designers are often asked to create solutions.

Sometimes our responsibility is the opposite.

Sometimes we need to challenge assumptions, question complexity, and protect the product from unnecessary additions.

Because every feature we add competes for attention.

Every screen we create asks for time.

And every decision we make shapes the experience users ultimately have.

Good design doesn't start with adding more.

It starts with understanding what can be left out.