> For the complete documentation index, see [llms.txt](https://handbook.hackalong.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.hackalong.io/patterns/cocreation/navigate-via-tension.md).

# Navigate Via Tension

**Challenges and opportunities** for an organization are revealed by people bringing awareness to the reasons why they experience tension.

**Note:** In this context, a *tension* is a personal experience: a symptom of dissonance between an individual’s perception of a situation, and their expectations (or preferences).

To **discover drivers**, investigate what stimulates tension, and describe what’s happening and what’s needed. Sometimes an inquiry reveals misconceptions and the tension goes away.

![Navigate Via Tension, Describe Organizational Drivers, Respond To Organizational Drivers](https://patterns.sociocracy30.org/img/process/navigate-describe-respond.png)


---

# 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://handbook.hackalong.io/patterns/cocreation/navigate-via-tension.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.