By the end, you should be able to
- Ask a reviewer a specific question tied to a purpose.
- Separate observable effects from judgments and preferences.
- Explain a revision and its remaining limitations honestly.
Give the reviewer a useful job
A request for “any feedback” makes the reviewer decide what you are trying to achieve and where to focus. Offer the purpose, audience, stage of work, and the question you need answered. For example: “This is a first draft of instructions for new volunteers. Please try steps one to three and tell me where you need information that is missing.” A small, concrete request is easier to respond to than a demand for a complete evaluation.
Choose a reviewer whose perspective fits the question. A newcomer can reveal confusing assumptions; an experienced organizer can check whether the instructions match the actual process. Neither person automatically speaks for every audience. Explain how much time the review should take and make it easy to decline. If you need language or accessibility feedback, ask someone able to assess that dimension instead of assuming a general review covers it.
Ask for a moment and its effect
Useful feedback often identifies a situation, something observable, and its effect. The Center for Creative Leadership describes these elements in its Situation-Behavior-Impact approach. You can adapt the structure to a draft: where was the reader, what did the text do, and what happened for the reader? Keep this a practical conversation aid rather than treating a named framework as a guarantee that every conversation will go well.
Compare “This is unprofessional” with “In the opening paragraph, three unfamiliar abbreviations made me stop to search for definitions.” The second comment points to something you can investigate. If feedback is vague, ask for one example. Also ask what worked and why, so you preserve useful choices. A reviewer may prefer a different color without finding the page harder to use; preference and task difficulty deserve separate treatment.
Listen, clarify, and evaluate
Let the reviewer finish before explaining your intention. Restate the observation in your own words and check that you understood it. “You could find the date, but you could not tell whether registration was required” is a useful clarification. Asking how the person reached that interpretation can reveal a missing sentence, a misleading heading, or a mismatch between the audience and your assumptions.
You do not have to accept every suggestion. The reviewer may accurately describe a problem while proposing a solution that conflicts with another requirement. Keep the observed problem and consider alternatives. When two reviewers disagree, inspect their tasks and backgrounds before averaging their opinions. Different needs may call for separate explanations. If a remark is personal or disrespectful, redirect toward the work or end the exchange; useful evidence does not require accepting mistreatment.
Revise and report what changed
Choose one or two changes that address the purpose of the work. Keep a short decision record: the observation, the change, and the reason. If you decline a suggestion, record the constraint behind that choice. Then retest the part you changed with an appropriate reader or task. A revision is a hypothesis about improvement until you see whether it resolves the original difficulty.
Communicate results with the same care you use for the work itself. “Two readers found the registration requirement after the revision” is more precise than “Everyone understands it now.” Distinguish completed changes, observations, and unresolved issues. When presenting a portfolio project, label fictional data, practice tasks, AI assistance where relevant, and your own contribution clearly. Honest boundaries help another person understand what your evidence actually demonstrates.
Fictional case: feedback that changes the draft
Luis shares a community workshop page and receives the comment “Make it more exciting.” He asks which part failed to hold the reviewer’s attention and what the reviewer expected to learn there. The reviewer explains that the opening describes the organizer but never says what a participant will do. Luis rewrites the opening to describe the activity and adds a sample task.
A second reader can now explain the activity but cannot find the equipment list. Luis moves that list beside the registration details. In his project log, he records both observations and the two revisions. He does not claim that the page will increase attendance, because he has not measured attendance or compared outcomes under conditions that could support that claim.
Request and apply one piece of feedback
- Choose a small draft and name its audience, purpose, and current stage.
- Write a review request with one task and two focused questions.
- Ask for a specific example and restate what you heard before deciding.
- Make one revision and document the evidence, decision, and next check.
Sources and context
- Center for Creative Leadership: Situation-Behavior-Impact and intentPrimary description of the organization’s feedback framework. The lesson adapts its structure to draft review without claiming guaranteed outcomes.
AI-assisted educational writing, checked against the linked sources. Examples and exercises are original teaching material. See our editorial standards.