There's a quiet assumption in our industry that the best designers are the ones with the most polished Dribbble shots or the deepest Figma mastery. I believed that once too. Then I watched a designer with mediocre visual skills produce work that consistently outperformed more polished alternatives — and I had to understand why.
The answer was mental models. She wasn't designing screens. She was designing the space between what users expected and what the interface delivered. And that gap — that invisible, psychological gap — is where elite UX actually lives.
A mental model is the internal representation a person holds about how something works. Every user arrives at your interface with one — and if your design conflicts with it, no amount of visual polish will save you.
The moment I understood mental models
Years ago, I was testing a checkout flow. Users kept abandoning at the payment step. The UI was clean. The copy was clear. The buttons were well-placed. By every heuristic, the design was "good."
But when we watched session recordings, we noticed something: people were hesitating — not because they didn't understand the form, but because their mental model of an online payment didn't match what we'd built. They expected to see an order summary next to the payment fields. We'd placed it on the previous screen, thinking we were reducing clutter. We were actually breaking their model.
Moving the summary alongside the form lifted completions by 18%. The design didn't become more beautiful. It became more aligned.
The three types of mental models every designer should know
1. The System Model (what the product actually does)
This is the truth. How the system genuinely works — its architecture, its logic, its constraints. Designers know this intimately. Users don't — and they shouldn't have to.
2. The Interaction Model (what the interface communicates)
This is what your design tells the user about how things work. Labels, visual hierarchy, affordances, feedback — all of it contributes to the story your interface tells. When this model is clear, users don't have to think.
3. The User's Mental Model (what the person believes)
This is the one that matters most. It's shaped by past experiences, by other products they've used, by cultural conventions, by their own unique context. You can't control it — but you can research it, respect it, and design around it.
The goal isn't to make all three identical. It's to close the gap between the interaction model and the user's mental model. When those two align, magic happens. The product feels "intuitive." It "just works." And users never think about the system model at all — which is exactly how it should be.
How to design with mental models in mind
Start with research, not wireframes. Before you open Figma, spend time understanding what your users already believe. Interview them. Watch them use competing products. Map their expectations before you try to shape them.
Leverage existing conventions. Users bring mental models from every other product they've used. If every e-commerce site puts the cart in the top right, putting yours in the bottom left isn't innovative — it's hostile. Borrow patterns that users already understand, then innovate only where it genuinely adds value.
Test for alignment, not just usability. Traditional usability testing asks: "Can users complete the task?" Mental model testing asks: "Did users expect this to work the way it did?" Both matter, but the second question catches the deeper issues.
Elite UX isn't about being original. It's about being familiar in all the right places — and original only where it creates genuine advantage.
The competitive edge
Here's what I've learned: most designers can make things look good. Few can make things feel inevitable. The difference is almost never a matter of tools or talent — it's a matter of depth. Of spending as much time understanding the human mind as you spend pushing pixels.
Mental models are the foundation of that depth. They're why some products feel like they were built for you, and others feel like they were built despite you. If you take one thing from this article, let it be this: your user already has a map of how your product should work. Your job isn't to give them a new map. It's to make sure your design matches the one they already hold.