You've used both kinds of interface.
The one where everything is just there — you know where to click, the next step is obvious, you finish what you came to do and barely remember the screen. And the other one: technically it works, nothing is broken, but using it feels like wading through mud. You can't quite say why. It just… drains you.
Here's the thing most people never learn: the difference between those two isn't taste, and it isn't luck. It's science. Every "this feels effortless" and every "why is this so annoying" traces back to how the human mind actually works — and once you know the handful of principles behind it, you stop guessing at design and start fixing the real cause.
This is a practical tour of that science. Not a lecture — a set of design problems you've definitely felt, each one paired with why it happens and how to fix it. By the end you'll be able to look at an interface and name what's wrong, which is the entire difference between decorating and designing.
First, how these three things connect
Quick map, because it makes everything after it click:
- Cognitive science is how the human mind works — how we perceive, remember, pay attention, and make decisions. It's the raw material you're designing for.
- HCI (Human-Computer Interaction) takes what we know about the mind and turns it into principles for how people should interact with systems.
- UX/UI is where those principles actually get applied — the real screens people touch.
So the chain is simple: cognitive science explains the human → HCI turns that into design principles → UX/UI is where you apply them. When a design "just feels wrong," it's almost always violating something one layer down. Good design isn't a mysterious gift — it's these three, connected.
Now let's see it in action. Here are the problems, and the science that fixes each.
Problem 1: "This form has twenty fields and I want to close the tab"
You've abandoned a signup or checkout because it threw everything at you at once — a wall of fields, options, and instructions. It didn't feel hard, exactly. It felt heavy.
The science: human working memory is tiny. We can only hold a few pieces of information in mind at once (this is the heart of cognitive load, and it's why "Miller's Law" gets cited so much). When an interface dumps everything on screen simultaneously, it overloads that limited space, and the brain responds the way it always does to overload: it wants to leave.
The fix: break it up. Split a long form into clear steps. Reveal advanced options only when needed (progressive disclosure). Group related fields so the brain processes chunks, not chaos. The exact same twenty fields, shown five at a time across four steps, feels dramatically lighter — because now it fits in the space the mind actually has.
Problem 2: "There are so many buttons I don't know where to click"
You land on a screen and everything is competing for your attention — five buttons, all the same size, all shouting equally. You freeze for a second, unsure which one you're supposed to press.
The science: the more choices you present, the longer and harder the decision becomes (Hick's Law). Every option adds a little processing cost, and when options pile up with no hierarchy, you turn a simple action into a puzzle. Simplicity isn't just an aesthetic preference — it's literally faster to use.
The fix: reduce and prioritize. Most screens have one action that matters most — make it the obvious primary, and visually demote the rest. Fewer choices, one clear path. If you can't remove options, at least rank them, so the eye lands on the important one first instead of weighing all five.
Problem 3: "I keep missing that tiny button"
Especially on mobile: the target is small, or crammed next to three other things, and you tap the wrong one, or miss entirely and have to try again. Small annoyance, but it adds up into something that feels clumsy and cheap.
The science: how long it takes to hit a target depends on its size and its distance from you (Fitts's Law). Small, far-apart targets are genuinely slower and harder to hit — that's not the user being careless, it's a measurable property of how movement and aiming work.
The fix: make important, frequent actions bigger and easier to reach. On mobile, respect the thumb zone — put primary actions where thumbs naturally land, not in a tiny corner. Give tappable things enough size and spacing that hitting them requires no precision. Effortless means the user never has to aim.
Problem 4: "I clicked it — did anything happen?"
You press a button and… nothing visibly changes. So you wait. Then you press it again, unsure. Maybe you just submitted the form twice. That flicker of doubt — did that work? — is a small but real discomfort.
The science: the brain expects feedback for its actions. In the physical world, everything you touch responds — press a real button and it clicks and moves. When a digital action produces no visible reaction, the mind is left in uncertainty, and uncertainty is a genuine cognitive cost. Silence reads as "broken."
The fix: every meaningful action needs a visible response. A button that shows a loading spinner. A saved-confirmation. A subtle state change. It doesn't have to be loud — it just has to answer the question the user is silently asking: did that work? Feedback is how you replace doubt with confidence.
Problem 5: "This looks clickable but isn't (and that isn't but is)"
You try to tap something that looked like a button — nothing. Meanwhile the actual button was that plain bit of text you ignored. The interface set expectations and then broke them, and now you feel a little stupid, which is really the design's fault, not yours.
The science: people carry mental models — expectations about how things behave — and they read affordances, the visual cues that suggest what a thing does (this is core Don Norman territory). We expect a button to look pressable and a link to look clickable. When something looks interactive but isn't (or vice versa), you're fighting expectations the user didn't choose to have.
The fix: make interactive things look interactive, and non-interactive things not. Buttons should look like buttons. Links should look like links. Don't make people guess or hover-hunt to discover what's clickable. The goal is that the interface looks like what it does — so people navigate on instinct instead of trial and error.
Problem 6: "Everything's shouting and I can't find what matters"
The screen is busy. Bold text everywhere, competing colors, ten things all demanding attention at once. You don't know where to look first, so your eyes just bounce around, and finding the one thing you need takes effort it shouldn't.
The science: attention is limited and selective — we can't process everything at once, so the brain automatically latches onto whatever stands out and filters the rest. And a lot of that happens before conscious thought: we register size, color, and position almost instantly. That means visual hierarchy isn't decoration — it's how you direct a scarce resource.
The fix: create a clear hierarchy. Make the most important thing the most visually prominent, and everything else quieter. Use size, weight, color, and space to say "look here first, then here." When everything is emphasized, nothing is — so choose what matters and let it stand out while the rest recedes.
Problem 7: "I have to remember where that setting was"
You know the app can do the thing, but you can't remember how — which menu, which command, where that toggle lived. So you hunt. Interfaces that make you recall things from memory feel like work in a way that ones that just show you never do.
The science: recognition is far easier for the brain than recall. Recognizing something you see ("oh, that's the one") takes almost no effort; retrieving it cold from memory ("what was that command again?") is genuinely harder. Good interfaces lean on recognition and spare people from having to remember.
The fix: show, don't make them recall. Visible menus and options instead of memorized commands. Clear labels instead of cryptic icons people have to learn. Keep frequently needed things visible rather than buried. Every time you replace "remember this" with "here it is," the interface gets lighter to use.
The real point: you can now name the problem
Read back over those seven. Notice what just happened — every "annoying" thing had a nameable cause and a specific fix. That's the entire difference between someone who decorates interfaces and someone who designs them.
The person who's learned this doesn't look at a struggling screen and say "hmm, feels off, let me make it prettier." They say: "that's cognitive overload — chunk it," or "too many equal choices — pick a primary," or "no feedback on that action — add a loading state." They can diagnose instead of guess. They can adapt when a pattern doesn't fit, because they understand the principle underneath it. And they can defend a decision in a review with "because that's how attention works," which beats "I think it looks better" every single time.
Why this matters more than ever
Here's the timely part. AI can now generate a clean-looking interface in seconds — the surface is basically free. Which means the surface is no longer where the value is. The value is in knowing why an interface works for a human, because that's the part the machine doesn't have. AI copies patterns; it doesn't understand the mind those patterns are for. Anyone — designer or developer — who understands the science can direct the tools and fix what they get wrong. Anyone who only knows patterns is now competing with a machine that copies patterns faster.
The science of how humans think is exactly the part that stays yours.
The takeaway
You don't need a psychology degree. You need to know that there's a science under good design — that "effortless" isn't taste or luck, it's working memory, attention, feedback, recognition, and a handful of interaction principles you can actually learn and apply.
Figma builds the surface. Understanding the human on the other side of the screen is what makes the surface actually work. And now that you can name these problems, you'll start seeing them everywhere — in your own designs, and in every app that quietly annoys you. That noticing is where better design begins.
What's the most quietly-annoying interface you use regularly — and can you now name why it's bad? Mine's a banking app that hides the one thing I need behind three taps and gives zero feedback when I press anything. Recognition-over-recall and missing feedback, back to back. Tell me yours — bonus points if you can name the principle it breaks.
Top comments (10)
Thanks for sharing @james_anderson_h . One of the thing many developers including me, UI/UX usually comes on the bottom of priority list. But one should also take into account that, even if your application has all the best features in the world, but if user is finding it difficult to use or navigate it then your app is of no use.
So true — the best feature set in the world is worthless if people can't figure out how to use it; UX is what actually lets all that hard work reach the user. 🙌
Helpful article
Thank you.😊
❤️
😊
Some comments may only be visible to logged-in visitors. Sign in to view all comments.