Tesla's law states that every system inherently has a minimum level of complexity that should not be meaningfully undercut. Consequently, every execution of a task or use of a tool is always associated with a cognitive load. This cannot be completely eliminated.

Origin

Tesler's law was introduced by Larry Tesler, a pioneer in the field of human-computer interaction, in the 1980s.

  • Tesler, L. (1980). Simplification vs. Liberation
  • Tesler, L. (1990). The Computer for the 21st Century

Application in UX and UI design

The development of certain applications, be it a checkout process for an online store or an electronic tax return, is always a highly complex process that requires a deep understanding of the client's requirements, their goals, but also the needs of the user.

Tesler's law reminds us that while the goal is to make a product as user-friendly as possible, this should not be done at the expense of necessary functionality.

Avoid simplifying user interfaces to the point of abstraction. It's not about making everything as simple as possible, but about finding the right balance. This balance takes into account both the abilities and needs of the users and the goal and purpose of the application.

A practical example is the design of software settings. Basic settings are placed prominently and easily accessible, while advanced options are placed in separate, less visible areas. This prevents the main interface from being overloaded and makes it easier for new users to get started, while still giving experienced users full control over the application.

Furthermore, complexity can often be reduced by iteratively running through processes and displaying less relevant information in context.

In many cases, it is sufficient for the user to know "how to use something" rather than "how it works".

Impact on the User Experience

strong

Further information