Tesler’s Law: The Law of Conservation of Complexity

 Why Simplicity for Users Often Means Hidden Complexity for Designers

In the world of design, especially UI/UX, there's a constant battle between functionality and simplicity. That’s where Tesler’s Law—also known as the Law of Conservation of Complexity—comes in.

What is Tesler’s Law?

Coined by Larry Tesler, a computer scientist who worked on Apple Lisa and Macintosh, Tesler’s Law states:

“Every application must have an inherent amount of irreducible complexity. The only question is who will have to deal with it—the user or the developer.”

In simpler words, complexity can't be eliminated, it can only be shifted. The best user experiences happen when the design team takes on that complexity—so the user doesn't have to.


Real-Life Example: Online Food Delivery App

Let’s say you're ordering food from an app like Foodpanda or Uber Eats. The process for you might look like this:




Yes ! Hot fresh pizza delivered


Simple, right? But behind the scenes, there’s a complex system doing all the hard work:

In a food delivery app, Tesler’s Law plays a crucial role in crafting a smooth, stress-free experience. Food ordering can be complex: there are menus, customizations, delivery zones, time estimations, payment options, and more. If the app throws all that complexity at the user, it leads to frustration and cart abandonment.

Here’s why applying Tesler’s Law is essential in food delivery app UI/UX:

1. Simplifies the User Journey

Designers must simplify multi-step actions—like customizing meals or scheduling delivery—into a few intuitive taps. The complexity of restaurant availability, delivery time calculations, or ingredient variations should be handled behind the scenes


CUSTOMER JOURNEY MAP

2. Reduces Cognitive Load

Users are often hungry, in a hurry, or distracted. A clean, minimal interface with smart filters, pre-filled fields, and personalized suggestions ensures they don’t have to think hard or make too many decisions.





3. Handles Complex Logic Invisibly

Let’s say a user picks a restaurant that’s temporarily closed, or chooses a delivery location just outside the range. Instead of showing error messages, the app can auto-suggest nearby alternatives or prompt for pickup—without breaking the flow.

Matching your location with available delivery drivers

Communicating with the restaurant in real time

Calculating estimated delivery time and price

Handling multiple payment methods

Sending push notifications about order updates

All of this happens in seconds—and you don’t have to worry about a thing.

Why? Because the design and engineering teams made it that way. They absorbed the complexity, so you could have a seamless and satisfying experience.

Restaurant timing is clear to the user. When the restaurant closes, the user is unable to take orders for a better experience.

4. Enhances Trust and Retention

By managing the heavy lifting—live order tracking, secure payments, smart notifications—users feel that the app "just works." That kind of reliability builds trust and keeps users coming back.


Users get reviews and ratings to help develop trust. The user feeling more dependable.

In short, Tesler’s Law teaches that a delightful food delivery experience doesn’t happen by accident—it’s the result of intentionally absorbing the complexity within the design and development process, so the user can focus on what really matters: enjoying their meal.


 





Post a Comment

0 Comments