How do you ask for feedback without sounding needy?

Ask about a specific, recent piece of work and ask a narrow question, such as one thing to keep and one thing to change. A focused request sounds like someone who wants to improve a piece of work. A vague request for reassurance is what sounds needy, and it usually gets a vague answer.

Who should I ask for feedback besides my manager?

Anyone who saw the work closely: a colleague on the same project, a client contact, someone from another team who used your output, or a mentor who watched you present. Different people see different parts of your work, and a manager often sees only the result.

What is the SBI feedback model?

SBI is a practice framework from the Center for Creative Leadership: describe the Situation, the observed Behavior, and its Impact. It keeps feedback specific and away from judgments about character. You can use it to give feedback and also to shape your request, by asking about one situation and its impact.

What should I do with feedback I disagree with?

Thank the person, ask one clarifying question such as an example of when they saw it, and do not argue in the moment. Then take a day before deciding what to do. Feedback can be partly right, and checking it with one other person who saw the same work helps you tell which part to act on.

How often should I ask for feedback?

Often enough that it becomes routine, for example after each project, presentation or important meeting. Small, regular requests are easier for both sides than a rare big conversation, and they give you a running picture rather than a verdict once a year.

How to Ask for Feedback and Get Useful Answers

Asking for feedback means actively requesting someone’s view on a specific piece of your work.

You ask at a moment and in a form that lets them give a useful answer.

Many people wait for feedback to arrive.

When it does, it often comes late, vague, or bundled into a yearly review. Asking well changes all three.

This guide is for mentees and employees who want better information about how their work lands.

It covers:

why asking matters
how to phrase a request that gets a real answer
the SBI framework
worked examples for three different situations
how to handle what you hear
how to use all of this with your mentor

Why ask for feedback instead of waiting for it?

Susan Ashford and Larry Cummings argued in 1983 that feedback is a resource people can actively seek.

It is not only something that is given to them.

That shifted attention from the person giving feedback to the person who wants it.

Later work by Ashford and J. Stewart Black looked at people starting new jobs.

It found that newcomers use several proactive tactics to settle in.

These include seeking information and feedback, building relationships and negotiating changes to their job.

In practice, waiting has three costs:

It is slow. By the time a formal review arrives, the work it refers to is months old.
It is vague. Feedback given unprompted tends to be general: “good job”, “a bit more visibility”.
It is skewed. You tend to hear about problems once they are big enough for someone to mention. You rarely hear about strengths.

Asking fixes the timing and gives you control over the question.

How do you ask for feedback so you get a useful answer?

A good request has four parts.

One piece of work. Name a specific, recent thing: “Tuesday’s client call”, “the budget section of the proposal”, “how I ran the team meeting on Monday”. Recent means the other person still remembers it.
A narrow question. “Any feedback?” invites “you are doing fine”. Better: “What is one thing I should keep doing and one thing I should change?” Or: “What would have made that section easier for the finance team to approve?”
The right moment. Ask when the person has a few minutes and the work is fresh. Avoid the corridor between meetings, and do not wait three weeks. If you want a considered answer, tell them the question in advance.
Visible use. Act on something you hear and let the person know. People give better feedback to someone who clearly uses it.

A complete request might read:

“Could I have ten minutes after the steering meeting tomorrow? I would like your view on how I presented the delay: one thing that worked and one thing I should do differently next time.”

What is SBI, and how does it help?

SBI is a practice framework from the Center for Creative Leadership.

It is described in Weitzel’s Feedback That Works. It structures feedback in three parts:

Situation: when and where it happened. “In yesterday’s planning meeting…”
Behavior: what the person observably did, without interpretation. “…you moved to the next item before the design team had answered…”
Impact: the effect it had. “…and they raised the same concern again by email afterward.”

SBI is usually taught for giving feedback, but it is equally useful for asking.

You can ask about a situation and its impact:

“In the planning meeting, how did it land when I pushed to move on?”

You can also use it to translate vague feedback you receive into something you can act on:

“When you say I could be more visible, can you give me a situation where that would have made a difference?”

What does asking for feedback look like in practice?

Three illustrative situations, composites rather than real people.

Each has a weak request, a better one, and what to do next.

A new team lead after her first all-hands presentation.

Weak request: “How did I do?”
Better: to two people who were there: “I am working on presenting to the whole department. What is one moment where you were with me, and one where you drifted?”
Why it works: it is specific, and it asks for a strength and a gap. Asking two people helps her separate a pattern from one person’s taste.
Next step: pick one change for the next presentation. Tell one of the two people what she is trying.

A data analyst whose reports seem to go unread.

Weak request: “Is the weekly report useful?” The answer will be “yes, thanks”.
Better: to the person who uses it most: “When you open the weekly report, what do you look at first, and what do you skip?”
Why it works: it asks about behavior rather than opinion, which is easier to answer honestly.
Next step: cut what nobody reads, move the most-used figure to the top, and ask again in a month.

A program coordinator at a nonprofit who wants more responsibility.

Weak request: “Do you think I am ready for more?”
Better: to her director: “I would like to lead the volunteer recruitment next spring. What would you need to see from me between now and then to feel confident about that?”
Why it works: it turns a judgment into a list of things she can show. It signals the ambition without demanding an answer on the spot.
Next step: write down what the director said and agree when they will check in. Bring the list to her mentor.

How should you handle the feedback you get?

Asking is half the skill; receiving is the other half.

Douglas Stone and Sheila Heen’s Thanks for the Feedback is a practice book.

It focuses on the receiver of feedback rather than the giver.

The habits below are practical starting points, not a summary of the book.

Listen to the end. Do not explain or defend while the person is still talking.
Ask for one example. “Can you give me a moment where you saw that?” turns a general comment into something specific.
Thank them, then wait. Decide what to do after a day, not in the conversation.
Check it. If you are not sure the feedback is right, ask one other person who saw the same work.
Act on something visible. Even a small change shows the person that asking you was worth it.

Feedback you disagree with can still be useful.

It tells you how your work looked to someone, even if you do not accept their explanation for it.

How do you use this with your mentor?

A mentor is useful for feedback in two ways.

They are a source of feedback on what they see. They are also a partner for preparing requests to other people.

Before you ask your manager or a colleague, draft the request and test it with your mentor. Ask whether it sounds specific and whether the timing works. Ask how they would react if they received it. The guide on how to prepare for a mentoring meeting covers how to bring this kind of material.
Rehearse. Ask your mentor to play the other person, including the version who gives a vague or defensive answer.
Debrief. Bring back what was said, as close to the person’s words as you can. Decide together what to act on.
Ask your mentor directly. “What have you noticed about how I describe my own work?” is a good question for any mentoring meeting. The guide to questions to ask a mentor has more.

If your program goal is about growth in your current role, a feedback routine is often the most practical first step.

The guide on setting goals with your mentor explains how to link small steps like this to the goal you set.

Sources

Ashford, S.J., & Cummings, L.L. (1983). Feedback as an individual resource: Personal strategies of creating information. Organizational Behavior and Human Performance, 32(3), 370-398. https://doi.org/10.1016/0030-5073(83)90156-3
Ashford, S.J., & Black, J.S. (1996). Proactivity during organizational entry: The role of desire for control. Journal of Applied Psychology, 81(2), 199-214. https://doi.org/10.1037/0021-9010.81.2.199
Weitzel, S.R. (2000). Feedback That Works: How to Build and Deliver Your Message. Center for Creative Leadership. Practice framework (SBI).
Stone, D., & Heen, S. (2014). Thanks for the Feedback: The Science and Art of Receiving Feedback Well. Viking. Practice book.