> 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/universal/problem-solving/occams-razor.md).

# Occam's Razor

The simplest explanation or solution is often the correct one

{% hint style="info" %}
AKA Law of Parsimony, Principle of Parsimony
{% endhint %}

Occam's Razor is a problem-solving principle that suggests we should always choose the simplest explanation among competing hypotheses, as long as they equally explain the phenomenon in question.&#x20;

In other words, it advocates for parsimony, favouring explanations that require the fewest assumptions. This principle is often paraphrased as "the simplest explanation is usually the best one." The principle is often expressed as "Entities must not be multiplied beyond necessity".

It is a principle in philosophy and science that suggests when faced with multiple possible explanations or hypotheses, the simplest one is often the best. In other words, it encourages us to choose the explanation that requires the fewest assumptions or entities.

#### Further Reading

{% embed url="<https://www.interaction-design.org/literature/article/occam-s-razor-the-simplest-solution-is-always-the-best>" %}

{% embed url="<https://medium.com/the-good-boss/5-mental-models-that-will-take-your-leadership-from-good-to-great-b589cde5ff56>" %}

{% embed url="<https://en.wikipedia.org/wiki/Occam>" %}

{% embed url="<https://lawsofux.com/occams-razor/>" %}

{% embed url="<https://medium.com/kubo/the-simplest-explanation-is-usually-the-right-one-f4b6667a0944>" %}

{% embed url="<https://webdesignerdepot.com/occams-razor-a-great-principle-for-designers/>" %}

{% embed url="<https://fs.blog/occams-razor/>" %}

{% embed url="<https://www.e-counseling.com/articles/parsimony-psychology/>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=Ie53YZiRZy0>" %}


---

# 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/universal/problem-solving/occams-razor.md?ask=<question>&goal=<user_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.
