How to Ask Your Manager for Feedback You Can Act On

To get feedback you can act on, stop asking your manager for feedback in general and ask about one skill and one recent piece of work, in a question small enough to answer in thirty seconds. “Any feedback for me?” almost always earns “You're doing great,” because it asks a busy person to review your whole job on the spot. This guide gives you eight narrow questions, a plan for when to ask them, a way to decode vague comments, a three-step reply for hearing criticism without bristling, and a simple log that turns one comment into a 30-day experiment. It is written for early- and mid-career employees who want to grow but hear little from their manager. If you are on a formal performance-improvement plan or in a dispute with your employer, coaching questions are the wrong tool: read your HR policy and consider employment advice instead.

Why “Any feedback for me?” gets you nothing

Open-ended requests fail for three reasons, and none of them is that your manager doesn't care. First, the question has no anchor: your manager has to recall weeks of your work, sort it, and pick something, all while thinking about their own deadlines. The easiest answer is a compliment.

Second, criticism carries social risk. Telling someone what they did wrong, unprompted and without a clear invitation, can feel like starting a conflict. A vague question doesn't signal that you genuinely want the uncomfortable part.

Third, the question is usually asked at the wrong moment, at the tail end of a one-to-one when there are two minutes left, or months after the work it's about. Specific questions fix all three: they point at a concrete moment, they give permission to criticize, and they can be answered quickly.

Pick one skill and one recent piece of work

Before you ask anything, choose a single skill you want to improve and a single piece of work from the past week or two that shows it. The pairing matters. “Presenting” alone is too broad; “Tuesday's budget presentation” alone invites comments on the numbers rather than your delivery. Together they give your manager a clear target: “I'm working on presenting more concisely. How did Tuesday's budget update land?”

Good skills to pick are ones your manager actually sees: written reports, meeting facilitation, prioritization, handling client emails, estimating timelines, giving updates. Skip skills they never observe, such as how you organize your own files. Choose work that is recent enough to remember clearly, ideally within five working days.

Say it up front, too. Telling your manager “I'm focusing on X for the next month” makes them a little more likely to notice X, which gives you better answers later.

Eight questions that get specific answers

Each of these is narrow, names a real piece of work, and asks for one thing rather than a list. Swap in your own project names and days.

1. “What's one thing I could have done differently in Tuesday's presentation?” “One thing” lowers the stakes and forces a choice.
2. “What would make my reports easier for you to use?” This frames criticism as helping them, which most managers find easier to give.
3. “Was there a point in the client call where you'd have handled it differently?” It asks for a moment, not a verdict.
4. “On a scale of 1 to 10, how ready was the draft I sent on Friday? What would have made it a 10?” Managers rarely answer 10, and the gap between their number and 10 is where the real answer sits.
5. “What should I start doing in the weekly planning meeting that I'm not doing now?” “Start” questions surface missing behaviors that “what went wrong” misses.
6. “If you'd written that proposal, what would you have cut?” It invites a concrete edit rather than a judgment.
7. “What's something I do that slows you down, even slightly?” “Even slightly” gives permission to mention small irritations that never otherwise get said.
8. “What's the next skill you'd want to see from someone in my role?” This is the growth question; save it for a calm one-to-one rather than right after a deadline.

Ask one question per conversation, two at most. A list of eight fired off in a row feels like an interrogation and produces shorter answers.

When to ask: right after the work or in your one-to-one

Timing changes what you hear. Use both moments, for different kinds of question.

Within a day of the work

Questions about a specific deliverable (questions 1, 3, 4 and 6) work best within 24 hours, while your manager still remembers details. Keep it light and quick: a message such as “Quick one: anything you'd change about how I ran that call?” or a sentence as you walk out of the meeting. Don't ask when they are visibly rushed or right after something went badly in front of others; give it a few hours.

In a scheduled one-to-one

Broader questions about habits and growth (questions 2, 5, 7 and 8) need more thought, so put them in your regular one-to-one. Better still, send the question a day ahead: “Tomorrow I'd like five minutes on what would make my weekly reports more useful.” That gives your manager time to think, which turns a reflexive “they're fine” into an actual observation.

A workable rhythm: one quick post-project question every week or two, and one growth question in a one-to-one roughly once a month.

Decoding vague comments with the SBI model

Even with good questions, you will sometimes hear “Be more strategic” or “Your emails could be tighter.” The Situation-Behavior-Impact (SBI) model, a framework widely used in management training, gives you a structure for turning those comments into something concrete. It breaks feedback into three parts:

