What is Tesler’s law?
Tesler’s law, also known as the law of conservation of complexity, suggests that every system has a certain level of complexity that cannot be eliminated—only managed. This principle doesn’t mean removing complexity altogether but rather deciding who should deal with it: the user or the system.
Larry Tesler, a pioneer in human-computer interaction, believed that good design shifts complexity away from the user. This mindset drove much of his work across industry giants like Xerox PARC, Apple, Amazon, and Yahoo.
Larry Tesler’s legacy in computing
At Xerox PARC in the 1970s, Larry Tesler helped develop innovations like cut, copy, and paste functionality and modeless software design—fundamentals that still shape modern computing.
At Apple, he played a key role in projects like the Apple Lisa and Newton, eventually becoming Chief Scientist. His influence extended to Amazon and Yahoo, where he continued championing user-centric design. Tesler passed away in 2020, but his contributions remain vital to understanding interface and product usability.
Good design takes time
There’s a common misconception that simple design is easy to create. In reality, designing something simple takes more time than building something complex.
If our goal was to ship complexity, anyone could be a designer.
However, great design is about intentionally managing and reducing cognitive load. That process takes thought, iteration, and refinement.
Managing complexity, not eliminating it
According to Tesler’s law, complexity in a system doesn’t vanish. It gets transferred into the product’s design or the user’s experience.
- When we optimize for user experience, the product handles the complexity.
- When we prioritize speed or ease of development, users manage the complexity, often resulting in frustration.
This is why truly simple-feeling products often involve layers of hidden sophistication—automation, streamlined flows, and smart defaults that reduce user friction without removing core functionality.
Simplicity vs. minimalism
Simplicity and minimalism are often confused, but they serve different purposes:
- Simplicity is about clarity and ease of use.
- Minimalism focuses on aesthetics and reducing elements to their bare essentials.
A minimalist product can still be hard to use, while a product designed with simplicity can have robust functionality and still be easy to navigate.
Tesler’s law reminds us that the goal isn’t to remove features—it’s to manage their complexity so that users aren’t overwhelmed. A well-designed product can be powerful, feature-rich, and still intuitive.
Simpler isn’t always better
Some products, such as CAD software, video editing suites, or data analytics platforms, are naturally complex. Their users need access to deep, nuanced functionality. Trying to oversimplify these tools can hinder their usability for those who rely on them.
The real challenge isn’t to strip away features—it’s to make the complexity manageable and discoverable. A truly good interface meets users where they are, balancing depth and accessibility.
Using progressive disclosure
One effective strategy for managing complexity is progressive disclosure. This design approach reveals only the most necessary options upfront and gradually introduces advanced features as users become more comfortable.
Examples of progressive disclosure include:
- Hiding advanced settings until needed
- Showing onboarding tips or tooltips contextually
- Using collapsible sections for secondary content
This method respects both beginners and experts. It keeps the interface clean and approachable while allowing deeper exploration over time.
Complexity evolves over time
A key idea often overlooked in Tesler’s law is that complexity is not fixed—it changes as users grow and technology evolves.
As users become more proficient, they can handle more sophisticated features. In turn, designers can progressively introduce new functionality that matches that growth.
For example, a photo-editing app might start by showing new users basic tools. As their skills develop, the interface can expand to offer advanced controls, filters, and adjustments. This evolving complexity feels natural because it grows with the user.
Designers should always consider how user experience evolves, adjusting how complexity is presented to match user familiarity and needs.
Common myths about simplicity in design and user experience
1. Simpler is always better
This idea isn’t always true. In many cases, oversimplification harms usability. Removing too many options or dumbing down interfaces can make products less functional, especially for professional or technical users. Tesler’s law doesn’t advocate for simplicity at all costs—it supports clarity, not limitation.
2. Minimalist design means good UX
Minimalism is a visual style, not a guarantee of usability. A sparse, clean interface might look beautiful but offer no guidance or functionality.
On the other hand, designing for simplicity requires intentional decisions about how features are surfaced, grouped, or hidden, aligning with Tesler’s principle of managing—not removing—complexity.
FAQs about Tesler’s law in design
What is Tesler’s law in simple terms?
- Tesler’s law states that every system contains some inherent complexity that cannot be removed. Effective user experience design ensures the system handles this complexity, not passing it on to the user. The goal is to make interactions feel intuitive without sacrificing functionality.
Why does simplifying a design take longer?
- Creating a simple, intuitive experience takes more effort than building something complex. It requires deeper thinking and iteration to hide complexity. Simplicity is achieved not by doing less but by doing more behind the scenes.
Is Tesler’s law only relevant to UX/UI design?
- Tesler’s law is most visible in UX/UI, but its principles apply far beyond screen-based design. Any system involving user interaction—such as support services, physical products, or documentation—benefits from managing complexity to reduce user burden. It’s a universal principle of user-centered thinking.
How does progressive disclosure help manage complexity?
- Progressive disclosure is a technique where users are shown only essential information initially, with more advanced features revealed as needed. This approach reduces cognitive load and helps users learn at their own pace. It keeps interfaces approachable while supporting depth for more experienced users.
Can you completely remove complexity from a product?
- No, and that’s the core of Tesler’s law. Complexity doesn’t just disappear—it has to go somewhere. You can hide, reduce, or organize it better but can’t eliminate it. If the system doesn’t absorb it, users are left to figure it out, often resulting in frustration or failure.
What are good examples of Tesler’s law in action?
- Apple’s modeless interfaces simplify powerful interactions without requiring users to toggle between modes. Google tools like Docs and Analytics use progressive disclosure to reveal advanced capabilities gradually. Notion allows flexibility through layered complexity, adapting to beginners and power users.
How can product teams decide which complexity to shift to the system?
- Teams can observe user behavior through usability testing and journey mapping to pinpoint high-friction tasks. Frequent, repetitive, or error-prone Tasks are strong candidates for system-side complexity management. The goal is to reduce decision fatigue and streamline common workflows.
What’s the difference between Tesler’s law and Hick’s law?
- Tesler’s law deals with the location of complexity—whether the system or the user manages it. Hick’s law, on the other hand, addresses decision time, which increases with the number of choices presented. Together, they help designers balance information clarity and efficiency.
How does Tesler’s law apply to AI or machine learning interfaces?
- AI systems often mask complexity by automating recommendations, predictions, or decision-making. Tesler’s law is at play when simple interfaces make these complex processes usable. The challenge lies in offering transparency and control without exposing users to overwhelming detail.
Can Tesler’s law be applied to content design or information architecture?
- Yes, content designers use Tesler’s law by structuring information logically, reducing jargon, and presenting content progressively. Whether in onboarding, FAQs, or long-form guides, managing complexity helps readers easily navigate content. It’s just as relevant for words as it is for UI.
How do you apply Tesler’s law in MVP (minimum viable product) development?
- It is important to identify and absorb only the most essential complexity in early-stage products. Prioritize core features that offer immediate value and reduce friction. Complexity can be layered in as the product grows through thoughtful iteration and user feedback.
How can we test whether we’re managing complexity effectively?
- User testing is the most effective way to validate how well complexity is handled. If users hesitate, struggle to complete tasks, or abandon workflows, the design may push too much complexity onto them. A clean interface means little if usability suffers underneath.
Conclusion: design isn’t about reducing—it’s about managing complexity
Designers often feel pressure to make things “simple.” However, as Tesler’s law teaches, simplicity isn’t about removal but thoughtful organization. Some complexity is necessary. The real skill lies in making that complexity feel natural and manageable. Designers must decide whether users should bear the brunt of complexity or whether the product should handle it for them.
By applying strategies like progressive disclosure, embracing evolving user needs, and understanding the line between minimalism and usability, we can design powerful and user-friendly experiences.
Tesler’s law in design remains a guiding principle for anyone seeking to create products that don’t just work but feel effortless to use.
