The first 3 interviews are free · Start free or see the prices

Stakeholder Interview: Questions to Ask Before a Project

Use this guide with people inside your company before a project starts. It finds the decisions the project must support and what each stakeholder believes. It also finds the constraints on the work.

Length
45 min
Questions
14
People
5 to 10
Sections
6
Run this study

What this guide finds out

  • The decisions that each stakeholder will make with the results of the project.
  • How each stakeholder defines success, and where these definitions conflict.
  • What stakeholders already believe about customers, and the evidence behind it.
  • The constraints, risks and politics that will shape the project.
  • How each stakeholder wants to receive findings.

When to use it

  • You start a research or product project that several teams care about.
  • You join a new company or team and need to learn what leaders expect.
  • A past project failed because the findings did not match what leaders needed.

Who to talk to

People inside your company who will fund, decide on, build or sell the result of the project. Talk to 5 to 10 people. Each interview takes about 45 minutes.

The discussion guide

Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.

01

Role and decisions

6 min

Learn how the project affects this person and what they will decide.

  1. What is your role, and how does this project affect your work?

    ProbeAsk what part of the project they own or fund.

  2. Which decisions will you make based on the results of this project?

    ProbeAsk for the specific decision and the date. If there is no decision, record that. The project may need a new focus.

02

Goals and success

10 min

Find the business goal and the measure of success for this person.

  1. What problem should this project solve for the business?

    ProbeAsk which customers or teams are affected. Ask what it costs the business today.

  2. In six months, how will you know that the project worked?

    ProbeAsk for one measure they will watch. Compare it with the answers of other stakeholders later.

  3. What happens if this project does not go ahead?

    ProbeThis shows how urgent the project is for this person.

03

Knowledge and assumptions

10 min

Learn what the person believes about customers and on what evidence.

  1. What do you already know about the customers for this project? Where does that knowledge come from?

    ProbeSeparate data from stories. Ask for the source of each belief: a report, a customer call or experience.

  2. Which assumption about customers are you least sure about?

    ProbeRecord it word for word. These assumptions become the research questions.

  3. What research or data has the company collected on this topic before?

    ProbeAsk where it is stored and who owns it. Ask what happened with the results.

04

Constraints and risks

10 min

Find the limits and risks the team must plan for.

  1. Which constraints should the team know about, such as budget, technology, legal rules or timing?

    ProbeAsk which constraint is fixed and which can change.

  2. What could make this project fail?

    ProbeAsk about dependencies on other teams, competing projects and changes in leadership.

  3. Who else has a strong opinion on this project, and what is it?

    ProbeAsk for roles and positions. If there is a conflict between teams, ask how it is usually resolved.

05

Working together

6 min

Agree how to share findings so that this person uses them.

  1. How do you want to hear about the findings, and how often?

    ProbeAsk about format: a short summary, a meeting, video clips or a full report.

  2. What would make the findings useless to you?

    ProbeListen for timing, format and trust in the method. Ask for an example from a past project.

06

Close

3 min

Capture the main question in the words of the stakeholder.

  1. Which question do you most hope this project will answer?

    ProbeRecord it word for word. Thank them and end the interview.

Example finding

ExampleDifferent measures of success

Sales leaders measured success by deal size, while product leaders measured it by weekly active use.

“If this does not help us close bigger deals, I do not see the point. Usage is nice, but it does not pay the bills.”
In a User Evaluation study report, each claim links to the clip where a participant says it.

Mistakes to avoid

  • Do not interview stakeholders in a group. People with less power agree with the most senior person.
  • Do not treat stakeholder beliefs as findings about customers. Record them as assumptions to test.
  • Do not skip people who will build or sell the result. They know constraints that leaders often do not.
  • Do not share what one stakeholder said with another by name. Report the themes, not the people.

Analyze the answers

Analysis templateResearch Insight Report Template: Findings, Insights, ActionsUse this template to write the report at the end of a qualitative study. Each element has a rule, so readers can tell facts from interpretation and see the strength of the evidence.

Questions

A stakeholder interview is a conversation with a person inside the company who has an interest in a project. It finds their goals, beliefs and constraints before the work starts.

Anyone who will fund, decide on, build, sell or support the result. Include people from sales, support and engineering, not only leaders.

Yes. Some stakeholders give more direct answers when they do not talk to a colleague. Use a person when the relationship matters, for example with a senior sponsor.

Write a short summary of the goals, the measures of success and the assumptions to test. Share it with all stakeholders before the project starts.

Let the AI moderator ask these questions

The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.

Run this study