Why the best interfaces feel obvious.
Good product design hides complexity and makes the next action feel natural, even when the system underneath is complex.
An interface feels obvious when dozens of small design decisions have already been made so the user doesn’t have to make them. When it works well, users rarely stop to admire it — they simply know what to do next, and they don’t experience that knowledge as something the product gave them. It just feels like common sense, which is exactly the effect good design is supposed to produce.
Obviousness is a design decision, not an accident
That feeling of obviousness is hard to create precisely because it requires so many decisions to disappear from view. Good design reduces competing signals, establishes a clear hierarchy, and gives each action an unambiguous purpose. None of that happens by default — it happens because someone decided, deliberately, what the user’s eye should land on first, second, and third, and removed everything that competed with that order.
Interfaces that feel confusing are rarely confusing because of one bad decision. They’re usually confusing because of dozens of small unmade decisions, each one small enough to seem unimportant on its own, that add up to a page with no clear order of attention.
Complexity doesn’t disappear — it moves
Good design doesn’t remove complexity from the underlying system. It removes unnecessary complexity from the user’s path through it. That distinction matters more as the system gets more capable, because more capable systems have more internal complexity that has to go somewhere. Either it gets pushed onto the user, in the form of settings, choices, and edge cases they have to think about — or it gets absorbed by careful design, so the system carries the weight instead of the person using it.
This is one of the more honest ways to think about what design work actually is: not decoration on top of a finished system, but a decision about who has to deal with the complexity that inevitably exists somewhere. Good design volunteers to deal with it. Bad design quietly hands it to the user and calls that flexibility.
Why this matters more for AI-powered products
This is especially important for products built on complex technology. The more sophisticated the engine becomes, the simpler the experience should ideally feel — not the other way around. A system capable of far more than a simple tool creates a temptation to expose all of that capability directly to the user, as options, toggles, and configuration. Resisting that temptation, and instead choosing what the system should just handle on its own, is where the real design work happens.
The products people describe as “it just works” are almost never simple underneath. They’re usually deeply considered on the inside and deliberately restrained on the outside.
Common questions
How do you know if an interface is genuinely obvious versus just familiar? Test it with someone who has no prior context. Familiarity can disguise real confusion for people who’ve already learned a product’s quirks. A genuinely obvious interface holds up for a first-time user with zero onboarding.
Does making something feel obvious mean removing all advanced options? Not necessarily — it means not showing advanced options by default to everyone. Progressive disclosure, where complexity is available but not forced on the majority of users, is often the right balance.
Is “obvious” the same goal for every kind of product? The target destination differs — a professional tool can tolerate a steeper learning curve than a consumer app — but the underlying principle holds everywhere: the next action should always be clearer than the alternative actions around it.
Takeaway: a powerful product that needs a manual is usually a sign the product still has design work left to do.