To ask for feedback at work, show a specific piece of work, explain what you are trying to improve and ask a question the other person can answer. “What should I change in this introduction so the main point is clearer?” gives a colleague a more useful task than “Was it good?”
You do not have to sound completely confident before asking. A clear, proportionate request lets you get information while respecting the other person’s time. This guide includes scripts for drafts, meetings and vague performance comments, plus a journal template for deciding what to do with the answer.
Choose the work and the question
Start with a small, visible sample: a paragraph, a presentation opening, a recent meeting contribution or a finished task. Then identify the dimension you want to improve: clarity, completeness, timing or suitability for the audience.
A request becomes easier to answer when the reviewer knows the intended result. “This email needs to tell the client what happens next” is useful context. “Please review my communication” is too broad for a quick response.
A four-part feedback request
- Context: what the work is meant to do.
- Sample: the specific work or moment you want reviewed.
- Question: one improvement you want advice on.
- Scope: the time, deadline or amount of input you are requesting.
For example: “I’m preparing a two-minute update for Friday’s meeting. Could you look at the opening paragraph and suggest one change that would make the main point clearer? A few comments by Thursday afternoon would help, if you have time.”
This asks for a useful action without requiring a judgment about your entire ability. If speaking in the meeting is also difficult, our meeting contribution scripts can help you prepare the actual contribution.
Feedback request scripts you can adapt
On a small screen, scroll the table sideways to see every column.
| Situation | Specific request |
|---|---|
| A draft email | “Is the next step clear in the final paragraph? What would you change before I send it?” |
| A presentation | “Which part of the opening needs more context for this audience?” |
| After a meeting | “Did my update include the information you needed? What should I add or shorten next time?” |
| A new task | “Could you point to one part that meets the expected standard and one part I should revise?” |
| A performance conversation | “When you say ‘take more ownership,’ what action would you like to see in the next project?” |
| A busy colleague | “Would you have time for one question about this paragraph, or is there someone else better placed to review it?” |
Adapt the tone to your workplace. A casual team may prefer a short spoken question; a formal process may need a written request and an agreed review date.
Ask for advice about the next attempt
Sometimes “What advice would you give me for the next version?” produces more usable input than a general request for feedback. Research by Blunden and colleagues on eliciting advice rather than feedback found that advice requests can improve developmental input. That does not mean the word “feedback” is always wrong or that one wording guarantees a helpful answer.
The practical distinction is direction. A broad verdict looks backward: “Was my presentation good?” A developmental question looks at the next attempt: “What should I change to explain the recommendation more clearly?”
Turn vague comments into observable actions
If the answer is “be more confident,” ask for a concrete example: “What would that look like in the next meeting?” If the answer is “communicate better,” ask which information was missing or where the message became unclear.
Use these follow-ups without turning the conversation into an interrogation:
- “Could you show me one example?”
- “Which part would you change first?”
- “What would a satisfactory version include?”
- “Is this about the content, the timing or the way I presented it?”
- “Let me check I understood: you want a recommendation before the background detail?”
A neutral summary lets the reviewer correct a misunderstanding. It also gives you an action you can write down rather than a label you must carry around.
Use a feedback-to-action journal
Work or situation:
Question I asked:
Comment received, as accurately as I can record it:
Concrete example given:
What I understand the requested change to be:
What I need to clarify:
One revision I will try:
How I will check whether it helped:
Keep sensitive work information out of a personal journal when workplace rules require it. A short task description may be enough. The log is for organising your learning, not secretly recording colleagues.
Worked example: an unclear project update
In this fictional example, a colleague says an update “needs to be sharper.” The writer asks, “Which information would you like first?” The colleague explains that the recommendation appears after three paragraphs of background.
The writer records the concrete change: move the recommendation to the opening, then include the two facts supporting it. They revise one update and ask whether the next step is now clear. The useful lesson is about the structure of this kind of message, not “I am a bad communicator.”
For sorting comments before responding, see our guide to handling criticism. For practising the revision itself, our small practice guide explains how to connect an attempt with specific learning.
When the feedback is conflicting or unhelpful
Two reviewers may have different goals. Ask who the audience is and which standard the work needs to meet. A sales colleague and a technical reviewer can reasonably focus on different details. Record that difference rather than trying to satisfy every preference simultaneously.
If a comment is personal or degrading, it may not contain usable developmental advice. You do not need to translate abuse into a lesson. Consider appropriate workplace support and documentation. A journaling exercise cannot fix an unsafe or discriminatory environment.
Also notice when you are repeatedly asking for approval after the work already meets the agreed standard. Our external validation guide helps distinguish useful information from another round of reassurance.
Common questions
How often should I ask?
Ask at useful points: early enough to revise a draft, after a meaningful attempt or during an agreed review. Repeated requests about the same unchanged work can use time without producing new information.
What if nobody replies?
Send one brief follow-up if appropriate, clarify the deadline and consider another suitable reviewer. Silence is not a reliable judgment of your work; availability and role may be the issue.
Do I have to accept every suggestion?
No. Understand the request, check it against the work’s purpose and explain your reasoning when needed. Managerial requirements and optional peer preferences may carry different weight.
Ask one question you can act on
Choose one piece of work and one improvement question. Give enough context, request a manageable amount of input and record a next step. Confidence can grow alongside the practice of asking clearly; it does not have to arrive first.
Keep the follow-up small: add one observation and one adjustment to your weekly journal review, rather than collecting comments you never use.
Research reference: Blunden and colleagues, Eliciting advice instead of feedback improves developmental input. The scripts and journal log are editorial applications, not quotations from the study.