Waterbed Theory of Complexity
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
In any system, there is an inherent amount of complexity that cannot be eliminated. You can only push it from one place to another (e.g., from the user interface to the backend development, or from developers to users). Just like a waterbed, pressing down one place causes another to bulge. Scaffolding role: awareness of trade-offs. Don't be fooled by 'simplification.' Ask yourself: 'Where have we hidden the complexity?' If the user feels it's simple, it means engineers are bearing a huge amount of complexity; and vice versa.
SCAFFOLDING EFFECT
Reduce cognitive load
Awareness of trade-offs. Don't be fooled by 'simplification.' Ask yourself: 'Where have we hidden the complexity?' If the user feels it's simple, it means engineers are bearing a huge amount of complexity; and vice versa.
Anchor fast decisions
Any system has a total amount of 'inherent complexity' that cannot be eliminated, only redistributed (e.g., from the user side to the development side, or from the front end to the back end). Like a waterbed: pressing down one place causes another to bulge. The mechanism is conservation of complexity—hiding a problem is not solving it.
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