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
- Decide deliberately who handles complexity: the system or the user.
- Use smart defaults, automation and good engineering to carry the load.
- Over-simplifying can push complexity into confusing edge cases.
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
- Identify the irreducible complexity in each task and decide who should handle it.
- Let the system do the work: defaults, autofill, detection and calculations.
- Expose complexity only to users who need control, through advanced settings.
- Invest engineering effort in absorbing complexity in high-traffic flows.
- Test whether simplifications actually reduce user effort or just hide 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