All posts
November 15, 2026
Figures checked November 2026

Ask for Feedback That Helps — Professional Development #004

Vague feedback is useless. Not because people are unkind — because the ask was vague. What do you think gets politeness. A specific question about a specific piece of work gets something you can use. This guide shows how to ask for feedback that helps: pick one piece of work, ask one scripted question, write the answer down word for word, apply one change, and thank the person in writing. Five steps. One conversation.

Two empty speech bubbles above a wooden table with an open blank notebook and a pencil, two empty chairs facing each other, and a small potted plant.
Two chairs, two empty bubbles, one notebook. The conversation starts with the ask.

Difficulty: Beginner · Time: 20 minutes to prepare and ask, plus the conversation itself · Equipment: One piece of finished work, a notebook, and a pen.

Disclosure: some links on this page are affiliate links. As an Amazon Associate, Changenaire earns from qualifying purchases made through links on this page, at no extra cost to you.

Key takeaways

  • Pick one piece of work and one person whose view you trust.
  • Ask the script: one thing to keep doing, one thing to change, in that specific task.
  • Write the answer down exactly as said, without arguing.
  • Apply one change from the answer to the next version of the work.
  • Thank them in writing and tell them what you changed.

No promises here. A good ask does not make the answer easy to hear, and one change does not remake the work overnight. The steps only make the conversation useful — what you do with the answer is the part no guide can do for you.

Who this is for: anyone working alone who never hears how the work lands — owners, freelancers, and people whose only reviewer is the customer who never comes back. It also fits anyone inside a team who only gets feedback once a year, in a review. Who should skip it: anyone already asking for feedback on every piece of work and using what they hear. You are doing this guide already.

Silence feels safe. No news is good news — until you start guessing what the silence means, and the guesses run worse than anything anyone would have said. Asking beats waiting, and asking well beats asking vaguely. This is the fourth piece in the Professional Development series. It follows Time-Block Your Work Week — guarded hours produce the work; this piece gets eyes on it — and it leads into Have the Hard Conversation, for the day the feedback points at a conversation you have been putting off.

Go deeper (affiliate link — we may earn a commission): the script below is free and it is enough to start. If receiving feedback is the hard part — the sting, the defensiveness, the urge to explain — Thanks for the Feedback by Douglas Stone & Sheila Heen is the book on taking feedback well: how to hear what is being said even when it is said badly. Ask first, read second — the conversation comes before the book.

Pick one piece of work and one person whose view you trust

Pick one piece of finished work — the proposal sent last week, the product page, the pitch deck, the report — and one person whose view you trust. The person needs two qualities: they saw the work, and they will tell you the truth about it. A kind friend who never criticizes is the wrong pick. So is a stranger who never saw the work. One piece, one person.

Asking beats waiting. Harvard Business Review's look at what employees assume when they get no feedback describes the cost of silence: people fill it with their own assumptions, usually worse than the truth (checked November 2026). The ask replaces the guessing with an answer — usually a kinder one than the silence suggested.

Ask with a script: one thing to keep, one thing to change

Ask with a script, word for word: What is one thing I should keep doing, and one thing I should change, in [the specific task]? Fill in the task — in the pricing section of the proposal, in the opening of the pitch. The script works because it is small: one keep, one change, one task. It gives the other person a shape to answer in, and it keeps the answer about the work, not about you.

Specific and behavior-based beats general and personal. Harvard Business Review's guidance on effective positive feedback makes the same point: name the behavior, not the person (checked November 2026). If you want a shape for framing the question, the SBI model — Situation, Behavior, Impact — comes from the Center for Creative Leadership, and this explainer walks through the model with examples (checked November 2026).

Write down exactly what they say, word for word, without arguing

Write down exactly what they say, word for word, without arguing. Notebook open, pen moving, mouth mostly shut. Do not explain why you did it that way. Do not correct their impression. Do not defend the work — the work is not on trial, and neither are you. Your only job in the room is to capture.

