Can your Most Appealing Work Also Be Your Biggest Mistake?
March 20, 2026
As an artist and designer, I've always lived with a particular kind of inner conflict. I'll spend hours, sometimes days, on something. Pushing shapes, wrestling with color, getting the spacing exactly where I want it. And when it finally looks the way I imagined, there's a genuine feeling of satisfaction. This is it. This is the one. Then someone actually tries to use it. That gap between what thrills me visually and what actually helps someone do something has humbled me more times than I'd like to admit. I've shipped interfaces I was proud of that confused real people. I've illustrated compositions that stopped me in my tracks but meant nothing to the person they were made for. It took me a while to stop seeing that as a failure of the user, and start seeing it as a failure of the work. This post is me thinking out loud about that tension. Not because I've solved it, I haven't but because I think every designer who cares about craft eventually has to reckon with it.
The Portfolio That Won Nothing.
Imagine a designer, let’s call her Sara, who spent three weeks redesigning a mobile checkout flow for a client. She did everything right. Custom iconography. A refined type scale. Generous whitespace. A soft, neutral palette that felt premium without being cold. When she posted the design on Dribbble, it received hundreds of likes. The client loved the presentation. Then came the usability test. Five users. One simple task: buy a product and check out. Three of them couldn’t find the “Continue to Payment” button on their first attempt. The button was there, clearly visible, yet it blended so softly with the rest of the interface that it disappeared into the composition. The call-to-action had become decoration. Sara had designed a beautiful dead end.
Aesthetics Isn't the Enemy, Ego Is.
Let’s be clear: this isn’t an argument against beautiful design. It’s not a call to make things ugly in the name of usability. That’s a false trade-off and anyone who frames it that way is selling you something. The real problem begins when aesthetic decisions stop serving the work and start serving the designer. It happens subtly. You establish a visual language and feel compelled to protect it. You choose a muted palette, and suddenly a bolder button color feels like a betrayal of the system. You create a layout that holds together so elegantly that you hesitate to disrupt it—even when disruption is exactly what the user needs. That’s ego, dressed up as craft. The best design is ruthlessly in service of the person using it. Sometimes that means a button louder than you’d prefer. A font size larger than feels refined. A layout that prioritizes clarity over composition. Not every screen needs to belong in a design award showcase. Some screens just need to work.
The Hierarchy Problem.
Here's the specific mistake that catches even experienced designers: visual harmony and functional hierarchy are not the same thing. Visual harmony is about how elements relate to each other — balance, rhythm, consistency. It's what makes a design feel considered and coherent. Functional hierarchy is about what a user sees first, second, third — and what they're compelled to do. It's what makes a design actually usable. The two can coexist beautifully. But when you prioritize harmony at the expense of hierarchy, you get Sara's checkout screen. Everything looks like it belongs. Nothing tells you where to go. A strong call-to-action needs to break the pattern slightly. A critical error message needs to feel urgent, not tasteful. A navigation item that matters needs visual weight, even if that weight disrupts the grid. These aren't bugs in your design system. They're features.
What to Actually Do About It.
Test with real people before you fall in love with the work. Not after. Not to validate, but to challenge. If you only test once you're attached, you'll rationalize what you see. Ask the dumb question out loud: "Can someone who has never seen this find what they need in under five seconds?" Not a designer. Not a developer. Someone who doesn't care about your kerning. Separate your reviews. Do one pass for aesthetics — does this feel right, is the system coherent, is the typography working? Then do a completely separate pass for function — where does the eye go, what's the hierarchy, what's the user supposed to do next? Mixing the two in a single review is how beautiful dead ends get approved. And finally: learn to love the loud button. Not every interaction is an opportunity for restraint. Sometimes the most sophisticated design decision you can make is to make something obvious.
Good Design Doesn't Ask to Be Noticed.
The irony of great UI and UX is that when it's working, no one sees it. The user just moves through the experience. They find what they need. They complete the task. They don't think about the palette or the grid or the micro-interactions — they just feel like the product understood them. That's the brief. Not "make something that looks like good design." Make something that works so well it becomes invisible. Sara's redesign eventually shipped — after a second round where she made the CTA button 20% larger, increased its contrast ratio, and gave it a fill instead of an outline. She hated how it looked for about two days. Then a second usability test came back clean. Five out of five users completed the flow without hesitation. She stopped hating it pretty quickly after that.
Comments