Stakeholder Interview Questions for Strategy Work, With a Guide

Eighteen interviews, one slide of platitudes

Picture the second week of a strategy project. The team has interviewed 18 senior leaders, an hour each. The synthesis slide says: “Customers are changing faster than we are.” “We need to be more agile.” “Silos slow us down.” “Execution is the problem, not strategy.” Every leader nods when it is presented. Nobody learns anything. Eighteen hours of the most expensive time in the company bought four sentences that were true before the project started.

The interviews were not too short or too few. They asked for opinions, so they got opinions, and senior people's opinions about their own company are the most rehearsed sentences they own. “What are the biggest challenges facing the business?” has a polished answer in every executive's head. It is the answer they gave at the last offsite.

Stakeholder interview questions for strategy work are the questions a strategist asks the people who hold information, influence or a stake in a decision, to learn facts the data cannot show, the positions people will take, and what would move them. The ones that work ask about specific past events (the last deal lost, the last decision reversed), about real choices, and about what would change the person's mind. They collect evidence that can be compared across interviews.

That is the thesis of this page: an interview is the one hour you get to buy evidence instead of opinion. Ask what happened, not what people think, and 18 interviews become a data set.

Ask what happened last time, not what should happen next time.

What the interviews are for

Strategy interviews do three jobs, and a good guide is built for all three.

• Facts the data cannot show. How decisions actually get made, why the last initiative stalled, which customer complaint never reaches a dashboard. These are the reason to interview at all.
• Positions and red lines. What each person would support, what they could not, and why. You need these before options harden, not after.
• Movement. Being asked changes people. Nielsen Norman Group lists increasing buy-in among the reasons to interview stakeholders ¹. In our experience, someone whose view visibly shaped the diagnosis is far easier to bring along to the conclusion.

Whom to interview, and in what order, is the job of a stakeholder map; that page also lists the questions that suit each group. This page is about how to ask them. One thing interviews are not: a vote. Ten leaders saying the same thing is one finding with ten sources, and possibly one shared blind spot.

The guide

A guide gives the interview direction without becoming a questionnaire. Nielsen Norman Group describes stakeholder interviews as usually semistructured: a discussion guide sets the direction but need not be followed precisely ¹. Build it in five blocks and a close for a 45 to 60 minute conversation. If you have only the 30 to 45 minutes the stakeholder map page suggests, keep blocks 2 and 4 and shorten the rest. Before the questions, write the header: the decision the interviews inform, the two to four hypotheses you are testing, and why this person is on the list.

Block 3 borrows a method from research on strategy alignment. Donald Sull, Charles Sull and James Yoder asked managers to list their company's strategic priorities, and across 124 organizations only 28% of the executives and middle managers responsible for executing strategy could list three ³. Asked in an interview, the same question tells you more than “How well is the strategy understood?” ever will. Block 5 is Gary Klein's premortem, turned into a question for one person: team members “assume that the project they are planning has just failed” and explain why ⁴. People who would never criticize a plan will readily explain its imagined failure. The close borrows Nielsen Norman Group's own final question: “Who else should I speak to?” ¹.

Questions that collect evidence

The difference between an opinion question and an evidence question is usually one rewrite. The opinion version asks for a judgment in general. The evidence version asks for a specific event, a number or a choice.

Then strip out the leading questions. Nielsen Norman Group defines a leading question as one that “includes or implies the desired answer to the question in the phrasing of the question itself,” and gives the example of asking “Why did you have difficulty with the navigation?” when nobody has said the navigation was difficult ². Strategy interviews are full of them: “Don't you think the channel conflict is getting worse?” tells the interviewee what you believe, and senior people are skilled at telling a strategist what they want carried back.

Keep probes ready for when an answer turns general: “Tell me more about that,” “Can you give me an example?” ¹, “When was the last time?”, “What did you do next?”, “How do you know?” The last one is the most useful and the least asked.

Running the hour

1. Send a short note aheadTwo or three sentences: the decision the work informs, why you want their view, how long it takes and how notes will be used. Do not send the questions; you will get prepared answers.
2. Interview one person at a timeNielsen Norman Group advises speaking to stakeholders one on one ¹. Two leaders in one room give you the answer they can agree on in front of each other, which is the least useful one.
3. Bring a note-taker if you canThis is our practice, not a rule from the sources: one person asks, one writes. Notes in the speaker's own words, with numbers and names written down exactly. Mark your own interpretations separately.
4. Let silence workAfter an answer, wait. The second thing a person says is often the true one. Nielsen Norman Group's advice applies: “Even if the stakeholder is long-winded, don’t interrupt them” ¹. Stay as neutral as possible ¹; nodding at the answers you like trains the interviewee to give more of them.
5. Follow the energy, then return to the guideWhen someone becomes animated, follow it with a probe. Then come back. Check the clock at the halfway mark and drop the least important block.
6. Close and write up the same dayAsk the closing questions. Within a few hours, write a one-page note: facts, positions, quotes, documents promised. Memory turns evidence into opinion within days.

