DEV Community

Cover image for Words from the Best Web Designer
Florence
Florence

Posted on

Words from the Best Web Designer

New week. New screens. Same question.

Am I designing for aesthetics or for clarity?

At the start of this project, I thought I already had the answer.

The layout was clean.
The typography felt right.
The colors worked beautifully together.

On the surface, everything looked “done”.

But then I stepped back and looked at it like a user, not a designer.

And I noticed something uncomfortable.

Nothing was wrong… but nothing was obvious either.

The message wasn’t hitting instantly.
The hierarchy wasn’t guiding enough.
The design looked good, but it wasn’t doing enough work.

So I went back in.

Not to redesign everything. Just to refine.

I adjusted spacing.
Tweaked contrast.
Shifted emphasis.
Tested different visual tones.

Same content. Same structure.
But a completely different feeling.

One version felt safe and minimal.
The other felt more confident, more intentional, more aligned with the kind of work I want to attract.

That process reminded me of something simple:

• Users don’t care how polished it looks if they have to think too hard
• Clarity builds trust faster than aesthetics ever will
• Good design is not what you add, it’s what you make obvious

This week, I’m focusing less on making things “look good” and more on making them make sense instantly.

Because at the end of the day, the goal isn’t to impress.

It’s to be understood.

So I’ll ask again:

Are we designing something that looks good, or something people can actually use without thinking?

Top comments (0)