> 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/interaction/hicks-law.md).

# Hick's Law

The time it takes to make a decision increases with the number and complexity of choices.

Hick's Law is a psychological principle that states the more choices or options you have, the longer it takes to make a decision. 

It suggests that as the number of choices increases, the time it takes to decide also increases. So, if you're presented with many alternatives, it might take you longer to make a choice because your brain needs more time to process and evaluate each option. 

This concept is often used to emphasise the importance of simplicity and minimising choices in design and decision-making to improve efficiency.

#### Further Viewing

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

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

#### Further Reading

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

{% embed url="<https://www.interaction-design.org/literature/article/hick-s-law-making-the-choice-easier-for-users>" %}

{% embed url="<https://medium.com/@incharaprasad27/hicks-law-the-psychology-of-decision-making-11bb52822a18>" %}

{% embed url="<https://www.uxtoast.com/ux-laws/hicks-law>" %}

{% embed url="<https://medium.com/perpetual/ux-design-principle-001-hicks-law-3d4d03cb22fa>" %}


---

# 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/interaction/hicks-law.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.