Why the Best Products Feel Invisible
The highest compliment a product can receive is one it will never hear: nothing.
No feedback. No complaints. No confused emails. No “where do I find…?” messages. Just silence — the kind that means someone opened an app, did what they needed, and moved on with their life without ever thinking about the interface.
The best products don’t demand attention. They dissolve into the task.
We don’t celebrate this enough. Product teams optimize for engagement, time-on-screen, click-through rates — metrics that reward stickiness. But stickiness isn’t always value. Sometimes it’s friction wearing a trench coat.
The Door Handle Test
Design has a term for this: affordance. Coined by psychologist James Gibson and popularized in product design by Don Norman in The Design of Everyday Things, affordance describes how an object’s design communicates how it should be used. A well-designed door handle tells you whether to push or pull — without a sign. You don’t admire it. You don’t Instagram it. You just use it. And that’s the point.
Now think about the last time you stood in front of a glass door, pushed when you should have pulled, and briefly questioned your competence as a functioning adult. Norman called these “Norman doors” — designs that make users feel stupid. That moment of confusion? That’s what bad product design feels like — except digitally, thousands of times a day, to millions of people who quietly blame themselves instead of the interface.
I think about this every time I watch someone struggle with a mobile app during usability research. The participant apologizes. “Sorry, I’m not very tech-savvy.” They never blame the product. They blame themselves. And we built the thing that made them feel that way.
The best design doesn’t make users feel smart. It makes intelligence irrelevant.
Engagement Is Not the Same as Value
There’s a dangerous assumption in product work: if users are spending more time, they must be getting more value. But time spent can mean many things. Exploration. Confusion. Rage-scrolling. The inability to find a “cancel subscription” button that’s been buried behind three menus and a modal confirmation dialog.
High engagement and high frustration can produce identical metrics. The dashboard won’t tell you which one you’re looking at. Only the user knows, and they’re too tired to fill out your survey.
This isn’t a hypothetical. Dark patterns — interface tricks that manipulate users into actions they didn’t intend — have been documented extensively by researchers at Princeton and the Norwegian Consumer Council. Their 2019 study of 11 popular platforms found deliberate friction in flows designed to prevent account deletion, obscure opt-outs, and manufacture false urgency. All of it drove “engagement.” None of it was value.
The products I admire most are the ones I barely notice:
- Google Maps rerouting quietly in the background, without announcing it as a personal achievement
- Stripe’s payment flow, which ends before you realize it started
- Notion’s autosave, which has never once asked me if I want to keep my changes
These aren’t “simple” products. They’re products that absorbed complexity so the user doesn’t have to.
Complexity Is the Product’s Problem, Not the User’s
Every feature request is an invitation to push complexity toward the user. More options. More toggles. More “advanced settings” that nobody advances to.
The discipline isn’t in building less. It’s in deciding where the complexity lives. Either the product carries it, or the user does. And every time we choose the user, we’re outsourcing our design work to someone who didn’t sign up for it.
Get Aditi’s stories in your inbox
Join Medium for free to get updates from this writer.
UX researcher Jared Spool has a useful framing for this. He describes the “expertise reversal effect” — the idea that features designed for novices often frustrate experts, and features designed for experts overwhelm novices. The products that get this right don’t split the difference. They change shape depending on who’s using them. They absorb the complexity of the decision so neither group has to make it.
Simplicity isn’t the absence of features. It’s the presence of decisions.
Gmail’s Smart Reply is a good example. The feature doesn’t give you more options — it reduces the number of decisions in a workflow most of us do dozens of times a day. The complexity of natural language processing, tone detection, and context inference is entirely invisible. What the user sees is three short phrases and a tap.
The Invisibility Paradox
Here’s the uncomfortable truth for anyone who builds products: your best work will go unnoticed. Not because it’s unremarkable, but because it’s so well integrated into someone’s life that they never pause to appreciate it.
That’s not a failure of recognition. It’s the highest form of craft.
Think about the architect who designs a staircase you climb without thinking. The editor whose deletions make a book feel inevitable. The product manager whose feature ships so naturally that users assume it was always there.
John Maeda touches on this in The Laws of Simplicity — his third law, “TIME,” argues that saving users time always feels like simplicity. But the inverse is also true: when a product takes too long to load, too many steps to complete a task, or too much explanation to understand — users experience it as complexity, regardless of how technically elegant the underlying system is. Invisibility is felt in time. The faster something disappears into your workflow, the better its design.
Invisibility isn’t the enemy of impact. It’s the proof of it.
When “Delight” Becomes a Distraction
There’s a tendency in product design to reach for delight as a proxy for good work. Confetti on a completed task. Micro-animations. Personality in error messages. These aren’t inherently bad — but they’re often used to paper over a product that hasn’t yet done the harder work of getting out of the user’s way.
Kathy Sierra, author of Badass: Making Users Awesome, argues that the goal of product design isn’t to make the product lovable — it’s to make the user feel capable. “The best user experience is the one that makes the user feel like a better version of themselves,” she writes. Not a user who loves the app. A person who loves what they can do because of it.
That reframing matters. Delight is self-referential. It draws attention back to the product. Invisibility is the opposite — it points entirely at the user’s goal.
So What Do We Optimize For?
Not delight — that’s often just animation.
Not engagement — that’s a proxy, not a purpose.
Optimize for absence. The absence of confusion. The absence of unnecessary decisions. The absence of the user needing to think about your product at all.
In practice, this means asking different questions during design reviews:
- What does the user have to figure out here that they shouldn’t have to?
- What decision are we asking them to make that we could make for them?
- What would this screen look like if we assumed the user was in a hurry, distracted, and just wanted to finish?
These aren’t questions about simplicity for its own sake. They’re questions about respect — for the user’s time, attention, and cognitive load.
The goal isn’t to be loved. It’s to be so useful that love is beside the point.
Because the moment someone says “I don’t even notice it anymore,” you’ve done something most products never achieve.
You’ve disappeared. And that’s the whole point.
If you found this useful, you might also enjoy:
- The Laws of Simplicity — John Maeda (MIT Press)
- The Design of Everyday Things — Don Norman (Basic Books)
- Badass: Making Users Awesome — Kathy Sierra (O’Reilly)
- Deceived by Design — Norwegian Consumer Council (2019)
