Charm of Simplicity

Why the best interfaces disappear, and the worst ones turn heating your house into reading a legal document.

Listen to this note

Published

Jul 12, 2026

Topic

Design

TL;DR Every extra setting is a designer who lost their nerve. Complexity compounds, simplicity has to be earned by cutting, not adding. The whole discipline comes down to three moves: cut until it breaks, default instead of ask, hide the machinery.

Nobody argues for less

Your thermostat has forty settings and you use two.

That’s not a feature. It’s a confession, the confession of a team that couldn’t decide what mattered, so they shipped everything and let you sort it out.

Simplicity isn’t the absence of features. It’s the presence of a decision.

Every interface you touch is really an argument. The designer is arguing for what matters and what doesn’t. Most of them lose their nerve halfway through. They add the toggle “just in case.” They keep the setting nobody asked for because removing it feels like admitting a mistake. So the product grows outward instead of inward, until turning on the heat feels like reading a legal document.

Here’s the physics of it: complexity doesn’t stay flat, it compounds. One extra option seems harmless. Ten extra options force you to build a mental model just to survive the interface. You’re not choosing a temperature anymore. You’re debugging a system.

Simplicity is a filter, not a style

Nest didn’t win because it was smarter. It won because it took a wall of buttons and turned it into one dial. Turn it, it learns, you never open a menu again. Dieter Rams said it decades earlier: good design is as little design as possible. Half the industry still treats that as a slogan instead of a discipline.

  1. Cut until it breaks. Remove features until the product stops working, then add back exactly one.
  2. Default instead of ask. Every question you put in front of a user is a tax. A good default beats most choices.
  3. Hide the machinery. Complexity can live in the backend. It should never live on the screen.

I’ve shipped products with settings pages I was proud of: dense, powerful, configurable. Users opened them once and never came back. The ones people loved had almost nothing to configure. That still stings a little.

The charm of simplicity isn’t that it’s easier to build. It’s harder. You have to know exactly what you’re building before you can cut everything else away. But the reward is a product that disappears into the task. Nobody thanks a thermostat for being simple. They just stop noticing it’s there.

That’s the whole point.