> 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/user-interviews.md).
# User Interviews
User interviews involve engaging with individuals who represent the target audience or user base of a product, service, or experience.
These interviews aim to gather insights about users' needs, preferences, behaviours, and pain points. By conducting user interviews, researchers and designers can gain a deeper understanding of user perspectives, motivations, and goals. The interviews are typically conducted in a conversational manner, allowing users to express their thoughts, experiences, and feedback.
User interviews help uncover valuable insights that inform the design process, improve user experiences, and validate assumptions. They provide an opportunity to empathise with users, gather qualitative data, and generate ideas for enhancements or innovations. User interviews contribute to user-cantered design by ensuring that products or services meet user needs and align with their expectations.
#### Further Reading
{% embed url="" %}
#### Further Viewing
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
---
# 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://www.designreference.xyz/ux-methods/discovery/user-interviews.md?ask=&goal=
```
`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.