Waterbed Theory
Updated 2026-09-11
INTRODUCTION
English translation pending.
CORE DEFINITION
The waterbed theory, drawn from software design, compares complexity to the water in a waterbed: pushing it down in one place makes it bulge somewhere else, because the total amount does not change. The core proposition is that complexity can be moved but rarely eliminated, so every simplification transfers the burden to another party or a later time. The key qualification is that the transfer is not necessarily bad: the goal is to place the complexity where it costs least and to do so knowingly, not to pretend it disappeared.
SCAFFOLDING EFFECT
Reduce cognitive load
- Transfer trace: when simplifying something, name exactly who now carries the complexity. - Party list: enumerate users, developers, operators, and future maintainers before deciding anything. - Fairness test: check that the new location is cheaper overall rather than merely convenient for you.
Anchor fast decisions
A system's total complexity is close to conserved because the requirements themselves do not shrink when the interface simplifies. Hiding validation from the interface pushes it into backend logic or onto the user, and abstraction that shortens business code lengthens the learning curve. Optimization along one dimension therefore usually costs another, which is why the question is where the burden lands.
MINIMUM ACTION
In progress 0/1Practice 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