The arguing can happen later, alone, with the notes — and most of it will not survive the night. What survives is usually the one true sentence in the answer, the one you did not want to hear. That sentence is the reason you asked. If the answer points at a bigger conversation you have been avoiding, Have the Hard Conversation covers that one next.

Pick one change and apply it to the next version

Pick one change from the answer and apply it to the next version of the work. One change, not all of them. The next version of the proposal, the next pitch, the next page — with the one change visible in it. Feedback you never act on teaches people to stop giving it; feedback with one visible change teaches them the ask was serious.

If the answer held no change worth making, say so honestly to yourself and pick the smallest useful adjustment anyway — a clearer heading, a shorter opening. The habit is the point: ask, hear, change one thing. The size of the change matters less than the fact of it.

Thank them in writing and tell them what you changed

Thank them in writing and tell them what you changed. A short note, same day or next: Thank you for the feedback on the proposal. I changed the pricing section to show the costs up front. Two sentences. The thank-you closes the loop, and naming the change shows the answer landed somewhere real.

That note is what makes the next ask easy. People say yes a second time to someone who used the first answer. And the next ask gets easier still when the work itself is steady — the guarded hours in Time-Block Your Work Week are where the next version gets made.

At a glance

At a glance: Ask for Feedback That Helps
StepThe short version
Pick the work and the personOne finished piece, one person who saw it and tells the truth
Ask the scriptOne thing to keep, one thing to change, in the specific task
Write it downWord for word, no arguing, no defending — capture only
Apply one changeOne change, visible in the next version of the work
Thank them in writingShort note, same day or next, naming the change you made

Common mistakes

Asking what do you think. A vague ask gets polite noise, and polite noise wastes everyone's time. Fix: use the script — one keep, one change, one specific task.

Asking five people at once. Five answers pull in five directions and the work stalls. Fix: one person, one piece of work, one conversation.

Arguing with the answer in the room. Defending the work teaches people to soften the next answer until it says nothing. Fix: write it down, decide later, alone, with the notes.

Never closing the loop. An answer with no thank-you and no visible change is the last honest answer you get from that person. Fix: thank them in writing and name the change.

Can't do today?

Do the 2-minute version: pick the piece of work and the person, and send the script as a message instead of a meeting. What is one thing I should keep doing, and one thing I should change, in [the specific task]? That counts as the ask. The missed-day rule: an unanswered ask gets one gentle follow-up after three days, then you pick a different person — you do not chase. What counts as enough: one ask, one answer written down, one change applied.

Questions people ask

How do I ask for feedback from my boss?

Use the same script, aimed at one finished piece of work: What is one thing I should keep doing, and one thing I should change, in the specific task? Ask after the work is delivered, not before, and offer the written option — some people answer better in a message than in a meeting. The script keeps it about the behavior, which is what Harvard Business Review's guidance on effective feedback recommends: name the behavior, not the person (checked November 2026).

What if the feedback hurts to hear?

Write it down anyway, word for word, and decide what to do with it the next day. The sting is information about you, not about the feedback — a true sentence can sting and still be true. Sleep on the notes before you answer them, and pick one change even if the change is small.

What is the SBI feedback model?

SBI stands for Situation, Behavior, Impact: name the situation, describe the behavior, state the impact. The model comes from the Center for Creative Leadership, and this explainer walks through it with examples (checked November 2026). Use it to shape the question you ask, or to shape the feedback you give.

How often should I ask for feedback?

After each finished piece of work that matters — the proposal, the pitch, the page — not on a daily schedule and not once a year. The ask follows the work. If weeks pass with no finished work worth a second pair of eyes, the calendar, not the feedback habit, is the problem.

What comes next

One ask, one answer, one change. Some answers point further: a working relationship to repair, a conversation postponed too long. Have the Hard Conversation is the next piece in the series, and it starts where this one ends — with the sentence you have been putting off saying.

Sources

Every fact in this post was checked against the sources below in November 2026.

The Changenaire Newsletter

Subscribe for more free step-by-step how-to guides to help you get more things done to grow your business or project everyday.

Email required. Unsubscribe anytime.

Read our Privacy Policy.