All UX laws

Tesler's Law

Every system has complexity that cannot be removed, only moved to the product or to the user.

Every system has an amount of complexity that cannot be removed, only moved.

By Rohit Sonawane, product designer · Last reviewed 16 November 2026

What is Tesler's Law?

Tesler's Law, also called the law of conservation of complexity, says every system has an amount of complexity that cannot be removed. It can only be moved, either onto the people who build the product or onto the people who use it.

Where does Tesler's Law come from?

Larry Tesler, a computer scientist who worked at Xerox PARC and later at Apple, is credited with the idea, which is also called the law of conservation of complexity. While working at Xerox PARC in the mid-1980s he argued that every application has an inherent amount of complexity that cannot be removed or hidden. The only question is who deals with it: the team that builds the product or the person who uses it. Tesler is also known for helping to bring cut, copy and paste into everyday software.

Decide who does the work on a form

A delivery form makes people type five fields, and they keep getting them wrong. For each field, choose whether the person or the product does the work, and whether what the product fills in can be edited.

How do you apply Tesler's Law?

Decide who carries the complexity. Move it from the person using the product into the product, where the team solves it once.

How to apply Tesler's Law, step by step

  1. List the complexity in the task: every decision, format and piece of data it involves.
  2. Split it into what the person must decide and what the system can work out.
  3. Move the second group into the product: look it up, pre-fill it, set a sensible default or detect it.
  4. Let the person see and change what the system filled in. Absorbing complexity should not take away control.
  5. Test it with someone new. If they still stop and ask what to do, there is complexity left on their side.

What does Tesler's Law look like in a real product?

A checkout that fills in the address

A delivery form asks for street, city, state, postcode and country in five separate boxes. Someone has to work out the full address either way. In version one, the customer does it, typing every part and fixing the typos. In version two, the customer types the first few characters of the street, picks the full address from a list, and the form fills in the rest. Indian checkouts often go one step further: type the six-digit PIN code and the city and state fill in on their own. The address is exactly as complicated as before. The difference is who deals with it: the team that built the lookup, once, instead of every customer, every time.

What are common mistakes with Tesler's Law?

  • Removing a field the system really needs, then guessing the answer wrongly. The complexity has not gone away. It now shows up as a parcel at the wrong address.
  • Hiding complexity the person needs to see, such as the real total price or what a setting changes.
  • Adding help text and tooltips to a confusing flow instead of fixing the flow. That moves the work to the reader.
  • Tucking every option into a hidden menu to look simple. The options still exist, so the person still has to find them.

When does Tesler's Law not apply?

Do not absorb complexity when the person needs to understand or control it. A tax form, a medical consent or a privacy setting should not be filled in silently for the user. Sometimes the right answer is to show the complexity plainly, in small steps. Tesler's Law is also not a reason to ship a complicated product. It says complexity has to go somewhere, not that you should stop removing the part that is not essential.

How do you know you applied Tesler's Law well?

Pick one task and count the fields, choices and rules the person has to handle. For each one, ask if the system could work it out. If it could, it is your job, not theirs.

Tesler's Law: frequently asked questions

Who was Larry Tesler?

A computer scientist who worked at Xerox PARC and Apple. He is credited with this law and is known for helping bring cut, copy and paste into everyday software.

What is an example of Tesler's Law in UX?

An address form that suggests full addresses as you type. The address is just as complicated as before, but the system deals with it instead of the customer, who picks one line from a list.

How do you apply Tesler's Law in design?

Decide what the person must choose and what the system can work out, then move the second group into the product with defaults, lookups, detection and pre-filling. Let people check and change what was filled in.

Does Tesler's Law mean you should never simplify?

No. It means you should be clear about where the complexity goes. Remove what is not essential, and for what is essential, make the product carry the load instead of the user.

Practise it on a real challenge

Delivery Address — five boxes to fill

A delivery form asks customers to type their street, city, state, postcode and country into five separate fields. Many people mistype the postcode or pick the wrong state, and orders arrive late or not at all.

More UX laws

  • Density Matches Context
  • Jakob's Law
  • Time-to-Value
  • Information Architecture
  • Endowed Progress Effect
  • Miller's Law
UX QuestUX Laws and PrinciplesUI UX PracticeUX Design Challenge GeneratorNotion TemplatesBlogPricingAboutContactPrivacy PolicyTerms of ServiceRefund PolicySitemapChangelogPopular UX laws:60-30-10 RuleDesign every stateStatistical PowerFunnel TriageAccessible contrastDensity Matches ContextHick's LawFitts's LawAll UX laws