Most people have been told to “ask for feedback” at some point. The advice sounds simple until you try it. Ask “How did I do?” and you may hear “Great, thanks” or “You could be more confident”. Neither answer tells you very much about what to repeat or what to change.
Useful feedback is specific enough to act on and relevant to something you are trying to improve. You can ask for it after a presentation, a piece of writing, a job interview practice session or an everyday conversation. The skill lies partly in your question, partly in how you listen and partly in what you do afterwards.
Decide what you want to improve before asking
Start with one behaviour or piece of work, not your whole personality. “I want to explain my main point more clearly in short presentations” is easier to review than “I want to become better at everything”. When the goal is specific, the other person can pay attention to something observable. You can then compare what you intended with what they experienced.
Write one sentence about the goal before the activity. For example: “By the end of this presentation, listeners should know the next three steps.” After the event, ask whether that happened and which part helped or confused them. Our guide to achievable goals offers a wider way to turn an intention into a practical target.
Ask the right person for the right kind of input
Someone who saw the work can describe what they noticed. A subject expert may spot a technical problem. A member of your intended audience can say whether they understood the message. These viewpoints are useful in different ways; a friend who wants to encourage you may not be able to judge a specialist skill, and an expert may not represent a first-time reader.
Choose one or two people whose perspective is genuinely relevant, rather than asking everybody. Tell them what you want reviewed and how long it should take. If the work is confidential, use only people who are authorised to see it. Asking someone for a quick reaction is a favour, so make the request easy to accept or decline.
Replace broad questions with focused ones
“Was it good?” tends to invite a polite verdict. Better questions ask about a particular part of the experience: “Where did the explanation become unclear?” “Which example helped most?” “What was the first thing you noticed?” “Was there a point when I spoke too quickly?” These questions point towards observations you can work with.
Avoid leading questions that suggest the answer you hope to hear, such as “You thought the introduction was strong, didn’t you?” Ask open questions first, then follow up with a concrete example. If someone says “The middle felt rushed”, ask “Which part should I slow down or explain differently?” That gives you a behaviour to test next time.
Make it safe to give a genuine answer
People are less likely to offer useful criticism if they expect an argument. Begin by saying why you are asking: “I’m practising shorter explanations and would value one thing that worked and one thing to improve.” Give permission for an honest answer without inviting personal attacks. Respect the person’s time and avoid asking for a long report when a five-minute conversation will do.
Your reaction matters. If you instantly defend every choice, the conversation can close. You do not have to agree with every comment, but you can acknowledge what was observed. Try “That is useful; can you point me to the part you mean?” instead of “No, that wasn’t what happened.”
Understand feedback about behaviour, not character
Actionable comments describe something a person could see or hear. “You showed the slide before explaining the key number” is much easier to use than “You are careless”. The first identifies an action; the second labels a person. When feedback arrives in vague language, ask for a specific moment or example rather than accepting a broad label.
The Center for Creative Leadership’s Situation–Behaviour–Impact model provides a useful structure: describe the situation, the observed behaviour and its impact. Though commonly taught to feedback givers, it also helps a recipient ask better follow-up questions.
Listen first; decide what to do later
When receiving a difficult comment, separate hearing from judging. Let the person finish, then summarise what you understood: “So the instructions were clear at first, but the example changed too quickly?” Ask if that is accurate. This does not mean surrendering your judgement; it means obtaining the information before evaluating it.
Pay attention to the conditions. A rushed meeting, poor sound or an unfamiliar topic may affect how someone experiences your work. These details can explain a problem without making the observation useless. Our active listening guide offers more practice in checking understanding during conversations.
Separate observation, interpretation and suggestion
A comment may combine several things: “I lost track at slide four, so I think you need more confidence and should use fewer charts.” The observation is that the listener lost track at slide four. The explanation (“you need more confidence”) is an interpretation. Using fewer charts is a proposed solution. Treat them as different kinds of information.
You can investigate the observation by reviewing slide four. You may discover that the chart title was unclear rather than your speaking style being at fault. This approach prevents you from turning one person’s opinion into a general truth about yourself. It also allows you to test the suggested change rather than applying it automatically.
Notice patterns without counting opinions as votes
If several people independently mention the same unclear instruction, it is worth attention. But the number of comments is not the only measure. An expert may notice a serious technical error that other reviewers miss, while a new reader may reveal that your language is hard for beginners. Consider each person’s viewpoint alongside the evidence.
Look for specific examples that repeat across situations. If feedback is inconsistent, test a revised version with a suitable audience. Do not chase praise or criticism as a score. Your goal is to understand whether the work is serving its purpose, not to collect the most positive reactions.
Turn comments into one small experiment
The most valuable part of feedback often begins after the conversation. Choose one change that you can make before the next attempt. If people found your introduction unclear, try beginning with the key point in one sentence. If instructions felt too long, test a three-step numbered version. Make the change concrete enough that you will know whether you tried it.
Do not attempt ten improvements at once. When everything changes, you cannot tell what helped. A small experiment gives you a clear next action and makes it easier to ask a second question later: “I moved the example before the theory. Was the explanation easier to follow this time?”
Set a simple follow-up date and measure progress
Write down the behaviour you are changing, when you will practise it and what you will look for. For example: “In Friday’s meeting, give the recommendation in the first minute. Afterward, ask two attendees whether the next action was clear.” The measure need not be a complicated score; a specific observation is often enough for an everyday skill.
The CIPD’s performance management guidance describes feedback and improvement as an ongoing process rather than a single yearly event. For personal learning, the same practical idea is useful: try something, learn from the response, adjust and revisit.
A worked example: improving a short presentation
Imagine you give a five-minute presentation to a study group. You want listeners to understand the recommendation. Instead of asking “Did you like it?”, ask: “What do you think I want the group to do next?” and “Which part made that decision easier or harder?” Suppose one person says the recommendation only became clear near the end.
Your next experiment could be to state the recommendation at the start and use the remaining minutes to explain why. In the following presentation, ask the same two questions. Record whether the audience can describe the action more accurately. This is a fictional example of a repeatable feedback loop, not a claim of measured improvement.
A worked example: improving written work
Suppose you are drafting a one-page instruction sheet for new colleagues. Ask a reader to follow it without your help, then note where they hesitate or ask for clarification. That observation is often more useful than “It’s well written”. Next ask what information they expected to find at the point of difficulty.
You might learn that step three assumes knowledge the reader does not have. Rewrite that step, try it with another authorised reader and check whether the same confusion appears. When the subject is technical, have a knowledgeable person verify that simplifying the wording did not make the instruction inaccurate.
Handle feedback you think is unfair
You can be respectful without accepting an unsupported judgement. Ask for the particular incident or example. If someone says “You’re always unprepared”, you might ask “Was there a meeting where the missing information caused a problem?” The goal is to identify a behaviour or context that can be examined, not to argue about the word “always”.
Feedback can also be biased, mistaken or delivered inappropriately. You are not required to tolerate personal insults. If the situation involves serious workplace concerns, use the relevant workplace support or complaints process. For ordinary disagreements, explain your perspective calmly and look for an objective way to assess the work.
Give useful feedback when somebody asks you
The same principles work in reverse. Start with what you actually observed, identify the context and explain the effect. Instead of “The design looks wrong”, say “On the mobile version, I could not find the contact button without scrolling past several sections.” That gives the creator a testable issue without pretending that your preference is universal.
Check what kind of response the person wants. They may need an error check, an audience reaction or ideas for improvement. Offer no more suggestions than they can reasonably act on. The CIPD’s evidence review of performance feedback notes that feedback can help or harm depending on how it is given, which is a good reason to keep the conversation fair, specific and two-way.
Keep a lightweight feedback record
Use a note with five headings: “What I wanted to improve”, “Who observed the work”, “Specific feedback”, “My next change” and “When I will review it”. Write brief facts rather than a diary of every feeling. The record lets you compare new attempts with older ones and makes it less likely that you forget a useful suggestion.
After a few attempts, review what has genuinely changed. Keep habits that work; drop changes that create other problems. Our critical-thinking guide can help you weigh evidence instead of treating every comment as a command.
Frequently asked questions
What is the best question to ask for feedback?
There is no single best question. Ask about a specific goal or moment, such as “Where did the explanation become unclear?” and follow up with a request for an example.
How do I ask for feedback without sounding insecure?
Describe the skill you are practising and the kind of observation you need. A focused request is a normal part of improving work, not a request for reassurance.
What should I do when feedback conflicts?
Check each person’s context and expertise. Look for specific observations, then test a change with the audience that matters for the task.
Do I have to act on every suggestion?
No. Consider the evidence and your goal. Choose a manageable change, test it and keep what genuinely improves the result.
How often should I ask for feedback?
Ask at meaningful points: after a draft, trial, presentation or completed task. Give yourself time to practise between requests rather than collecting comments continuously.
Make feedback worth asking for
A useful feedback habit is small and practical: define one goal, ask somebody who has seen the work, listen for specific examples and test one change. You do not need approval from everybody. You need enough information to make the next attempt clearer, more effective or more considerate of the people it is meant to serve.
Sources and further reading
Center for Creative Leadership: SBI feedback model; CIPD: performance feedback evidence review; CIPD: performance management factsheet; Center for Creative Leadership: intent and impact.
