Pretty Doesn’t Fix Broken

By a UX Design Student Who’s Tired of Watching It Happen.

By Vaishnav Kanakkassery Suresh • August 2026

Let me tell you what nobody warned me about before I enrolled in a UX program.

You spend months learning how to conduct user research; you study interview techniques, affinity mapping, journey mapping, and usability testing methods. You build mental models and personas from real data you know. You start to believe, genuinely believe that this is how things work.

Then you look at the actual job postings and talk to people already in the field. And a picture starts to form in your mind that is a lot less flattering than the case studies in your textbooks.

Many companies don’t want a UX designer. They want a decorator.

They want someone to show up at the end of a product creation cycle, open Figma, and make things look clean, with better fonts and rounder corners. A hero image that should feel “premium.” Ship it by the weekend. The research phase? Ah… not needed. The testing? Some other time. The user flows? The dev team already built it. Just make it pretty.

That is the “coat of paint” trap, and it is everywhere.

Here’s the thing about paint: it can never fix a crumbling wall.

Everyone will have an experience using a product where the interface was gorgeous, muted tones, clean typography, and smooth micro-animations. It looked like it belonged in an awards showcase. But completing a basic task required jumping between three separate screens, re-entering information the system already had, and ultimately hitting a dead end with no error message,  just silence.

Beautiful. Completely broken.

No amount of visual beauty can fix a navigation that creates user friction and backtracking. No rebrand rescues a checkout flow that hemorrhages customer experience at the payment screen. These are not aesthetic problems. They are structural ones, and the only way to uncover them is through proper usability testing with actual users, actual tasks, and actual friction points, documented and addressed systematically.

A visual redesign without that groundwork is never a solution. It causes delays.

To the clients and stakeholders reading this: skipping the UX phase is not saving you time or money. It is a very expensive gamble that you think is efficient.

When you hand a designer a fully built product and ask for a final visual refresh, you lock in every bad decision the team has already made. The dev costs to fix a broken user flow after product launch are significantly higher than the cost of finding it in a low-fidelity prototype. The user trust you lose when someone can’t complete a purchase doesn’t show up on a spreadsheet, but it absolutely shows up in company turnover and one-star reviews.

Research is not a nice-to-have. It is the foundation. Without it, you are guessing, and your users are the ones paying for it, and the company in the long run.

My generation of designers did not sign up to make just pretty screens.

We want to build things that actually work for people, in real contexts, with real friction accounted for from day one. We want to sit in the room when decisions are made, not get called in after everything and add a fresh coat of paint over a broken structure.

The industry asked us to learn better. Now let us use it.