> 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/ja/user-guide/experience-optimization-classic.md).

# Experience Optimization (classic)

エクスペリエンス最適化は、企業におけるデジタル従業員体験 (DEX) を管理するための出発点です。エクスペリエンス最適化は、従業員体験の可視化を得るための完璧なハブであり、問題の優先リストを使用して全体的な体験を積極的に改善するための中心です。

エクスペリエンス最適化のいくつかの機能は Finder (クラシック) と連携しています。

{% hint style="info" %}
Nexthink Finder は Windows 専用のデスクトップアプリケーションであり、その機能は現在 Nexthink の Web インターフェース内で利用可能です。 Nexthink は現在ブラウザから直接使用でき、ほとんどの機能は追加のデスクトップアプリケーションを必要としなくなりました。
{% endhint %}

* [エクスペリエンス最適化 (クラシック) のはじめ方](/platform/ja/user-guide/experience-optimization-classic/getting-started-with-experience-optimization-classic.md)
* [エクスペリエンス最適化 (クラシック) の使用方法](/platform/ja/user-guide/experience-optimization-classic/using-experience-optimization-classic.md)
* [デジタル体験スコア (クラシック)](/platform/ja/user-guide/experience-optimization-classic/digital-experience-score-classic.md)
* [デバイスとユーザーのスコア評価 (クラシック)](/platform/ja/user-guide/experience-optimization-classic/rating-devices-and-users-with-scores-classic.md)


---

# 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/ja/user-guide/experience-optimization-classic.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.