Ask for feedback by showing a small piece of work, explaining its purpose and naming the decision you want help with. A focused request makes it easier for another person to respond usefully. Treat feedback as evidence to investigate and apply, not as a request for someone else to complete the task.
Choose the right reviewer for the question
A classmate can tell you whether an explanation is understandable, while a subject specialist may be needed to verify technical correctness. Someone outside the intended audience may notice different problems from a likely user. State which kind of response you need.
UNC’s office-hours guidance encourages preparing questions and reviewing attempted work. The same principle can help independent learners, although access to teachers or mentors is not automatically available. Respect the person’s time and the community’s rules. Do not assume that a public profile creates an obligation to review your entire project.
Provide context without overwhelming the reader
Include the goal, relevant constraints, your attempt and the specific uncertainty. Share only the material needed to examine it. Remove private data, passwords and restricted files. If the project is fictional, say so.
A request such as “Please review my dashboard” is broad. “Does this chart support my conclusion about the three fictional product categories?” gives the reviewer a task. Carnegie Mellon’s learning principles connect goal-directed practice with targeted feedback. Clear criteria help both people understand what a useful response would address.
Practice: a fictional chart-review request
Create a small chart from invented campus stationery sales. State that you want to compare net sales by product and that the dataset excludes costs. Ask a reviewer whether the labels and written conclusion match that purpose. Provide the underlying summary table so the numbers can be inspected.
Suppose the reviewer notes that your conclusion calls revenue “profit.” Correct the terminology, inspect related labels and explain the change. Then ask whether the revised statement is clearer if further review is available. Do not turn this informal exchange into a claim of professional financial validation or invent a reviewer’s credentials.
Respond through revision and checking
Separate factual corrections, interpretation questions and preferences. Verify a technical suggestion against an authoritative source or a small test when appropriate. Reviewers can be mistaken, and conflicting comments may reflect different goals.
Keep a brief change note explaining what you accepted, modified or postponed and why. If feedback remains vague, ask a focused follow-up rather than defending the work immediately. Early feedback can be especially useful because there is still time to revise. The important outcome is a better attempt and clearer reasoning, not simply collecting encouraging comments.
A practical decision checklist
| Check | Useful evidence | Decision rule |
|---|---|---|
| Purpose | The task and the intended audience or user. | The reviewer should know what the work is supposed to achieve. |
| Scope | A small excerpt, example or decision. | Make the request manageable and remove irrelevant material. |
| Question | A specific uncertainty linked to a criterion. | Ask for evidence or explanation rather than general approval. |
| Follow-through | A revision and a check of the result. | Use feedback to change the work instead of only saving the comment. |
- Prepare
Choose the output and identify the exact question that needs another perspective.
- Ask
Provide concise context, your attempt and appropriate access to the evidence.
- Interpret
Separate corrections, assumptions and preferences, checking technical claims where needed.
- Revise
Apply a reasoned change and inspect whether it resolves the original concern.
- Vague request
- Tell me whether my project is good.
- Focused request
- Check whether this fictional sales chart supports the written comparison and uses the correct terms.
- Useful response
- A reviewer identifies the revenue-versus-profit error, leading to a specific correction and recheck.
Common questions
Who should I ask when I have no mentor?
Look for an appropriate peer, course forum, teaching-support route or community that welcomes the type of question. Match the reviewer to the issue and respect its rules. A peer may help with clarity, while technical correctness may need authoritative documentation or a specialist. Do not expect one person to evaluate everything.
How much work should I send?
Send the smallest amount that lets the reviewer understand the question and inspect the evidence. Include context and relevant inputs, but avoid a large unexplained folder. A narrow request is easier to answer and more likely to produce actionable feedback than asking someone to explore an entire project without direction.
What if the feedback is only “looks good”?
Thank the reviewer and, if appropriate, ask one specific question about the criterion that remains uncertain. For example, ask whether the conclusion follows from the table or whether an instruction can be followed. General approval may be encouraging, but it does not necessarily verify accuracy or resolve your learning question.
Should I follow every suggestion?
No. Understand the reason and compare it with the task, evidence and constraints. Check technical claims where needed, and distinguish preferences from corrections. Explain significant decisions respectfully. The purpose is to improve your judgment and the work, not to treat every comment as an unquestionable instruction.
How do I handle conflicting feedback?
Identify whether the reviewers are using different goals, audiences or assumptions. Clarify the project criteria and test the disputed point where possible. You may need a specialist for a correctness question. Record the decision and its reasoning rather than choosing the comment that is easiest or most flattering.
Can I ask AI for feedback instead of a person?
It can generate questions or possible issues, but its judgments may be wrong or generic. Verify important claims and avoid sharing private material. Use it as one input, not a substitute for required expert review or actual user observation. A convincing explanation from a tool is not proof that the project is correct.
What should I do after receiving criticism?
Translate the comment into a specific issue, ask for clarification if needed and choose a manageable revision. Separate the quality of one output from a judgment about your ability. Keep the original version so you can explain what changed. A correction can become strong evidence of learning when the follow-through is visible.
How can I acknowledge a reviewer in my portfolio?
Ask permission before naming the person or quoting their comments. Describe the scope of the feedback accurately and avoid implying formal endorsement or comprehensive validation. You can explain that a peer review revealed a confusing label without inventing expertise, credentials or approval beyond what actually occurred.
A useful next step
Capture feedback decisions in a learning journal. For a manageable review target, use the practice-project scope guide.
Sources and references
- UNC: Using office hours effectively — Preparing specific questions and reviewing work can make instructor feedback more useful; access depends on the actual course.
- Carnegie Mellon: Learning principles — Prior knowledge, component skills, goal-directed practice, feedback and self-monitoring support instructional decisions; article exercises are original suggestions.
- Carnegie Mellon: Early course feedback — Feedback during learning allows adjustment before a course ends; article applies the principle without claiming a required institutional process.
Skills & Learning Desk
MP Job Hub’s organisational byline for sequenced practice, course evaluation and useful learning habits.
Skill roadmaps · Learning resources · Practice projects
View profile →Read our research process or request a correction.
