> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/engineering-metrics/devex-metrics/devex-score.md).

# DevEx Score

Monitor team morale and engagement through surveys or regular check-ins and keep a tab on the well-being score. A motivated and happy team is more likely to be efficient and productive.

<div align="left"><figure><img src="/files/UxHe5LE1slfiM7hBVNzg" alt=""><figcaption></figcaption></figure></div>

**Click here to learn more about** [**DevEx configuration**](/typo-help-docs/platform/settings-and-admin/devex-setup.md)&#x20;

Measuring "developer experience" is crucial for improving engineering team efficiency and fostering a positive work environment. Developer well-being encompasses various factors that impact the mental, emotional, and physical health of individual team members. Understanding and addressing these aspects can lead to higher productivity, reduced burnout, and increased overall team performance.&#x20;


---

# 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://typo.gitbook.io/typo-help-docs/engineering-metrics/devex-metrics/devex-score.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.