Skip to content
BENIBIX Learn

Tesler's Law

Also known as Law of Conservation of Complexity, Conservation of Complexity, Teslers Law

Every task has some hard part. Either the product or the user must carry it.

Think of it like

A heavy box has to be carried. Either you lift it, or the truck does.

Example

A form asks for your town and postcode. A better one looks up the town from the postcode, so you type less.

Why it matters

Making a screen look simple is easy. Making the task simple means the team does the hard work.

Definition

Tesler's Law says each task has a hard part that cannot be taken away. It can only be moved, either onto the user or into the system. Good design moves as much of it as it can into the system. It is named after Larry Tesler, who worked on early computer interfaces. The goal is to do the hard work once in the product, not every day by each user.
The same weight of work sits on one side or the other. Good design moves it to the product.

Common mistake

Hiding a hard part instead of handling it. Removing a field the system needs only moves the trouble later.

Key takeaways

  1. 1
    Some is fixed. Every task has a hard core.
  2. 2
    Move it inward. Let the product do the work.
  3. 3
    Not too far. Keep control where people need it.

Learn it properly