> 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/psychology/yerkes-dodson-law.md).

# Yerkes-Dodson Law

The Yerkes-Dodson Law posits that performance increases with physiological or mental arousal, but only up to a point. When levels of arousal become too high, performance decreases. This relationship is graphically represented as a bell-shaped curve, illustrating that optimal performance is reached at an intermediate level of pressure.

#### The Relationship Between Task Complexity and Arousal

The "optimal" point of arousal is not fixed; it shifts depending on the difficulty and familiarity of the task at hand:

* **Simple or Well-Learned Tasks**\
  These require higher levels of arousal to maintain focus and prevent boredom. For instance, a repetitive data entry task might require a fast-paced environment or a tight deadline to ensure the individual remains engaged and efficient.
* **Complex or Novel Tasks**\
  These are best performed under lower levels of arousal. High pressure, such as a looming high-stakes deadline or a cluttered, noisy interface, can lead to cognitive overload, increased error rates, and "choking" under pressure.

#### Application in UX and Design

In the context of user experience, this law is a vital tool for managing cognitive load. If a user interface is too minimalist or lacks clear calls to action, the user may experience low arousal (boredom or lack of motivation) and fail to complete the journey. Conversely, if a system is overly complex, flashes too many alerts, or uses aggressive countdown timers, the resulting high arousal can cause the user to become frustrated and abandon the task.

The goal for designers is to maintain the user in the "Goldilocks zone" of arousal: enough stimulation to guide them through the process, but not so much that the interface becomes an obstacle to their performance.

#### Further Viewing

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/psychology/yerkes-dodson-law.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.