Tesler’s Law Explained: Why Good UX Feels Simple

Who carries the complexity

In real-life situations, complexity falls on someone, either the system or the user. Good UX design tries to move as much of this complexity as possible from the user to the product. This can mean more work in design, engineering, or business logic, but it leads to a more seamless experience for the user.

If this doesn't happen, users are the ones who suffer. They get confused, have to take extra steps, or feel overwhelmed.

Reducing effort, not complexity

Good UX doesn't have to make things simple; it should  make them easier to handle. Complexity is often still there; it's just hidden from view. Things like logic, defaults, and automation do the hard work, so users don't have to think about every technical detail.

This makes the product seem more straightforward from the outside. But internally, it's probably doing more work than you'd think.

Why this matters at scale

Tesler's thinking centers around reducing complexity for the end user. It's generally more beneficial for a team to put in the time to solve a complex issue once, rather than having each user figure it out on their own. Spending a bit more time in development can save numerous small headaches down the line.

As products get bigger and more users come on board, this trade-off becomes even more crucial.

Where the law comes from

The principle is named after Larry Tesler, and this principle grew out of his UX work at PARC, which was later formalized at Apple. His work focused heavily on making software more approachable, and he advocated for standards and structures that reduce the burden on end users. Many of the interaction patterns that feel “normal” today are influenced by his approach.

Why it’s central to UX

In UX, this law is especially relevant because users rarely tolerate unnecessary difficulty. If an interface seems too complicated, people will lose interest.

Products that are easy to use tend to perform better for several reasons:

Forms and input friction

Forms are a great example. When you've got a lot of repetitive info to enter, it gets frustrating fast. UX can help by cutting down the number of fields, using autofill, and picking sensible defaults. The task of collecting data is still inherently complex, but users don't have to deal with that complexity upfront.

If you want to learn more about what makes a good form and which common mistakes to avoid, check out our article on Form Design Best Practices. 

Navigation and cognitive load

Navigation is another area where Tesler’s Law applies. Clear menus, logical grouping, and visible CTAs (calls to action) reduce the amount of mental effort required to move through a product. A well-structured IA (information architecture) doesn’t remove inherent complexity from the system, but makes it easier to understand and navigate.

Automation as a design strategy

Automation is one of the most direct ways to apply Tesler’s Law. Features like auto-suggestions, predictive text, smart filters, and personalized recommendations all move work from the user to the system. The product anticipates needs and handles decisions in advance, which shortens the path to completion.

Checkout flows and repetition

Checkout flows show the same idea. Features like copying billing info into shipping fields, one-click buying, or using Apple Pay make it easier. Users don't have to enter the same information multiple times.

AI and intent-based interfaces

More recent interfaces are pushing this even further. With the help of AI tools, they let users talk in plain language, and the system figures out what the user means and performs the necessary actions. Now, users don't have to follow a set of steps. They just say what they want to happen, and the system handles the details.

The risk of complexity bias

One thing to consider is complexity bias. People often think that complex solutions are better or more advanced. In design, this can lead teams to overcomplicate designs or add extra features that aren't needed.

This mindset can hurt the user experience without anyone noticing.

A warning against overdesign

Tesler’s Law can also be read as a warning. If a product keeps building up features, options, or logic, it may be a sign that the underlying problem hasn’t been clearly defined. Adding more doesn’t always improve the experience. Sometimes the harder task is stepping back and simplifying the problem itself.

Where simplification goes too far

At the same time, simplification has limits. Removing too much complexity can strip away useful functionality or make a product feel overly abstract. Some users need flexibility, control, or visibility. Removing these layers can make tasks harder, not easier.

Progressive disclosure as a balance

To strike a balance, you can use progressive disclosure. The main actions and info are shown right away, while more advanced things are hidden until you need them. Menus, toggles, or extra screens reveal these deeper options. This way, the interface stays easy to use without losing its depth.

This ties in quite closely with how people really use products. Most users don't bother with the manual, they just dive in and figure it out as they go. So, guidance should be part of the experience, not something separate.

Supporting users in context

Tooltips, inline hints, contextual help, and well-chosen defaults all support users as they move through a task. Instead of expecting them to understand the entire system upfront, the product provides assistance at the moment it’s needed.

Complexity as a design responsibility

At a broader level, Tesler’s Law is about responsibility. If teams don’t deal with necessary complexity during design and development, that complexity doesn’t disappear. It gets passed on to users as friction, confusion, or extra effort.