> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/foundations/teslers-law.md). # Tesler's Law Every system has a degree of complexity that cannot be reduced, only managed. {% hint style="info" %} AKA The Law of Conservation of Complexity {% endhint %} Tesler's Law states that for any system there is a certain amount of complexity which cannot be reduced. Tesler's Law suggests that in software design, complexity is constant. This means that no matter what you do, you can't eliminate complexity entirely. Instead, you can choose where you want that complexity to be. If you simplify the user interface, the complexity may shift to the back-end, and vice versa. The key is to make sure that the complexity is managed and not unnecessarily burdensome for the user. #### Further Viewing {% embed url="" %} #### Further Reading {% embed url="" %} {% embed url="" %} {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/foundations/teslers-law.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.