Questions to Ask Stakeholders for Feedback
Questions for the conversation where you put work in front of a stakeholder and ask what they think, covering first reactions, missing pieces, the objection they are too polite to raise, and who actually owns the decision.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
Before I show you anything, what were you hoping this would do for you?
Asked first, this anchors the review to their original expectation instead of to the thing in front of them. If they cannot state an expectation, everything they say afterwards will be taste rather than judgement, and you should weight it that way.
- 2
What is your first reaction, before you talk yourself into being fair?
The first ten seconds are the only moment a stakeholder responds like an ordinary user. Once they start being constructive they start editing, so write the raw reaction down verbatim and do not argue with it.
- 3
Which part did your eye go to first?
Attention order tells you what your emphasis actually communicates, which is often not what you intended. If the first thing they name is a caveat, a footnote or a chart axis, your hierarchy is inverted.
- 4
What did you expect to see here that is not here?
Absence is the hardest thing for a reviewer to notice unprompted, because people react to what is on the page. Asking directly is usually the only way missing scope surfaces before it becomes a late change request.
- 5
Which part would you have to explain to someone else on your team?
Almost nobody admits to being confused, but everybody will happily predict confusion in a colleague. Whatever they name is the part that needs rewriting, relabelling or removing.
- 6
If you had to cut one thing from this, what would go?
Forcing a cut gets you priorities without asking for them, which stakeholders usually refuse to give in the abstract. Note whether they cut something of their own or something of someone else's.
- 7
What would you change if we had two more weeks?
A two week horizon collects polish items: wording, layout, one more example. Keep this list separate, because it is cheap and it buys goodwill without touching the plan.
- 8
What would you change if we had two more months?
The same question at a longer horizon collects direction, not polish. If the two answers point in different directions, you have a scope disagreement that the short answer was hiding.
- 9
Does anything here create work for you or your team?
Stakeholders rarely object on the merits. They object because a decision quietly moves effort onto their people, and the objection arrives later dressed as a concern about quality. Ask now and you get the real one.
- 10
What is the part you were dreading, and did it show up?
People come into reviews carrying one specific worry. Naming it lets you address the thing they actually came for, rather than the twelve smaller notes they gave you because the big one felt rude to raise.
- 11
Which of my assumptions do you think is wrong?
This asks them to critique the reasoning rather than the artefact, which is where stakeholders usually know more than you do. Vague answers here often mean they have not read the underlying material.
- 12
Who else is going to have an opinion about this that I have not heard yet?
Stakeholders know the political map better than you do, and most late vetoes come from someone who was never in the room. The names you get here are the ones worth a separate conversation before you commit.
- 13
If we shipped this on Monday as it stands, what would you be nervous about?
A deadline in the question converts abstract criticism into risk, and risk is specific. What they name is the difference between a note you can defer and one you cannot.
- 14
What feedback have you given on something like this before that went nowhere?
Half of stakeholder frustration is repeat feedback that was never acknowledged. Hearing the old note lets you either act on it or explain why not, and either one is better than being the third person to ignore it.
- 15
Which of the changes you have asked for is the one you actually care about?
Most people give you a list because a list feels thorough, not because every item matters. Asked to rank, they will usually drop half of it themselves, and the survivor is the one to negotiate over.
- 16
What would you say about this in a room I am not in?
Said lightly, this gives permission for the blunt version. If the answer is identical to what they have already told you, that is a good sign about the working relationship rather than a wasted question.
- 17
What did we get right that you would not want changed in the next round?
Review sessions collect only defects unless you ask for the opposite, and teams then quietly break the parts that were working. This is the only question in the set that protects existing work.
- 18
Six months after this lands, what would tell you it was worth doing?
Stakeholders judge finished work against a private definition of success they have never written down. Getting it now means the next review is against an agreed standard rather than a moving one.
- 19
How much of this decision do you want to own, and how much do you want me to own?
Ambiguity about who decides is the most common cause of feedback loops that never end. Ask them to place themselves as decision maker, consulted, or informed, and repeat their answer back.
- 20
How and when do you want to hear about this next?
Closing on cadence prevents the drip of one-off check-ins that consume a project. It also surfaces people who want weekly involvement in something they described as a low priority ten minutes earlier.
Getting useful feedback out of stakeholders
Practical guidance for the conversation itself.
Setting the session up
Setting the session up
- Say at the start what kind of feedback you want: direction, detail, or a decision. Reviewers default to line edits because that is the easiest thing to produce.
- Send material in advance, then assume nobody read it. Budget five minutes to walk through it anyway rather than discovering the gap halfway in.
- Interview stakeholders one at a time when their interests conflict. Group sessions produce the most agreeable answer in the room, not the most accurate one.
- Ask reaction questions before explanation questions. Once you have justified a choice, you can no longer find out how it reads cold.
- Write answers in their words. Paraphrasing in the moment is where feedback quietly becomes what you already believed.
Reading what you get back
Reading what you get back
- Feedback about wording is often feedback about direction that the person has not fully formed. Ask a follow-up before you go and change the wording.
- Repeated small notes on one section usually mean the section is wrong at the structural level, not the sentence level.
- Silence from a stakeholder who normally has opinions is information. It generally means they have stopped believing the project will happen.
- Distinguish preference from constraint. Preferences can be negotiated in the room, constraints have to be designed around.
- If two stakeholders contradict each other, do not average them. Take the conflict back to whoever owns the decision and name it plainly.
Closing the loop
Closing the loop
- Send a short summary of what you heard, what you will act on, and what you will not. The second list matters more than the first.
- Give a reason for anything you decline. Unexplained refusals are why people stop giving feedback and start escalating instead.
- Track which requests came from whom. When priorities collide later, the record is more persuasive than memory.
- Come back to the person whose note you rejected before the next review, not during it. Nobody likes hearing no in front of an audience.