# Stakeholder Interview Questions: A Project Guide by Role

Stakeholder interview questions by role, plus a worked project example to compare conflicting accounts and plan useful follow-ups.

- Canonical URL: https://www.harmate.com/en/blog/stakeholder-interview-questions-guide
- Author: Harmate Team
- Published: 2026-10-25
- Updated: 2026-10-25T22:43:08.172312+00:00
- Language: en

## Content

# Stakeholder Interview Questions: A Project Guide by Role

Before changing a service, process, or tool, prepare a shared set of interview prompts and a few questions tailored to each stakeholder’s experience. Ask the sponsor about decisions, frontline staff about actual work, support teams about exceptions, and users about their own journeys. Each important account should lead to a specific follow-up that someone can investigate.

This guide is for project stakeholder interviews, rather than hiring interviews about stakeholder management skills. It includes questions you can adapt and a worked example showing how apparently conflicting accounts lead to different checks.

## Choose perspectives before writing the guide

A manager may explain a rule without knowing every situation in which people apply it. A user may describe a confusing journey without knowing the processing constraints behind it. These accounts offer different perspectives; no single job title guarantees a complete picture.

Use a [stakeholder map](/en/blog/stakeholder-mapping-who-to-involve-and-whose-voice-is-missing) to identify affected people and missing voices before sending invitations. Look for contrasting experiences too: routine cases and exceptions, recent arrivals and experienced staff, completed journeys and abandoned ones. This selection helps explore variation; it does not automatically create a representative sample.

Write one sentence at the top of the guide: “These interviews should help us understand [situation] to inform [decision].” If you still need to agree on the assignment with the sponsor, the [semi-structured interview guide](/en/blog/semi-structured-interview-guide-method-steps-and-15-examples) includes a separate commissioning-client framework.

## Keep a common thread across interviews

[Nielsen Norman Group’s professional guide to stakeholder interviews](https://www.nngroup.com/articles/stakeholder-interviews/) recommends preparing themes around the interview goal and the stakeholder’s role while allowing conversational follow-ups. The questions below are an applied working template for a service project, not a validated survey instrument.

Start with an actual experience:

- “What was your role in the most recent instance of [situation]?”
- “What happened, from the beginning through your last involvement?”
- “Where did you need to wait, ask for clarification, or change how you worked?”
- “Can you describe another case that went differently?”

Keep these themes comparable without reading every follow-up mechanically. Open-ended answers can surface details your initial categories would have missed. Their richness still depends on the setting and the interview: openness alone does not establish accuracy or representativeness.

Explain who can read the notes, how quotations may be used, and what participants will hear afterward. Do not promise confidentiality that the actual arrangement cannot deliver. If you want to record, explain that and obtain the necessary agreement before starting. Choose a setting in which the participant can discuss the work without being asked to account for it in front of a supervisor.

## Questions to ask each stakeholder role

Select the prompts that matter to the project and ask them separately. Someone may hold several roles; record which experience they are drawing on rather than forcing them into a single category.

### Project sponsors: decisions and trade-offs

Once the assignment is scoped, explore actual decisions and their consequences:

1. “Walk me through the last decision you made about this service.”
2. “What information was available when you made it?”
3. “What happened afterward that you could observe?”
4. “What evidence would lead you to revisit that choice now?”

A useful follow-up is: “Who observed that consequence directly?” It distinguishes the sponsor’s own experience from an account passed on by another team.

### Frontline staff: work as it happens

1. “Thinking about your most recent case, what did you receive at the start?”
2. “What did you do next, including any steps outside the usual procedure?”
3. “Where did you need input from another team?”
4. “When does this approach stop working?”

Ask to review an authorized example or a record of a handoff without collecting unnecessary personal information. Avoid “Why don’t you follow the procedure?” That question has already assumed both a deviation and someone at fault.

### Support teams: exceptions and recovery

1. “Describe a recent request that required your intervention.”
2. “What did the person know when they contacted you?”
3. “What did you check before responding?”
4. “What resolved the case, or what left it open?”

Support records describe the cases that reached support. Before treating their distribution as the distribution of all user experiences, ask which problems people resolve elsewhere or never report. Keep that gap visible in the notes.

### Users: the experienced journey

1. “What were you trying to accomplish the last time you used this service?”
2. “How did you work out what to do?”
3. “What happened after you submitted your request?”
4. “How did you know the process was complete?”

Use the participant’s own wording for follow-ups: “When you say ‘approved,’ which message had you received?” An employee’s account of what users think is indirect evidence. It does not replace speaking with people about their own experience.

## Worked example: three accounts of different events

**This example is entirely fictional.** A training provider wants to improve workshop registration. Leadership says confirmations are immediate. Administrative staff say they are waiting for a document. A participant says she paid but could not tell whether her place was reserved.

| Account | Next interview question | Person or record that could clarify it |
|---|---|---|
| Sponsor: “Confirmation goes out immediately.” | “What does that message confirm: receipt, payment, or completed registration?” | Journey owner and the automatic message template |
| Administration: “We are waiting for the supporting document.” | “Where does that pending step appear in this particular case?” | Staff member handling the case and its request history |
| Participant: “I had paid but did not know whether I was registered.” | “Which messages did you receive, and in what order?” | Participant and any messages she agrees to share |

The interviews do not yet establish that the system failed or that the participant misunderstood it. “Confirmation” may refer to several different events. The next step is to compare messages and timestamps for the same case, then examine a contrasting case. The journey owner can subsequently decide whether to clarify a message, change a step, or investigate further.

Do not settle the issue by counting which account appears most often. Several people might describe the same intended rule while one person describes a different exception. First establish what each statement refers to and which evidence could distinguish the explanations.

## Close with a useful follow-up record

Before ending, summarize one or two important situations and ask what you misunderstood. Then ask: “Who could describe another part of this case?” and “What record might help check this point?” An unanswered question remains an explicit limit rather than a gap to fill with an assumption.

For each account you retain, record the role and context, an exact excerpt, the event described, a provisional interpretation, the unresolved question, and someone able to help investigate it. Keep conflicting accounts separate. The [organizational diagnosis evidence matrix](/en/blog/organizational-diagnosis-an-evidence-matrix-for-conflicting-perspectives) provides a next step for comparing these accounts with documents and observations.

When you have written responses to examine, [Harmate’s open-ended response analysis](/en/product/open-questions) can help you review themes and findings while returning to supporting excerpts. You select the material that belongs in the decision file. The tool does not decide which stakeholder is right or replace follow-up work in the field.