> 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/stakeholder-interviews.md).

# Stakeholder Interviews

Stakeholder interviews involve conducting one-on-one discussions with individuals or groups who have a vested interest or influence in a project or initiative.&#x20;

These interviews aim to gather insights, perspectives, and feedback from key stakeholders to understand their needs, expectations, and concerns. The interviews typically focus on understanding stakeholders' roles, goals, and their desired outcomes from the project.&#x20;

By conducting stakeholder interviews, organisations can gain a deeper understanding of stakeholder perspectives, uncover potential challenges, and identify areas for alignment or improvement. The insights gathered from these interviews inform decision-making, stakeholder engagement strategies, and project planning.&#x20;

Stakeholder interviews help ensure that stakeholder voices are heard, concerns are addressed, and their input is incorporated into the project's design and implementation.

#### Further Reading

{% embed url="<https://medium.com/@tonyodonohoe/something-5880ed16f1ba>" %}

{% embed url="<https://www.nngroup.com/articles/stakeholder-interviews/>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=fekaYjH7Ysw>" %}

{% embed url="<https://www.youtube.com/watch?v=Hu2PfM1fV1g>" %}

{% embed url="<https://www.youtube.com/watch?v=MOlDhx_Wn50>" %}

{% embed url="<https://www.youtube.com/watch?v=HP2MZscvFl8>" %}


---

# 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://www.designreference.xyz/ux-methods/discovery/stakeholder-interviews.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.
