> 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/ux-methods/discovery/first-principles-thinking.md).

# First Principles Thinking

First principles thinking involves breaking down a complex problem into its most basic components. By questioning underlying assumptions and focusing on fundamental truths, this approach challenges conventional wisdom and encourages critical thinking. This can lead to innovative solutions.

In UX design, first principles thinking is particularly valuable during the Discovery phase. By applying this method, designers can challenge assumptions, gain deeper user insights, uncover true needs, and develop innovative solutions that go beyond surface-level requirements.

Learn more about First Principles Thinking in the **Cognitive Tools** section below.

{% content-ref url="/pages/1nlIdlAfXOj3XA65I0f3" %}
[First Principles Thinking](https://www.designreference.xyz/cognitive-tools/universal/problem-solving/first-principles-thinking.md)
{% endcontent-ref %}


---

# 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/ux-methods/discovery/first-principles-thinking.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.
