> For the complete documentation index, see [llms.txt](https://docs.oobeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s2-recurring-high-cognitive-load.md).

# S2- Recurring high cognitive load

### **Why is this a symptom?**

This symptom refers to a consistently high level of cognitive effort among team members. This could be due to a lack of resources, or a lack of knowledge-sharing culture and practices. 

If there is a recurring high cognitive load on team members, it can be considered a symptom of the development process. A recurring high cognitive load can lead to burnout, reduced productivity, and decreased job satisfaction.

{% hint style="info" %}
**Level:** Team Level, Individual Level

**Potential Complications:** #burnout, #low\_productivity, #low\_job\_satisfaction, #knowledge\_silo
{% endhint %}

### **Possible Causes**

* Lack of resources
* Poor planning process
* Lack of knowledge-sharing culture
* Operating as a knowledge silo
* Excessive workload

### **Improvement Areas**

* Provide additional resources or support as needed
* Improve knowledge-sharing culture and practices
* Identify and break down the knowledge silos within the team
* Improve planning processes
* Ensure team members have the necessary support and resources to complete their tasks
* Review past instances of high cognitive load to identify patterns and root causes

### **Detection Method**

Oobeya detects this symptom if the impact score of an individual is significantly more than the average team impact for recurring periods.

**Formula:** (ind\_impact > 2(avg\_team\_impact)) x\[specified\_period] recurring period

**Example:** During each of the **last 3 months**, a team member has consistently had an **impact score** **2 times more than** the team average.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s2-recurring-high-cognitive-load.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.