← All 60 lawsProduct strategy

Tesler's Law

Every system has a certain amount of complexity that can't be removed — only moved — so the product should absorb it instead of passing it to users.

Key takeaways

Origin

Attributed to computer scientist Larry Tesler, known for his interaction design work at Xerox PARC and Apple, who argued that an engineer should spend extra time reducing complexity so that millions of users don't each have to deal with it.

How to apply it

How Science of Apps uses this law

4 checks in every investigation rely on Tesler's Law, for example: “Can the core task be completed in the fewest steps the domain allows, with complexity absorbed by the system?”

Get your product investigated
Tesler's Law — Laws of UX · Science of Apps