One of the biggest misconceptions about design is that if something looks modern, clean, and minimal, it must also be easy to use. As a UX designer, I can say with full confidence that this is one of the fastest ways teams get usability wrong. A product can be visually impressive and still create confusion, hesitation, and friction for the user.
I was reminded of this during a recent in-store checkout. The setup looked sleek and intuitive, with a screen, a scanner, and the familiar self-checkout look. I did what I always do and scanned the item, but nothing happened. I tried again, still nothing. An employee finally told me the item wasn’t meant to be scanned. Instead, I had to place it in a recessed area so the system could detect it automatically.
This might seem like a small issue, but it shows a big UX problem. The interface suggested one action, but the system needed something else. That gap between what users expect and what the product wants causes friction.
This is why ideas like mental models, affordances, and signifiers are important. People use products with expectations based on what they’ve seen before. If a design includes something familiar, like a scanner, users expect it to work the usual way. That’s not a user mistake, it’s a normal reaction. Good UX takes this into account, and great UX designs with it in mind.
What made this experience even more frustrating was the lack of help. There were no clear instructions, prompts, or feedback to guide me. Good UX meets users halfway by confirming actions, preventing confusion, and gently redirecting people when they make a mistake. Poor UX leaves users guessing, and once that happens, the experience falls apart.
This matters because friction is more than just an inconvenience. In digital products, it affects trust, task completion, satisfaction, and conversion. If users can’t figure out what to do, they might give up. In ecommerce, that means lost sales. On a service platform, it could lead to more support tickets, lower retention, or a bad impression of the brand. Even small friction adds up over time.
As a freelance UX designer, I watch for these moments because they show what teams often miss when they rely on their own assumptions. Internal teams know how the system works, so they stop noticing what’s unclear. Users don’t have that inside knowledge; they only see what’s in front of them. That’s why usability testing is so important. It shows the gap between what designers intend and how users actually behave.
If I were to redesign that checkout, I’d start by making the instructions simpler. If an item needs to go in a detection area, the design should make that clear with labels, visual cues, lighting, and on-screen instructions. If there’s a scanner, it should work as expected or be made less noticeable so it doesn’t confuse people. I’d also add instant feedback, like “Place item here to continue,” so the system helps users right away instead of leaving them guessing.
The main lesson is simple: users don’t experience your intentions, they experience your interface. They interact with your flows, labels, visual hierarchy, feedback, and assumptions. When these things aren’t aligned, even a great-looking product can be frustrating.
That’s why UX isn’t just decoration. It’s about making decisions, providing clarity, and bringing empathy to every interaction. Often, it’s what separates a product that just looks good from one that truly works.