Good UX vs. Poor UX: The Difference Users Feel But Can’t Always Explain

A quiet breakdown of the small decisions that make or break an experience.

From my experience in design reviews, I’ve started to notice a pattern: when a screen looks polished, everyone in the room relaxes. Nice colors, tidy spacing, a modern font, then ship it. But looking good and working well aren’t the same thing, and users find that out the hard way, usually while trying to cancel a subscription or track a package.

Good UX isn’t a style. It’s whether someone can do what they came to do without stopping to think, “wait, what just happened?”

That’s really the only question I ask when I review a design: can the user move through this without unnecessary confusion? Everything else - the buttons, the copy, the loading spinners, is just in service of that one thing.

Here’s what that looks like in practice.

01. Navigation shouldn’t make people think

A good nav bar answers three questions instantly: where am I, where can I go, and how do I get there. “Home · Explore · Saved · Profile” does that without effort. Something like “Start · Discover · More · Workspace” makes people pause and guess - and every pause is a tiny tax on their patience.

If users have to interpret your menu before they can use it, the menu has already failed.

02. Give people the right information, not more information

There’s a habit in tech writing of over-explaining. “Your package has been processed and is currently with the shipping carrier and will arrive soon” - technically informative, practically useless.

Compare that to:

Your order is on the way 🚚
Arriving tomorrow, 10 AM–12 PM
Confirmed → In transit → Out for delivery

Same facts. Completely different experience. Good UX isn’t about adding more text, it’s about structuring what’s already there so it’s scannable at a glance.

03. Buttons should say what happens next

“Submit,” “Go,” “Proceed” - these tell you nothing. “Continue to payment” tells you exactly what you’re about to do. This matters most on the actions people hesitate over: deleting an account, placing an order, saving changes. A vague label turns a simple click into a small moment of doubt.

04. Forms: ask for what you need, when you need it

Nobody wants to fill out ten fields before they’ve even seen your product. A signup form asking for just an email and password gets people in the door -you can always ask for the rest later, when it’s contextually relevant.

That said, I want to push back on a common myth: fewer fields isn’t automatically better UX. If a field is genuinely necessary, the goal isn’t to delete it; it’s to make it easy to fill in. The real question is whether the field earns the effort it asks for.

05. Tell people what’s happening

Click “Pay Now” and see… nothing. Did it work? Should you click again? Did you just get charged twice? That silence is one of the most common (and avoidable) UX failures out there.

“Processing payment…” followed by “✓ Payment successful” costs almost nothing to build and completely changes how safe the interaction feels. This applies anywhere something takes a moment- uploads, downloads, form submissions.

06. Errors should help, not just report

“Error 400 - something went wrong” tells the user nothing and blames no one in particular. “Password doesn’t meet the requirements - use at least 8 characters and one number” tells them exactly what to fix. Even better is preventing the error in the first place with a live checklist as they type.

The goal of an error message isn’t to log what broke. It’s to get the user unstuck.

07. Accessibility isn’t a phase two

It’s tempting to treat accessibility as a checklist you run at the end of a project. It should be baked in from the start - color contrast, keyboard navigation, screen reader support, touch target size. A simple example: don’t rely on a red border alone to flag an invalid field. Say “email address is invalid” so it’s not just visible, it’s understandable, to everyone.

08. Consistency means users only have to learn your product once

If one screen says “Save,” another says “Submit,” and a third says “Done” - for the exact same action - you’re quietly asking users to relearn your app every time they turn a corner. Once someone understands a pattern, they should be able to reuse that knowledge everywhere else in your product. That’s what consistency actually buys you: less thinking, less friction.

09. Performance is UX, not just engineering

A five-second silent wait after clicking “upload” feels like a freeze, even if it’s just… loading. “Uploading… 75%” turns the same wait into something users can trust. People are far more patient when they understand what’s happening - the delay isn’t usually the problem. The uncertainty is.

10. Cut effort, not necessarily steps

There’s a persistent myth that fewer screens always means better UX. Not true. A five-step checkout is fine if every step earns its place. What actually hurts users is unnecessary effort; a field the system could’ve remembered, a decision that didn’t need to be theirs to make, a step that could’ve been automated. Don’t count screens. Count friction.

11. Let hierarchy do the talking

Ever seen a product card yelling “50% OFF! LIMITED TIME! BEST QUALITY! BUY NOW!” all at once? None of that information is wrong - it’s just all competing for the same attention at the same volume. Good hierarchy creates a path: product, then description, then price, then action. This is where UI and UX genuinely overlap - visual design either guides the eye or fights it.

12. A good interface teaches itself

If your product needs a manual for basic tasks, that’s a UX gap, not a user problem. Compare “Configure the required parameters before initiating the workflow” to “Let’s get started: here’s a quick guide.” Same intent, wildly different accessibility. Familiar words, clear labels, and a little onboarding go a long way toward making a product feel intuitive on the first try.

Good UI doesn’t automatically mean good UX

This is the distinction I wish more teams internalized: an interface can have beautiful typography, perfect spacing, smooth animations and still bury a frequently used action behind five clicks. It’ll look great in a portfolio shot and still frustrate the person actually using it.

UI is how the interface communicates. UX is how the entire experience works. They support each other, but one can’t cover for the other’s mistakes.

The question worth asking

Next time you’re reviewing a design yours or someone else’s, resist the urge to just ask “does this look good?” Ask instead:

Can I understand what this screen is for? Can I find what I need? Do I know what will happen before I click? Does it tell me what happened after? If I mess up, can I recover? Can everyone actually use this?

When UX is done well, people don’t notice it. They just find what they need, understand it, act on it, and move on with their day. Nobody writes a five-star review that says “the button label was really clear” - but they definitely notice when it isn’t.

That quiet, invisible ease is the whole job.

Good UX vs. Poor UX: The Difference Users Feel But Can’t Always Explain was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.