Are you designing for aesthetic or for action?

There’s a quiet tension that exists in design work. The version that looks best in a mockup isn’t always the version that works best for users.

Minimal forms with no visible labels look clean in a Figma file. Low contrast text feels sophisticated on a landing page. Icon-only navigation looks uncluttered in a portfolio screenshot.

But none of those users are in the Figma file. They’re on a phone, in bad lighting, under time pressure, trying to complete a task.

When aesthetic decisions win out over usability, users lose. And when users lose, people who rely on assistive technology lose big. Low contrast text that’s inconvenient for sighted users is completely unusable for someone with low vision. A form that’s slightly confusing without visible labels is completely broken for a screen reader user.

The question worth asking before shipping any design decision: Does this help users take action, or does it just look good in a screenshot?

Aesthetics and usability aren’t always in conflict. But when they are, usability must win. A form that users can complete beats a form that looks beautiful. Text users can read beats text that feels elegant.

Good design doesn’t just look nice. It works right.