Ask for Feedback on a Work Draft Without Getting Only 'Looks Good'
Link the current draft, say who it is for and what stage it is at, then ask a question the reviewer can answer. Give a real response window and say where comments belong. Feedback can inform a decision; it does not automatically approve the work or make the reviewer responsible for it.
Miles Crawford
Replace "thoughts?" with the question behind it
"Thoughts?" can be a genuine invitation to explore. But if you need to know whether an introduction explains the next step, ask that. Otherwise a reviewer may polish sentences while you are still deciding what the document should say.
The University of Illinois Writers Workshop recommends naming the writing stage and the kind of feedback that would help. UNC's Writing Center similarly recommends a short background followed by specific questions. Their guidance is about academic writing; the useful principle transfers to a work draft without making every workplace review an academic exercise.
Our examples below are fictional. They illustrate how to frame a review, not a claim that a particular phrase guarantees better comments.
The first draft of the volunteer arrival note is linked here. It is for people who have never visited the venue. Could you read the opening section and tell me what you would do first on arrival? I am checking whether the instructions are clear before polishing the wording.
Asking a reader to describe their understanding can expose a mismatch that "Is this clear?" may not reveal. Do not lead them toward the answer you want, such as "You can obviously see the check-in desk comes first, right?"
Match the review to the draft stage
Use this original decision aid to choose the request. These are examples, not fixed stages every team must adopt. A serious factual, safety or accessibility issue remains relevant even when the requested review is narrow.
| What is still open? | A useful question |
|---|---|
| Purpose or direction | Does this address the reader's actual task? What important need is missing? |
| Structure or flow | Where would you look for the next step, and is it where you expect? |
| Near-final details | Which statements, labels or links are wrong or ambiguous? |
Erin Casali's A List Apart article separates the stage of the work from the depth of the requested critique. You can ask about one difficult part of a broad early draft or check a larger assumption late in the process. "Near final" should not mean "please do not notice a real problem."
This is the revised outline, not a finished proposal. I need feedback on whether the evidence belongs before or after the recommendation. Please focus on that sequence for now; sentence edits can wait. If the recommendation itself has a factual problem, flag it.
Give the reviewer a small, usable brief
Include the current version, intended reader, review question, timing and place to reply. If those details already live in the linked task, summarize what matters rather than pasting the entire history.
Could you review the customer handoff note, version 3, for missing setup steps? The reader has an account but has not used this feature. Please leave comments beside the relevant step in the document. I plan to revise it at 2pm Mexico City time tomorrow. Is that review window workable for you?
That is a request, not an assumed assignment. Ask early enough to allow a real review and revision. Do not call a long document "a two-minute check" unless you have a basis for that estimate. If you only need one section checked, identify it and explain what is outside the request.
Check that the person can access the right version and is allowed to see it. Do not make a private document public just to solve an access problem. If the document keeps changing, identify the review version or checkpoint so comments can be understood later.
Atlassian recommends choosing reviewers whose roles and experience fit the goal. A colleague who knows the workflow can check missing steps; a subject-matter owner may need to verify a technical claim. Neither role automatically includes authority to approve a client release.
Show alternatives without turning the review into a vote
If you want to compare two options, give each the same context and evaluation question. Explain the tradeoff you are unsure about. Do not quietly ask for approval when you really need exploratory feedback.
Both opening versions describe the same service change. Version A gives the reason first; version B starts with the action customers need to take. Which makes that action easier to find, and what in the wording led you to that view? This is a clarity review, not release approval.
Intercom's account of its critique process recommends clearly separated alternatives and honest open questions. Nielsen Norman Group also distinguishes a standalone critique from a review used to gain approval. Names vary by organization, so state the purpose rather than assuming everyone interprets "review" the same way.
A reaction poll can collect preferences, but a 👍 is not a substitute for the required factual, legal or release sign-off. If approval is needed, ask the authorized person for that decision explicitly through the agreed process.
When comments conflict, return to the goal
Do not automatically follow the loudest comment or average incompatible suggestions. Ask what problem each reviewer is trying to solve. One may be optimizing for a new reader while another assumes an expert audience.
I have one suggestion to shorten the setup section and another to add more detail. The intended reader is using this for the first time. Which step would be unclear without the extra explanation? I will use that to revise the section and flag any unresolved policy question for its owner.
UNC recommends asking for clarification when a comment is unclear. Nielsen Norman Group suggests reconnecting critique to the work's objectives rather than personal taste. An unexpected comment may reveal a missing assumption, so do not dismiss it only because it was outside the original question.
Close with what changed, what did not and what still needs a decision. Casali describes iteration posts with the goal, work, changes and questions; Intercom describes recording concrete next steps after a critique. You do not need a fresh meeting for every comment, but people should be able to find the resulting version and remaining question.
If no one replies, use the agreed review window and our follow-up guide. Silence is not approval. If you need help solving a specific obstacle rather than reviewing a draft, use a focused help request instead.
Sources and limits
Reviewed October 29, 2026. This guide adapts writing-center guidance and design-critique practice to work chat. The decision aid and messages are our synthesis, not a validated universal framework. Follow your team's review, privacy and approval requirements.
- University of Illinois: stage and purpose of a feedback request
- UNC Writing Center: specific questions and clarification
- Nielsen Norman Group: critique scope, objectives and follow-up (2016)
- A List Apart: asynchronous feedback and iteration posts (2021)
- Atlassian: choose reviewers and define critique goals
- Intercom: its approach to options and next steps (2016)
The hero is conceptual AI artwork about looking at different parts of a draft, not a screenshot or a tested feedback method.