Tesler's Law
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
Every process has an inherent, irreducible core of complexity. This complexity cannot be eliminated, only transferred. It is either handled by engineers in the code (making the system more complex) or by users during operation (making it more cumbersome for users). -
SCAFFOLDING EFFECT
Reduce cognitive load
The principle of conservation of blame-shifting. - Why are today's apps increasingly foolproof? Because engineers absorb all the complexity. Why are some government procedures so tedious? Because departments are too lazy to handle complexity, shifting the burden to the citizens. There is no real 'simplicity', only a trade-off of 'who bears the burden'.
Anchor fast decisions
The law of conservation of complexity: every system has inherent complexity that cannot be eliminated, only transferred between the designer (system) and the user. Good design places complexity on the side that can bear it more easily.
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Law_of_conservation_of_complexityverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS