Tesler’s Law: The Law of Conservation of Complexity

“Every application has an inherent amount of irreducible complexity. The only question is: Who will have to deal with it—the user, the application developer, or the platform developer?” – Larry Tesler

1. What is Tesler’s Law?

Tesler’s Law, also known as the Law of Conservation of Complexity, is a foundational UX principle established by Larry Tesler during his time at Xerox PARC in the mid-1980s. The law dictates that every process or application contains a certain baseline of inherent complexity that cannot be eliminated. Before this, engineers often believed that an interface could be simplified infinitely by just stripping away elements. Tesler proved that this complexity doesn’t simply disappear; it just shifts between the system and the user. In modern UX architecture, this isn’t just about making an interface look “simple”; it is a critical driver for deciding how much developmental and design effort should be spent to abstract complexity away from the user to build scalable, highly adoptable digital products.

2. The Core Concept: Shifting the Burden and User Adoption

Managing complexity directly dictates whether a user can easily adopt your platform or abandons it out of sheer cognitive overload. When designers and developers absorb the complexity behind the scenes, users experience a highly intuitive flow.

• They experience immediate frustration and are highly likely to bounce if forced to complete tedious, complex configurations or steep learning curves before getting value from a product.
• They completely lose their context and abandon complex tasks (like detailed onboarding or advanced data entry) if left to figure out intricate system requirements on their own.
• They experience a frictionless, high-converting journey when the system does the heavy computational lifting in the background, making the digital product feel incredibly intuitive and user-centric.

When you architect solutions optimized for reducing the user’s cognitive burden, you stop relying on extensive tutorials or manuals to hold the user’s hand and instead use intelligent system design to drive decisive action and task completion.

3. Key Takeaways for UX Designers

• Absorb the Complexity: Even if a backend process requires significant engineering effort, the UI must remain straightforward. Designers and developers must take on the heavy lifting of complex logic (data formatting, sorting, and processing) to ensure the user’s interaction is as simple as possible.
• Beware of Oversimplification: When you try to simplify an interface too much, you risk removing necessary controls or context. This strategy can backfire by making the product harder to use because the user lacks the required tools to complete their specific tasks, forcing them to find workarounds.
• Prioritize Smart Defaults: For complex forms or settings, design the interface to assume the most common use cases. Show pre-filled intelligent defaults instantly to maintain the user’s momentum, rather than forcing them to start from scratch and input predictable data manually.

4. Real-World Examples

• High-Volume E-commerce (One-Click Checkout): On high-converting platforms like Amazon or Apple Pay integrations, the system abstracts the massive complexity of payment processing, fraud detection, and shipping logistics. The system doesn’t burden the user with entering redundant information, absorbing the complexity entirely on the backend to facilitate a single tap.
• Ride-Sharing Apps (Uber/Lyft): When requesting a ride, the complex logistics of matching drivers, calculating dynamic pricing, estimating traffic, and GPS routing are completely hidden. The user is presented with a simple map and a “Confirm” button, shifting the immense complexity of dispatching away from the rider and onto the system architecture.
• Email Clients (Smart Attachments): When composing an email, modern platforms automatically detect if you typed “attached” or “attachment” but forgot to upload the file, prompting you before sending. This absorbs the complexity of error prevention and recovery, keeping the user’s workflow smooth without requiring them to double-check their own work.

5. How to Handle “Irreducible Complexity” (Managing Friction)

Because Tesler’s Law demands acknowledging an unavoidable baseline of complexity, advanced features—such as enterprise software configuration, intricate data filtering, or specialized professional tools—present a critical friction point. To handle this, you must aggressively manage how information is structured and disclosed. If you cannot completely remove the complexity, you must organize it. Replace overwhelming, single-screen dashboards with categorized, progressive disclosures, step-by-step wizards, or advanced toggle modes. This transforms a passive, anxiety-inducing interface into an active, manageable process that empowers the user without overloading them upfront.

Summary for Designers

“Take on the burden of complexity during the design and development phases to ensure the user’s experience remains simple, intuitive, and focused.” By rigorously applying Tesler’s Law, you stop shifting system limitations onto the user and start resolving the deep, structural friction points that impact usability, scale, and business ROI.