> For the complete documentation index, see [llms.txt](https://docs.opendialog.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile.md).

# Outcome: user profile

The outcome of any primary and secondary research needs to be analyzed and summarized to be useful as an input to design. One way to summarize the information is to create a user profile. The user profile is similar to a user persona description, but more focused on information that's relevant to the use of the product specifically. If you wish, you may use user personas instead.

Here is an example of a user profile.

<figure><img src="/files/iI1mUhTYxA6m5cYAmEfn" alt=""><figcaption></figcaption></figure>

Depending on the complexity of the user interaction with a product, it may be useful to summarize other insights, in addition to the user profile. A live handoff of this information from the UX research team to the designers is preferable.


---

# 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://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile.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.