> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead.md).

# AHEAD

The AHEAD dashboard is designed primarily for business application owners and the teams responsible for the adoption, performance, experience, and overall success of critical enterprise applications. It brings together five dimensions into a single, decision-focused view, helping you quickly measure impact and take targeted action.

For hybrid (web and desktop) applications, AHEAD reflects **web app metrics only**. Desktop metrics remain available on the separate **Desktop** tab.

Refer to [Configuring AHEAD](/platform/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/configuring-ahead.md) to configure the AHEAD dashboard for your web applications.

{% hint style="info" %}
The **AHEAD** tab is visible only when you enable AHEAD for the application. If AHEAD is disabled, the tab bar shows the [Overview](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/overview.md) dashboard instead.
{% endhint %}

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FjoIov6tiaxswDyy2xmpb%2F2026.8_AppEx_8_Lp3Ck8.png?alt=media&#x26;token=c8609dc6-e68b-4b3d-9e70-037d42c0a4bc" alt=""><figcaption></figcaption></figure>

## Background

AHEAD measures the application across five dimensions:

* **Adoption** tracks how many employees use the application and how that usage trends over time, showing whether employees are using the application at all. See [Analyzing application adoption](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/adoption.md).
* **Health** shows how reliably and how well the application performs for employees, and whether it works as expected. See [Analyzing application health](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/health.md).
* **Efficiency** tracks how often employees raise IT support tickets for the application, and which employee groups struggle most. This shows where the application creates the most support burden. See [Analyzing application efficiency](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/efficiency.md).
* **Affordability** compares license usage against cost, showing whether you pay for licenses employees do not use. See [Analyzing application affordability](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/affordability.md).
* **Delight** captures employee sentiment, showing whether people are satisfied using the application day to day. See [Analyzing application delight](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/delight.md).

{% hint style="info" %}
AHEAD includes the following AI features:

* **Summary**: Insights, Assist chatbot
* **Adoption**: Insights, Assist chatbot
* **Health**: Insights, Assist chatbot
* **Efficiency**: Insights, Assist chatbot
* **Affordability**: Assist chatbot
* **Delight**: Insights, Assist chatbot

Users with a limited View domain can still access the **AHEAD** tabs. They do not see the Insights widget, but the Assist chatbot remains available.
{% endhint %}

## Using AI-powered insights

Exploring the available AI-powered **Insights** on each AHEAD dashboard opens detailed investigations from the right-side panel. Each tab initially surfaces one insight, if available. On heatmaps with more than 10,000 rows, the system displays an infobar noting that not all results are shown, which can make the ranking inaccurate. Use these insights to reduce the time you spend troubleshooting issues. Refer to the [Nexthink Insights - AI Model Card](https://docs.nexthink.com/legal/global-ai-hub/nexthink-insights-ai-model-card) documentation to learn about the AI-generated architecture used by this feature.

## Key benefits and use cases

### Gain full application visibility through improved dimension tracking

* Track **Adoption**, **Health**, **Efficiency**, **Affordability**, and **Delight** in one view.
* Identify low adoption segments using heatmaps and trends.
* Detect application performance issues.
* Identify where employees struggle most with an application and focus on the biggest opportunities for improvement.
* Optimize license usage.
* Measure and improve employee satisfaction of an application.
* Compare application experience against industry benchmarks.


---

# 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://docs.nexthink.com/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead.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.
