Asking for feedback is one of the most useful and courageous things you can do to advance in any field. Done well, it reveals blind spots and strengths you cannot see on your own. But the insight is only as good as the feedback it comes from, and the feedback is only as good as the request.
Asking is a skill. Most requests go unanswered for a simple reason: they ask for too much and promise too little. The request is vague, hoping to capture anything and everything. The giver has no idea whether their words stay anonymous or who will read them. And it quietly asks for more of their time than they have.
Asking for feedback at work works when you do three things: ask specific people about a specific thing, make it safe for them to be candid, and make it easy to answer in five minutes. Here's how to do each.
Ask specific people about a specific thing
It is much easier for someone to give feedback on something specific and distinct, like a presentation or a skill you are working on, than on something broad and general, like "my people management."
A concrete situation gives the feedback giver an anchor. They can replay what they saw and generate rich observations from it. It also makes the feedback safer to give: by narrowing the field, you are inviting them to comment on an aspect you chose, rather than asking them to judge you as a whole.
Good subjects for a request:
- A specific piece of work: a project you led, a presentation, a workshop, a client meeting.
- A skill you are deliberately practicing: running meetings, delegating, giving clear direction.
- A defined period: your first 90 days in a new role, the last quarter with a new team.
Then choose the people. Three to six is plenty. Pick people who actually saw you do the thing, and mix perspectives where you can: a peer, someone you manage, someone you report to, a stakeholder outside your team. Resist the pull to only ask people who like you. The most useful answers usually come from the person who was in the room and has no reason to flatter you.
Address each person directly, by first name, and tell them why you want their perspective in particular. "You sat through all three client reviews, so you saw the parts I'm unsure about" does more than any generic invitation. You are showing that you trust them to be honest and constructive, and people tend to rise to that.
Make it safe for them to be candid
Candid feedback is a gift that is hard to get. Three things raise the signal-to-noise ratio.
- Tell them who will see it and what it is for. Before anyone writes a word, they are silently asking: does my manager see this, does it affect anyone's review, could this come back to me? Answer those questions in the request itself. If you are asking several people at once, say whether their answers are anonymous and how that anonymity is protected. A tool like ZenFeedback does this by holding answers back until enough people have responded and by mixing responses so no single answer can be traced to a name. If you are asking by email, say plainly: "This is for my own development. It stays with me and never goes to my manager."
- Ask for candor explicitly. People default to polite. Give them permission to be direct: "I'd rather hear the uncomfortable thing now than find out in a year." Say why it matters to you and what you plan to do with it. A giver who knows their words will lead to something is far more willing to spend the effort.
- Ask about the future, not just the past. Questions about what went wrong put the giver in the position of a judge, which most people dislike. Questions about what you could do differently next time put them in the position of an adviser, which most people enjoy. This is the idea behind feedforward: the same observation, framed as a suggestion for what comes next. "What should I do more of in the next presentation?" gets richer answers than "What did I do badly?", and it is a lot easier to hear.
Questions about the past make the giver a judge. Questions about the future make them an adviser. Most people would much rather be the second.
Make it easy to answer in five minutes
People are far more likely to write quality feedback when they know how much time it will take. Say it in the request: "Three questions, about five minutes." Then honor it.
Three to five questions is the right number. More than that and answers get shorter, not longer. Here is a set you can copy and adapt:
- What did I do well on [the project / the presentation] that I should keep doing?
- What is one thing I could do differently next time that would make the biggest difference?
- Was there a moment where you thought "I wish [your name] had..."? What was it?
- What do you think I might not be seeing?
- If you had to give me one piece of advice for the next [quarter / similar situation], what would it be?
Give a deadline about a week out. Without one, the request sits in the inbox as a good intention. Send one gentle reminder two days before, and thank each person when they answer, even if you have not read it properly yet.
A request that puts all of this together:
Hi Anna,
I'm collecting feedback on how I ran the Q3 planning workshop, and I'd really value your view because you were in every session. It's three questions and should take about five minutes. This is for my own development only. It stays with me and doesn't go to anyone else. Please be as direct as you like, the uncomfortable version is the useful one. If you could reply by next Friday, that would be great.
Thanks,
Victor
What I learned running feedback programs
Having run 360 feedback programs at L'Oréal and Nike, and built management development tools alongside them, I believe asking for feedback is genuinely difficult for most managers. It takes courage to ask and discipline to follow through.
Three patterns showed up again and again.
The first is that the quality of feedback tracks the quality of the request almost exactly. The same group of people would give thin, careful answers to a vague form and rich, specific ones to a well-framed question a month later.
The second is that candor disappears the moment feedback is connected to evaluation. When people suspect their words might feed into a rating or a pay decision, they write for the record rather than for the person. The most honest feedback I ever saw was collected off the record, for development only, and everyone involved knew it.
The third is that people like to be asked. Giving feedback is sharing an opinion, and most of us enjoy being asked for ours, as long as we are asked directly, understand why, and feel at ease about who will see it. The best requesters were not the most senior people. They were the ones who were genuinely interested in getting better, and it showed.
Those three patterns are why I built ZenFeedback: a way to ask a few specific people a few specific questions, off the record, and turn the answers into a plan.
What to try this week
Pick one piece of work from the last month. Choose three people who saw it. Send each of them three questions, tell them it will take five minutes and that the answers stay with you, and give them a deadline of next Friday.
That is the whole exercise. If you want the request, the anonymity, and the follow-up handled for you, ZenFeedback does exactly this and is free to use.
Frequently asked questions
How many people should I ask for feedback?
Three to six. Fewer than three and you are hearing one opinion. More than six and the answers blur together, and the effort of chasing them outweighs the extra insight.
Should feedback be anonymous?
For candid feedback on your own development, yes, especially when asking more than one person. Anonymity removes the giver's fear of consequences. The trade-off is that you cannot follow up on a specific comment, so ask questions that stand on their own.
How often should I ask for feedback at work?
Tie it to events rather than a calendar. After a significant project, a presentation, or the first few months in a new role. Two or three well-framed requests a year will teach you more than a monthly survey nobody answers.