A filled-in example

Look at what the notes contain. A specific event with a number and a cause that cuts against hypothesis 2. A position with a condition attached. A risk nobody would raise in a steering meeting. A name and a document. None of it is an opinion about whether direct channels are good.

From eighteen interviews to a finding

Synthesis is where most interview programs lose their value, because the notes get summarized into themes and the themes come out as the platitudes from the opening. Work the other way: from hypotheses to evidence.

1. Tag every note to a hypothesis. For each, mark whether it supports, contradicts or is neutral, and whether it is a fact the person observed or an opinion.
2. Count facts, not mentions. Seven people saying brokers would revolt is one opinion repeated. One person describing the last broker who left, and why, is evidence.
3. Build a contradiction table. Where two interviewees describe the same event differently, that disagreement is often the finding.
4. Check every important fact against data or documents. Interviews tell you where to look. They are not the last word on what happened.
5. Report positions separately from findings. “Head of distribution would oppose direct sales above a size threshold” is a position for the stakeholder map. “The last broker loss was over price” is a finding.

If a hypothesis survives the interviews, write down what would still kill it and test that with data. The hypothesis-driven problem solving page covers how.

Politics, posture and the case against interviews

The strongest objection is that strategy interviews are theater. Senior people use them to lobby. They say what they want carried to the CEO, protect their budgets and posture for the strategist they assume will brief the top team. Eighteen interviews with motivated speakers, the argument goes, are worse than no interviews, because they look like evidence.

There is truth in it, and the evidence-question method is the answer to most of it. Lobbying lives in opinions and forecasts. It is much harder to spin “walk me through the last deal you lost” than “what should our strategy be?” Facts can be checked, and checking a few in front of the next interviewee (“finance's numbers show that deal at half that size”) changes how carefully everyone answers.

• Set the confidentiality terms and keep them. If something said in confidence surfaces in a steering meeting with a name attached, every later interview is a press release.
• Interview in a deliberate order. The stakeholder map sets who goes first. Within that, where you can, hear from someone close to the work about an event before you ask the executive who oversaw it, so you can ask about specifics rather than collecting their framing first.
• Watch the interviewer's own posture. Strategists lobby too. If you notice yourself steering toward a hypothesis your sponsor likes, your notes will show it: count how often you probed confirming answers versus contradicting ones.
• Treat the interview as an intervention. Someone who was asked well, and whose evidence visibly shaped the diagnosis, is more likely to argue for the conclusion than against it. That is not a side effect. For some decisions it is the main reason to do the interviews.

A last limit: interviews tell you about the organization's beliefs, and the hardest strategy problems are often ones the whole organization shares. Ask customers, former employees and the people who left for competitors as well. They have no stake in your current story.

Before your first interview

• The guide header names the decision, the hypotheses and why each person is on the list.
• At least half the questions ask about a specific past event, number or choice.
• No question contains its own answer.
• The premortem question and “Who else should I speak to?” are in every guide.
• Confidentiality terms are written down and the same for everyone.
• Someone is taking notes in the speaker's words, and the write-up happens the same day.

The eighteen interviews in the opening cost eighteen hours of executive time and produced four sentences anyone could have written. The same eighteen hours, spent on what happened, who decided and what would change a mind, would have produced the diagnosis. Opinions are free in every meeting. The interview is the one hour you get to collect the evidence.

Questions

What questions should you ask in a stakeholder interview?

Ask mostly about specific past events, numbers and choices: walk me through the last deal you lost, who made the last escalated decision and how long it took, what your team stopped doing because of the strategy. Add a question on which options the person could not support and what would change their mind, a premortem, and close with who else you should speak to.

How long should a stakeholder interview be?

For strategy work, 45 to 60 minutes is a practical length for a guide of five short blocks and a close: opening, a past event, priorities, the decision and a premortem. If you have only 30 minutes, keep the past event and the decision blocks and drop the rest.

What is a leading question, and why avoid it?

A leading question includes or implies the answer you want, such as “Don't you think the channel conflict is getting worse?” It tells the interviewee what you believe, and in strategy interviews senior people are quick to give the answer they think will be carried back. Ask open questions about what happened instead.

How do you synthesize stakeholder interviews?

Tag each note to a hypothesis as supporting, contradicting or neutral, and as an observed fact or an opinion. Count facts rather than mentions, build a table of contradictions, check important facts against data, and report people's positions separately from findings about the business.

Where to go next

• Stakeholder Mapping for Strategy Work
• How Strategists Think: Hypothesis-Driven Problem Solving
• Stakeholder Engagement Framework
• Stakeholder & Power Map