• Situation: when and where it happened.
• Behavior: what you actually did or said, something a camera could record.
• Impact: what effect it had on the listener, the group or the result.

Most vague comments contain only an impact or a label. Your job is to ask for the missing parts. If your manager says “Be more strategic,” ask: “Can you think of a recent meeting where I could have been more strategic? What did I do there?” You might learn that in Thursday's planning session (situation), you spent ten minutes on formatting details (behavior), and the group ran out of time to discuss priorities (impact). That is something you can change; “be more strategic” is not.

Listening without defending: a three-step reply

The way you react to the first piece of criticism decides whether you get a second. If you explain, justify or correct, your manager learns that feedback costs them effort and goodwill. Use this three-step reply instead, even when you disagree.

1. Thank them. Keep it short and plain: “Thanks, that's useful.” You are thanking them for the honesty, not agreeing with every word.
2. Ask one clarifying question. Just one, aimed at the missing piece of SBI: “Which part of the report was hardest to use?” or “What would good look like there?”
3. Summarize what you'll try. “So for the next two reports I'll put the recommendation in the first paragraph and move the detail to an appendix.” This shows you heard them and creates something to check later.

If you feel defensive, that is normal; the goal is not to stop the feeling but to delay the response. Writing the comment down while they talk gives your hands something to do and slows you down. If you genuinely think the feedback rests on a misunderstanding, raise it a day later, calmly and with specifics, not in the moment. Practicing this kind of composed, specific reply is part of broader communication skills that build career confidence.

Preference or performance? How to weigh a comment

Not every comment deserves the same weight. Some describe how well the work does its job; others describe how your manager personally likes things done. Both are worth knowing, but they call for different responses. Signs that a comment is more preference than performance:

• It can't be tied to any impact. Ask “What happened because of that?” If the answer is “Nothing, I just prefer it,” it's a preference.
• It contradicts what other reviewers have asked for, such as a manager who wants bullet points when the client asked for prose.
• It's about style (fonts, tone, word choice) rather than accuracy, clarity, timing or results.
• It changes from week to week.

Preferences from your direct manager are often still worth following for work they receive, because making their job easier is part of your job. Just don't treat them as a universal standard or rebuild your whole approach around them. Performance comments, especially ones you hear from more than one person, deserve priority in your next experiment.

When your manager rarely gives input: peers and clients

If your manager stays vague no matter how you ask, widen the pool. The same rules apply: one skill, one piece of work, one narrow question.

• Peers see your day-to-day work more often than your manager does. Ask someone who worked alongside you on a specific task: “When I handed over the dataset last week, was anything missing that cost you time?”
• Internal clients (the departments that use your work) can tell you about usefulness: “Is there anything in the monthly summary you skip or never use?”
• External clients need lighter questions, ideally at the close of a project and with your manager's blessing: “Is there one thing that would have made this project easier on your side?”
• A colleague one level above you can answer question 8 about the next skill to build, often more freely than your own manager.

Feedback from several sources is also a good check on preference. If three people independently mention slow replies, that's a pattern; if one person mentions it, note it and watch for it.

Turning one comment into a 30-day experiment

Feedback changes nothing until you test it. Pick one comment, the most specific performance comment you've heard, and turn it into a 30-day experiment with a clear behavior, a way to tell if it worked, and a date to check in.

1. Write the behavior as an action. Not “be more concise” but “keep every status update under 150 words with the decision needed in the first line.”
2. Decide what success would look like. Fewer follow-up questions, a meeting that ends on time, a client who stops asking for clarification.
3. Tell your manager what you're trying. One sentence is enough: “Based on your comment, I'm testing shorter updates this month.”
4. Book the check-in. Put a date about 30 days out in your one-to-one agenda and ask: “I've been doing shorter updates for a month. Have you noticed a difference, and is there anything you'd adjust?”

The check-in is what makes the loop work. It shows your manager their comment had an effect, which makes them more likely to give you another one, and it gives you a second, sharper round of feedback on the same skill. Working on one change at a time, and checking it before moving on, follows the same logic as other self-improvement strategies that stick.

A one-page feedback log

Keep a simple log in a notebook, spreadsheet or document. Four columns are enough, and one page will usually cover a couple of months. The rows below are an illustrative example of how entries might look.

Review the log before each one-to-one. Over a few months it shows which comments led to real change, which skills keep coming up, and what to raise at your next performance review. It also gives you concrete examples when you ask for a stretch assignment or a promotion, because you can point to the comment, what you did about it, and what happened next.