> For the complete documentation index, see [llms.txt](https://playbook.thevantageproject.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.thevantageproject.com/executing/level-3/the-real-why.md).

# Seeing the Real 'Why'

Understanding the cause of an occurrence is a non-apparent skill. We are trained to see only as far as what garners social acceptance.&#x20;

|              |                 |                                       |
| ------------ | --------------- | ------------------------------------- |
|              |                 | 'Why was the product delivered late?' |
| **Status**   | What occurred   | 'I missed my timelines'               |
| **Behavior** | What enabled it | 'I put in less than 4 hours per day'  |
| **Belief**   | What caused it  | 'Delay of a day or two is acceptable' |

Status is always the most obvious answer. And the most untrue.

Understand the why Keep asking the why until you reach an answer that you can change in yourself.

###

### Role of Values

Our mind makes decisions based on the value system it is subscribed to. Most of it is learned through social institutionalization; not discovered within.

Belief is emotion. Value is intellect. They are interchangeable in their purpose here. Use whatever is your usual method.

When you discover the belief that is hindering progress. Evaluate if it really is relevant, to this moment. That self-question, executed with integrity is enough for transformation.

There are no objective beliefs, only subjective truths.

### Interesting Reads

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

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

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

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


---

# 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://playbook.thevantageproject.com/executing/level-3/the-real-why.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.
