Feedback is most useful when it describes something you can see, hear, or change. Yet many requests for feedback are vague: “What do you think?” or “Any comments?” These questions invite general praise or a reaction that is hard to act on. A better question points to one moment, asks for an observation, and invites a small experiment. This guide uses an example unrelated to performance ratings, such as a draft email, a short presentation, or a project plan, to show how the same approach works in everyday work.
A practical example
“Does this look OK?” is a difficult favor to do well. The recipient has to guess whether you want proofreading, encouragement, or a reason to change direction. Compare these two requests about the same proposal:
“Can you review this before Friday?”
“Could you read the pricing paragraph by Thursday? Without looking at the table, tell me which revisions you think the fee includes. I’m deciding whether the table needs to move up.”
The second request tells your colleague where to look, what to report, and which decision is still open. It doesn’t tell them which answer you hope to hear. If they say “two rounds” and you meant one, you’ve learned something useful without asking anyone to rate your writing.
When the answer is vague
Suppose your colleague replies, “Seems fine.” Instead of pressing for criticism, try “If the client asks for a third draft, would you expect a new charge?” If they found the answer immediately, ask which words settled it. If they had to guess, ask where they looked first. Either reply is more useful than another verdict.
The observation and the proposed fix are different things. A reader who missed the revision limit might suggest rewriting the whole proposal. You can take the observation seriously and try a smaller edit: move the limit next to the price. Ask a fresh reader the same question before deciding you’ve fixed it.
Ask while you still have time to act. If the price is settled and the proposal goes out tomorrow, say so. Five minutes spent checking whether the terms are clear is a fairer request than inviting a colleague to rethink a decision you cannot reopen.
Pick one specific moment
Start by choosing the part of the work you want help with. Instead of sending an entire document, identify a paragraph, a slide, a decision, or a single exchange in a meeting. Specific requests give the other person something concrete to examine. For example, “Could you look at the opening paragraph of this proposal?” is easier to answer than “Could you review the proposal?”
Explain briefly what you were trying to achieve in that moment. A sentence of context helps the reader understand whether the section is doing its job.
Ask for an observation
An observation describes what happened. A verdict judges whether it was good. Ask for observations because they are easier to use. “When you read the opening, where did your attention drift?” asks for a direct reaction. “Is the opening good?” invites a simple yes or no, which tells you little about what to change.
Observations also reduce the pressure on the reader. People are often more willing to describe what they noticed than to pass judgment on your work, and the descriptions usually contain the clues you need.
Name the decision you need to make
Tell the reader what decision the feedback will help you make. Are you deciding whether to shorten the section, change the order, or keep a particular example? When the purpose is clear, the other person can focus their attention on the question that matters, and you can judge their response more quickly.
If you have already made a choice, say so. Feedback on a settled decision may be less helpful than feedback on the part you are still unsure about.
Make it easy to answer
Reduce the effort required to respond. Give a deadline that fits the reader’s schedule, specify how much time you need, and offer to discuss the result in a short call if that is easier. If you can, send the material with a clear question at the top. A reader who can answer in five minutes is more likely to give thoughtful feedback than one who must find an hour.
Listen for what is not said
Sometimes the most useful feedback is an absence: a reader skipped a section, asked a question you did not expect, or rushed through a paragraph. Notice those signals. If someone says the section is fine but seems confused when you discuss it, ask a follow-up question such as “Which part felt least clear?” That question often reveals the real issue.
Avoid defending the work while the other person is speaking. Your job during the conversation is to understand their view, not to justify each choice.
Try one change before asking again
After you receive feedback, choose one change to test. Changing everything at once makes it hard to know which edit helped. Make the change, then ask a specific follow-up question about the same moment. This creates a useful loop: request, observation, one adjustment, and a second look.
Thank the reader for their time, and tell them what you changed based on their input. People are more willing to help again when they see that their observations were taken seriously.







