Law of conservation of complexity
From Wikipedia the free encyclopedia
The law of conservation of complexity, also known as Tesler's Law,[1][2][3] or Waterbed Theory,[4] is an adage in human–computer interaction stating that every application has an inherent amount of complexity that cannot be removed or hidden. Instead, it must be dealt with, either in product development or in user interaction.
This poses the question of who should be exposed to the complexity. For example, should a software developer add complexity to the software code to make the interaction simpler for the user or should the user deal with a complex interface so that the software code can be simple?[5]
Background[edit]
While working for Xerox PARC in the mid-1980s, Larry Tesler realized that the way users interact with applications was just as important as the application itself.[5] The book Designing for Interaction by Dan Saffer[6] includes an interview with Larry Tesler that describes the law of conservation of complexity.[5] The interview is popular among user experience and interaction designers.
Larry Tesler argues that, in most cases, an engineer should spend an extra week reducing the complexity of an application versus making millions of users spend an extra minute using the program because of the extra complexity.[5] However, Bruce Tognazzini proposes that people resist reductions to the amount of complexity in their lives.[7] Thus, when an application is simplified, users begin attempting more complex tasks.
Applications[edit]
Possible applications of Tesler's Law:
- Programming
- Vehicles
- Home appliances
- Workplace equipment
References[edit]
- ^ "Tesler's Law". uxtoast. Retrieved 2021-01-03.
- ^ Yablonski, Jon (21 April 2020). "Chapter 9: Tesler's Law". Laws of UX: Using Psychology to Design Better Products & Services. p. 87. ISBN 9781492055280.
- ^ Saffer, Dan (2010). "Chapter 7: Refinement". Designing for Interaction: Creating Innovative Applications and Devices. p. 136. ISBN 978-0321643391.
- ^ "Waterbed Theory". wiki.c2.com. Retrieved 2022-01-12.
- ^ a b c d "Larry Tesler Interview". Designingforinteraction.com. Retrieved 2011-10-18.
- ^ "Designing for Interaction" by Dan Saffer at amazon.com
- ^ The Complexity Paradox, by Bruce Tognazzini