Design Is Decisions, Not Decoration

<p>Most people think design is about making things look good. That's decoration. Design is about making things <em>work</em> — and that requires saying no far more often than saying yes.</p> <h2>Every element is a decision</h2> <p>Every pixel of spacing, every color choice, every word in a button. Good designers don't add things. They remove everything that doesn't earn its place.</p> <p>I've killed beautiful components because they didn't serve the user's goal. I've chosen ugly-but-clear over pretty-but-confusing. Every time, the metrics proved the boring choice right.</p> <h2>The subtraction test</h2> <p>Before you add anything to a screen, ask yourself four questions:</p> <ul> <li>What job is this element doing for the user?</li> <li>If I removed it, would the page still work?</li> <li>Is it here because it <em>helps</em>, or because it <em>looks good</em>?</li> <li>Does it make the primary action more obvious, or less?</li> </ul> <p>If you can't answer the first question in one sentence, cut it. If the page still works after you cut it, leave it cut.</p> <h2>Invisible is the goal</h2> <p>The best interfaces feel invisible. You don't notice the design — you just accomplish what you came to do. That invisibility is the hardest thing to achieve, and it comes from relentless editing, not relentless adding.</p> <p>Stripe's checkout. Linear's command palette. Apple's share sheet. None of them feel "designed." They feel inevitable. That's not luck — it's a thousand decisions about what to leave out.</p> <h2>Start with a knife, not a brush</h2> <p>Next time you're designing something, resist the urge to make it prettier. Instead, ask what you can remove. What's here because it looks good versus because it helps? What happens if this section disappears?</p> <p>The answer will make your work ten times better. Design is decisions. Start making harder ones.</p>