Design, at its surface, looks like decoration.
People see colors, fonts, layouts — the visible layer. But behind every choice is a quiet intention: what should the user feel, and what should they do next?
Recently, I worked on a product where one color became… famous.
It was bold. Vibrant. Instantly recognizable. The team loved it, stakeholders loved it, and during reviews, it was always the part people pointed at and said, “This looks amazing.”
So we used it everywhere.
Buttons, highlights, notifications — it became the identity of the product.
And that’s exactly where the problem began.
Users couldn’t tell what mattered.
When everything is loud, nothing stands out. Primary actions looked the same as secondary ones. Alerts felt no different from regular updates. The interface was beautiful, but it lacked hierarchy.
It didn’t guide. It just existed.
At first, I tried subtle fixes. Adjusting sizes, adding spacing, changing weights. But the confusion remained. The issue wasn’t layout — it was the color itself.
So I suggested something that didn’t go well in the first meeting.
“We need to remove it.”
Not completely, but drastically reduce it. Use it only where it truly matters.
There was resistance.
Why remove something that people clearly liked? Why take away what made the product visually striking?
Because design isn’t about what looks good in isolation.
It’s about what works in context.
We made the change.
The vibrant color was stripped from most elements. What remained was a calmer, more neutral interface. At first glance, it felt less exciting—even to me.
But once we tested it, the difference was immediate.
Users moved faster. They clicked the right things. They hesitated less. And when that bold color appeared now, it actually meant something.
It guided.
That project taught me something I keep coming back to.
Good design isn’t about adding personality everywhere.
It’s about knowing where to hold back.
Because sometimes, the strongest element in a design…
is the one you choose not to use.