At some point in your career, someone will slide a brief across the table and say some version of the following: “We just need someone to make it look good.”
And if you’re a designer, you’ll feel that sentence in your teeth.
Not because aesthetics don’t matter. They do. But because “make it look good” fundamentally misunderstands what design is, what designers do, and why organizations that treat design as decoration consistently produce worse products than organizations that don’t.
What design actually is
Every element on a screen is a decision. The placement of a button. The weight of a heading. The amount of whitespace between two sections. The color of an error state. The label on a form field. None of these are arbitrary — or at least, none of them should be.
Good design is the result of hundreds of small decisions made with intention, each one answering a question: What does the user need to know here? What action do we want them to take? What will they misunderstand if we aren’t careful? What does this communicate about the product before a single word is read?
Decoration is the application of aesthetics without answering those questions. It’s making something look polished while leaving the underlying thinking unresolved. And it shows — not always immediately, but always eventually.
The “make it pretty” trap
Here’s how it plays out in practice.
A startup launches a product. The engineering team has built something functional but rough. Leadership decides they need a designer, but what they actually mean is they need someone to apply a coat of paint — better typography, a consistent color palette, maybe a new logo. They’re not interested in revisiting flows, questioning assumptions, or slowing down to understand users. They just want it to look more credible.
So a designer comes in, makes it look more credible, and the product still doesn’t convert. Users still drop off at the same points. The onboarding still loses people. The core interaction problems that were invisible under bad visual design are now invisible under good visual design — which is arguably worse, because now it’s harder to see what’s wrong.
The aesthetics were never the problem. They were never going to be the solution.
Aesthetics are a tool, not a goal
This is the nuance that gets lost in the “just make it pretty” framing: visual design is not separate from UX. It is UX.
Typography affects readability, which affects comprehension, which affects whether a user understands what to do next. Color communicates hierarchy, state, and meaning — get it wrong and users will miss critical information or misinterpret what an interface is telling them. Spacing creates relationships between elements, guiding the eye and communicating structure. Animation signals causality — this happened because of that.
None of this is decoration. All of it is communication. And communication is, at its core, a functional problem.
The best visual designers I know don’t think about making things beautiful. They think about making things clear. Beauty, when it shows up, is a byproduct of clarity done well.
The decisions that happen before anything looks like anything
The most consequential design decisions are made before a single pixel is placed.
What is this product? What problem does it solve, and for whom? What are the objects a user interacts with, and what can they do with them? What is the hierarchy of information on this screen, and why? What does a user need to understand before they can take the next step?
These are design questions. They don’t live in Figma. They live in research sessions and whiteboard sessions and messy documents full of half-formed thinking. By the time you’re choosing a typeface, the important work is largely done — or it should be.
Organizations that bring designers in at the “make it look good” stage are bringing them in after the decisions that matter most have already been made — usually by people who weren’t thinking about users at all.
What this means for how you hire designers
If you’re a founder, a product manager, or anyone responsible for building a product: the question you should be asking isn’t “can this designer make our product look good?” It’s “can this designer help us make better decisions?”
A designer’s job is to be the advocate for the user in every room they’re in. To slow down the conversation when something isn’t resolved. To ask why before asking what. To push back on assumptions that feel like facts. To translate user needs into product decisions and product decisions into interfaces that communicate clearly.
That’s a strategic function. Treating it as a cosmetic one is leaving the most valuable part of the job on the table.
For the designers reading this
You will encounter clients and stakeholders who see you as a production resource. Who send you finished specifications and ask you to “design them up.” Who override your recommendations because they prefer a different color. Who equate design quality with visual complexity or trendiness.
Your job in those moments isn’t to capitulate or to lecture. It’s to redirect — to bring the conversation back to the user, back to the problem, back to the decision that actually needs to be made. Ask questions. Show your reasoning. Connect visual choices to outcomes.
You can’t always change how people think about design. But you can model what thoughtful design practice looks like, consistently and without apology, and let the work make the argument for you.
Design is not the last step. It’s not the polish applied after the real work is done. It is the work — from the first question asked to the last pixel placed.
