Feedback is the fastest way to improve at anything, and it is entirely in the giver's control whether they bother. People stop giving it to those who argue, deflate or go quiet. Handling the first ten seconds well is most of the skill.
The first ten seconds
Your instinct will be to explain. Resist it long enough to understand what is being said, because explaining first reads as defending, and the other person will decide it is not worth doing again.
- Listen to the end without interrupting, even when the first sentence is wrong.
- Say thank you, and mean the thanks for the effort rather than the content.
- Repeat it back in your own words: "So the reports are accurate but arriving too late to act on."
- Ask one question that makes it more specific.
- Say what you will do, or that you need to think about it. Both are complete answers.
There is a difference between "that is because the data arrives on Thursday" said to explain a system, and said to end the conversation. If you are giving context, say the point first: "You are right, and here is what causes it."
Ask for the specific, not the general
Most feedback arrives too vague to act on, not because the person is withholding, but because vague is what comes to mind first. A good question converts it into something you can change.
| You are told | Ask |
|---|---|
| Be more confident | "What did I do that read as unsure? Was it what I said or how I said it?" |
| Your writing is too long | "Which part would you have cut first?" |
| You need to be more proactive | "Can you give me an example of something you would have expected me to start on my own?" |
| Good job | "What is the one thing you would change if I did it again?" |
Separate the message from the delivery
Some feedback arrives badly: in public, at the wrong moment, or wrapped in someone else's bad day. You are allowed to think the delivery was poor and the content was right. Take the content now and, if it matters, raise the delivery separately and later, when it is a conversation about how you work together rather than a rebuttal.
It is also worth checking one thing before acting: is this one person's view, or have you heard it before from someone else? A single opinion is data, not a verdict. A pattern is a verdict.
Ask before you are given it
Waiting for feedback means only ever receiving it when something has gone wrong. Asking puts you in control of the timing and the subject, and people answer a narrow question far more honestly than an open one.
- "What is one thing I could have done better in that meeting?" beats "any feedback for me?"
- Ask soon after the thing, while the detail is still fresh.
- Ask people who see different sides of your work, not only your manager.
- When you act on what they said, tell them. It is the single strongest reason for someone to tell you the truth again.
Keep a record
Write feedback down the same day, in the person's own words, and revisit the list every couple of months. Patterns show up in writing that are invisible in the moment, and the ones you have already fixed are worth seeing too.
Key takeaways
- Listen fully, thank, repeat it back, then ask one specific question.
- Convert vague feedback into something changeable before you act on it.
- Take a right message even when the delivery was wrong.
- Ask narrow questions early, and tell people when you acted on the answer.
Want to practise this with people?
Udaan 90 runs Soft Skills and Public Speaking tracks, so you build these in front of a cohort rather than alone.
See Udaan 90