Good design doesn’t start with how it looks
There’s a principle in design that has been misquoted and misunderstood for over a century, but its core idea remains sound: form should follow function. In other words, how something looks should be shaped by what it needs to do, not the other way around. The trouble is that aesthetics are visible and immediate. Function often isn’t. So when decisions get made quickly, or by people who aren’t close to the problem, appearance tends to win. The result is work that looks considered but isn’t: beautiful interfaces that confuse people, polished reports nobody reads, websites that win awards and lose customers.
This doesn’t mean aesthetics don’t matter. Visual quality builds trust, signals care and shapes how people feel about what they’re using. But those qualities only land when the underlying design is already doing its job. A well-designed product that also looks good is the goal. A good-looking product that doesn’t work is simply expensive decoration. The sequence is important. First understand the problem, define what the design needs to achieve, then bring visual design to serve that purpose. Reverse the order and you’re solving the wrong thing beautifully.
In practice, this means asking harder questions earlier. Who is this for and what do they need to do with it? What gets in their way? What does success actually look like? The answers to those questions should drive every decision, visual or otherwise.
