Eva360
feedback, communication

How to Ask Coworkers for Honest Feedback (Without Making It Weird)

Asking a coworker “hey, can you give me some honest feedback?” is one of those requests that sounds simple and lands like a pop quiz. The other person freezes, scans your face for what you actually want to hear, and says something safe: “Honestly? I think you’re doing great.” You both walk away having accomplished nothing, and now it’s a little awkward on top of that.

The problem usually isn’t that your colleagues have nothing to say. It’s that the way most of us ask makes honesty expensive for the other person. Fix the ask and you fix most of the problem.

Why “any feedback for me?” almost never works

Put yourself in your coworker’s seat. You’ve just been asked, live and unprompted, to critique someone you have to keep working with. Saying something critical carries real social risk. You might hurt them. You might be wrong. You might damage the relationship. And there’s nothing in it for you. The rational move is to say something pleasant and change the subject.

So the goal isn’t finding braver colleagues. It’s lowering the cost of honesty:

  • Make it specific. “What’s one thing I could do better in meetings?” is answerable. “Any feedback?” is a job interview question in reverse.
  • Make it asynchronous. People say more honest things in writing, with time to think, than on the spot with your face right there.
  • Make it about your growth, not their judgment. Frame the ask around something you’re working on, so answering feels like helping instead of criticizing.
  • When possible, make it anonymous. This is the big one, and we’ll come back to it.

Pick people who will actually tell you something

The instinct is to ask the colleagues you like most. Resist it. Your work friends have the strongest incentive to protect the relationship, and protecting the relationship often means protecting you from anything uncomfortable.

Better selection criteria:

  • People who see your work up close. Someone who was in the room when things went sideways, not just when the demo worked.
  • People with different vantage points. A peer, your manager, someone junior to you, and a former colleague will each see completely different things. The overlap between their answers is where the signal is.
  • At least one person with mild friction. Not someone you’re in open conflict with. But the colleague you occasionally clash with over priorities probably has the most useful observations about you. They’ve been thinking about your weak spots for free.
  • Former colleagues. People you no longer work with have almost nothing to lose by being straight with you. They’re consistently underused.

A mix of three to six people across those categories will tell you far more than ten close friends ever would. (Not coincidentally, that’s the range a structured 360 uses. More on that below.)

How to word the ask

A few principles, then a script you can steal.

Explain why you’re asking, briefly and honestly. People open up a lot more when the request comes with a reason. “I’m trying to get better at how I run projects” beats an unexplained request every time: it tells them what to aim at, and it signals you actually want the answer.

Ask for one thing, not a review. “What’s one thing I do that gets in my own way?” gives them permission to name a single flaw without feeling like they’re delivering a verdict on your whole career.

Give them an out and a runway. “No pressure, and no need to answer now” removes the on-the-spot panic that produces safe answers.

Here’s an example of a message that works, whether you’re inviting someone to a structured feedback tool or just asking directly:

Example message: “Hey Priya, I’m working on getting a clearer picture of how I come across at work, especially the stuff I can’t see myself. You’ve worked with me closely enough to have a real opinion, and I’d genuinely rather hear something uncomfortable than something polite. Would you be up for giving me some honest feedback? It’s a short set of questions, your answers stay anonymous, and blunt is better than kind here. Totally fine to say no.”

Look at what that message is doing. It explains why. It names the person’s specific qualification (“you’ve worked with me closely”). It explicitly licenses criticism (“blunt is better than kind”), and it offers an exit. Every one of those lowers the cost of saying yes, and of saying something real.

The two hardest asks: your manager and your direct reports

Asking your manager feels risky because you’re inviting scrutiny from the person who evaluates you. Two things help. First, frame it as initiative, not insecurity: “I want to work on my biggest development area before it shows up in a review. What would you say it is?” Managers generally read that as ambition. Second, ask outside review season, when the conversation carries no stakes.

Asking a direct report is harder in the other direction. The power gap means they have every reason to flatter you, and a face-to-face ask can feel like a loyalty test no matter how gently you phrase it. For reports especially, anonymity isn’t a nice-to-have. It’s the only condition under which most people will tell their boss something critical. If you can’t offer genuine anonymity, at minimum ask in writing, ask about behaviors rather than opinions of you (“what’s one thing about how I run our one-on-ones that you’d change?”), and, crucially, respond well to the first mildly critical thing they say. How you receive the first 10% of honesty determines whether you ever get the other 90%.

Make honesty structurally safe, not just verbally safe

You can promise “I won’t take it personally” all you want. People believe structures, not promises. This is the real argument for using an anonymous, aggregated process instead of a series of one-on-one conversations.

It’s also why we built Eva360 the way we did. It’s a self-serve 360 review you buy for yourself ($69, one-time), and your employer never sees the results, so nobody is feeding into a performance file. You invite 3–6 raters yourself: peers, your manager, direct reports, former colleagues. And the anonymity is enforced, not promised. Results only appear once at least three people have responded, answers are shown only in aggregated groups of three or more, and if a group (say, your direct reports) has fewer than three respondents, that group’s results are suppressed entirely. Your report can never point back at one person’s answers, and your raters know it. That knowledge is what unlocks the sentences they’d never say to your face.

What to do with what you hear

However you gather feedback, the follow-through matters more than the ask:

  • Say thank you and stop there. Don’t defend, explain, or contextualize, even once. Any pushback teaches people that honesty with you has a price.
  • Look for patterns, not verdicts. One person’s comment is a data point. The same theme from a peer, your manager, and a report is a finding.
  • Close the loop. A few weeks later, tell people one thing you’re doing differently. Nothing earns you future honesty like proof that the last round of honesty mattered.

Asking for feedback doesn’t have to be weird. It gets weird when the request is vague, public, and risky for the person answering. Make it specific, make it safe, make it clearly about your own growth, and you’ll find most colleagues were never unwilling to be honest with you. They were just waiting for a way to do it that didn’t cost them anything.

Curious what your own report would say?

Start my 360