Questions to Ask for Feedback on a Project
Twenty questions for getting useful feedback on a project instead of polite approval. They work for a manager, a client, a reviewer, or a colleague, and they are written to be asked while there is still time to change the work.
The questions
Open any question for the note
What is your honest first reaction, before we get into detail?
Why ask it
First reactions are the closest thing you will get to how an audience will meet the work, and they decay within a minute of analysis. Ask for it before you start explaining anything, because your explanation will replace it.
If you could change only one thing, what would it be?
Why ask it
Forcing a single answer produces a ranking, which a list never does. If someone genuinely cannot pick, ask what they would change if they had one hour rather than one month.
Where did you get lost, or have to read something twice?
Why ask it
This asks about their experience, which they can report accurately, rather than for a judgment they may feel unqualified to give. Points of confusion are also the cheapest defects to fix.
What did you expect to see here that is not here?
Why ask it
Missing pieces are far harder to notice than weak ones, because nothing on the page prompts you to think of them. A reviewer's expectations are a map of what the work seemed to promise.
Which part are you least convinced by?
Why ask it
Softer than asking what is wrong, which makes it more likely to get a real answer from someone senior to you or paying you. Note whether their weak point is the one you already suspected.
In one sentence, what would you say this is mainly about?
Why ask it
If the summary that comes back is not the one you intended, no amount of polish on the detail will help. It is the fastest test of whether the central point survived the draft.
Who did you picture reading this?
Why ask it
Work aimed at nobody in particular usually reads as written for the author, and the reviewer's guess reveals which audience the draft actually addresses. A mismatch here explains most disagreements about tone and depth.
What would someone who disagrees with this say?
Why ask it
This lets a reviewer voice an objection without owning it, which is often the only way to hear it. It is particularly effective with people who default to being encouraging.
Which decision here would you have made differently, and why?
Why ask it
Focuses on choices rather than execution, and the reasoning behind their alternative is usually worth more than the alternative itself. It also surfaces constraints they know about and you do not.
What is this ready for, and what is it not ready for?
Why ask it
Reframes feedback around a decision rather than a grade, so you learn whether it can go to a client, a wider team, or nobody yet. This is the answer to quote when someone else asks about status.
Who else needs to see this before it goes out, and what will they push back on?
Why ask it
Reviewers often know the politics better than the craft, and this uses that knowledge. Naming the likely objection in advance is how you avoid a late round of changes.
What did I spend too much time on?
Why ask it
Almost nobody volunteers this, because pointing at wasted effort feels unkind. It is the question that most reliably changes how you work on the next project rather than this one.
Is the goal I set for this the right goal?
Why ask it
Feedback usually assumes the brief and critiques the execution, which is useless if the brief was wrong. Ask it early, because after a certain point the answer cannot be acted on.
How does this compare with similar work you have seen?
Why ask it
Gives you a benchmark you cannot construct yourself, and reveals a standard the reviewer is applying without having stated it. Follow up by asking what the best example did differently.
What would make this a clear yes for you?
Why ask it
Converts hedged feedback into a condition you can meet, and exposes whether the objection is fixable at all. If there is no answer, the concern is probably about something other than the work.
What could come out entirely without anything being lost?
Why ask it
Reviewers find it much easier to nominate cuts than to name what is weak, and the two lists overlap heavily. Anything two reviewers would both cut is not doing work.
Where does it sound like it is trying too hard?
Why ask it
Overclaiming and padding are obvious to a reader and invisible to the person who wrote them at midnight. This is also where credibility gets lost with a skeptical audience.
What is the smallest change that would make the biggest difference?
Why ask it
Useful when the deadline is close and a rebuild is not available. It also tests whether the reviewer's critique is grounded in something specific or is a general unease.
If we shipped this as it is, what do you think breaks first?
Why ask it
Shifts the conversation from taste to consequence, which is where reviewers with operational experience are most valuable. The failure they name is worth planning for even if you disagree about the odds.
Now that a day has passed, what has stayed with you?
Why ask it
Ask this in a follow-up message rather than in the room, because it only works once the detail has faded. What a reviewer still remembers unprompted is what the work actually communicated, and it is rarely the part you worked hardest on.
Getting feedback people are willing to give
Practical guidance for the conversation itself
Set the request up properly
Ask before you are finished
Feedback on work that is clearly complete arrives as approval, because nobody wants to cause a rebuild. Show it at seventy per cent and say so.
Tell them what kind of feedback you want
Structure, argument, numbers, or wording are different jobs, and reviewers default to the easiest one, which is wording. Name the two you care about and say which you do not need yet.
Give them a specific question and a deadline
A vague request for thoughts produces a vague reply a week late. One question plus a date gets a usable answer.
Pick reviewers who differ
One person who knows the subject, one who represents the audience, and one who will say the unpopular thing will cover more ground than three colleagues who sit near you.
In the conversation
- Do not explain first. A two-minute defence in advance shapes everything you hear afterwards.
- When you disagree, write it down and say nothing. Arguing in the moment trains them to stop offering.
- Ask for the example behind a general statement: which paragraph, which slide, which number.
- Separate matters of correctness from matters of taste, and say out loud which one you think you are hearing.
- Repeat back the single most important point before you close, and check you have it right.
Afterwards
Reply with what you changed and what you did not
A short note that names the changes you made, and the one you decided against with a reason, is what makes someone willing to review your next project.
Keep a record of repeated comments
The same criticism from three different reviewers across two projects is a pattern in your work, not an opinion about one piece. That is the feedback worth acting on structurally.
Close the loop on outcomes
If a reviewer's warning turned out to be right, tell them. It is the cheapest way to keep a candid reviewer.
Common pitfalls
Asking whether they like it
This is a question about the reviewer's manners rather than the work, and almost everyone answers yes. Ask what is weakest instead.
Sending it to everyone at once
Twelve sets of comments on the same draft produces contradictions you then have to arbitrate. Two or three reviewers per round works better.
Treating all feedback as equally weighted
The person who will use the work, the person who signs it off, and the person who happened to be in the meeting have different standing. Decide whose objection has to be resolved before you start editing.