How to Get Employees to Respond to Feedback Requests

You post the message. “I reworked our onboarding doc, would love your feedback before Friday.” Then you wait. One person reacts with a thumbs up. Nobody actually reads section three. By Monday you are quietly wondering whether the whole team is checked out.

Most leaders read that silence as apathy. From years of building a tool around this exact problem and talking to leaders, I can tell you that reading is almost always wrong, and acting on it makes things worse. The research backs it up.

What I have seen play out in practice lines up closely with the research. I went back through it to sharpen the picture: conversations with managers who have figured out how to get a response, research from Harvard Business School on why people withhold feedback even when it costs them nothing, and a piece from HR practitioner Mikki Forbes on why feedback dries up over time. Together they explain the pattern better than any one of them alone.

Key takeaways

When you ask a group for feedback, no single person feels responsible for answering. This is diffusion of responsibility, and it is the main reason broadcast requests get ignored.
Silence is rarely apathy. It is usually a rational response to vagueness, to power dynamics, or to past requests that went nowhere.
People crave feedback far more than they are willing to give it. HBS found a consistent gap between how much we want input and how comfortable we feel offering it.
The standard fix, naming a specific person with a specific ask and a deadline, works. But it does not scale, and overused it starts to feel like surveillance.
Removing diffusion of responsibility structurally, by making input habitual, anonymous, and visible, gets you a response rate that manual tagging cannot match.

Why nobody answers your request

There is a pattern managers run into again and again. Ask a team for feedback in general and you get near silence. Tag a few people directly with a precise question and you can get a 100% response rate. Same team, same week, completely different outcome. That gap is worth understanding before you try to fix it.

Diffusion of responsibility

This is the core of it. When you write “I need feedback on X” to a channel, no individual feels personally on the hook. Everyone assumes someone else will reply, or that they are not the right person to comment. The more people you address at once, the less any single person feels called to act. You think you asked five people. Each of them heard you ask the room.

Cognitive overload

Your teammates get dozens of notifications a day. A message like “I reorganized the knowledge base” reads as background information, not as a task. Their brain triages it against everything else competing for attention, and a request with no clear action ends up at the bottom of the list. Not because it is unimportant, but because nothing about it says “this needs you, now.”

Ambiguity about what you actually want

“I need feedback” is vague in every dimension that matters. Feedback on what part? How detailed? By when? Is it required or optional? Who specifically should answer? This ambiguity creates a kind of paralysis. When people are not sure what a good response looks like, the safe move is to say nothing.

The power dynamic

If you are the manager, your team may quietly think “who am I to judge whether my boss’s work is good?” Even a sincere request for honest input runs into the reality that disagreeing with the person who runs your reviews carries risk. The HBS research sharpens this point. In one study, only four out of 212 people told a stranger they had a visible smudge on their face. People withhold even trivial, low-cost feedback, because they overestimate the discomfort of giving it and underestimate how much the other person wants it. Now add a reporting line on top of that instinct.

Silence is usually rational, not lazy

The most useful reframe I came across was from Mikki Forbes, who spent 15 years in HR. Her argument: when employees stop giving feedback, leaders assume disengagement, but the real reason is simpler. People stop believing it matters.

Feedback does not vanish overnight. It erodes through experience. Someone raises a concern, watches what happens next, and learns. When input is acknowledged but never acted on, when the response is vague or defensive, or when nothing changes at all, the lesson sinks in. As Forbes puts it, “silence becomes self-preservation, not disengagement.”

This is the part leaders miss. Each new survey or feedback request gets framed as a fresh start, a promise that this time will be different. The team remembers the last three times it was not. So participation drops, comments get shorter, and candor fades. Forbes is blunt about the diagnosis: “the issue is not engagement. It is credibility.”

That has a hard implication. If your team has learned that feedback goes nowhere, asking louder or more often will not help. Forbes notes that repeated requests without visible outcomes actually accelerate the withdrawal. People read constant surveying as proof that leadership listens without acting.

People want the feedback loop more than you think

It would be easy to conclude that people just do not care about feedback. The HBS work says the opposite, and the contrast is the interesting part.

A Gallup poll found only 26% of employees strongly believe the feedback they receive helps them do better work. In another survey, 72% of people rated managers giving critical feedback as important to their development, while only 5% felt their managers actually provided it. The appetite is real and mostly unmet.

So you have a team that genuinely wants a working feedback loop, sitting inside a system that has taught them giving and receiving feedback is risky and pointless. The silence is not the absence of wanting. It is wanting plus learned caution. That distinction is what makes the problem fixable.

The standard fix, and where it runs out

One fix is clean, and I think it is correct as far as it goes. Stop broadcasting. Make every request follow a simple pattern, Assignment, Request, Constraint:

Assignment. Name who should act. Not “the team.” A specific person.
Request. Say exactly what they should do. Not “give feedback” but “tell me if section X is clear enough to follow.”
Constraint. Add a deadline, because a time box creates the small pressure that moves a task off the bottom of the list.

So instead of “folks, I reworked the doc, thoughts?”, you write “@Sofia, you run the most onboardings, can you tell me by Thursday whether step three is clear?” That single change removes diffusion of responsibility, ambiguity, and cognitive overload in one move. It works.

It also has a ceiling. First, it is entirely manual. You have to hand-craft a targeted ask for every person every time you want input, which does not scale past a handful of requests. Second, a lighter version, asking people to at least leave a reaction so you know they have read it, tends to backfire. The team can read it as micromanagement, a check that they have done their homework, or it produces hollow compliance, a thumbs up with no real thought behind it.

And the deepest limit is the one that matters most. Getting people to respond to a message is a communication problem. Getting people to actually use a process, or to keep offering honest input over months, is an adoption problem. The blunt version: a chat message will never change an established behavior. What changes behavior is making the desired thing easier, building it into a routine, and showing that it works.

That is the gap a single well-worded message cannot close. And it is the part worth solving properly.

Where TeamMood fits

If diffusion of responsibility, the power dynamic, and learned silence are the three things killing your feedback requests, the fix is not a better-worded message. It is a channel where those three failure modes cannot take hold. That is the case for making input habitual, anonymous, and visible, which is roughly what TeamMood is built to do.

Habitual removes diffusion of responsibility. A TeamMood check-in is not a broadcast to a channel where everyone assumes someone else will answer. It is a short, regular prompt that arrives addressed to each person individually, through Slack, Teams, or email. There is no crowd to hide in, so “someone else will reply” stops working. Because it is a small daily or weekly rhythm rather than a one-off ask, responding becomes a habit instead of a decision, which is exactly the adoption mechanism a single message can never trigger.

Anonymous removes the power dynamic. Comments are anonymous by default. The HBS instinct, where people swallow feedback because giving it feels risky, gets a lot weaker when there is no name attached and no review-time consequence to weigh. That is the difference between “who am I to tell my boss this is unclear” and just typing what you actually think. Anonymity lowers the cost of honesty, which is the specific thing the power dynamic raises.

Visible rebuilds credibility. This is the answer to Forbes. Mood trends and comments aggregate into a shared view over time, so input does not disappear into one person’s inbox. The team can see that the signal is being collected and watched. When you bring an anonymous comment into a retro and say what you changed because of it, you are closing the loop in public, which is the one move Forbes says actually restores trust. Visible action is what teaches people that this time really is different.

None of this replaces talking to your team directly. A good targeted question is still the right tool when you need one specific person’s judgment on one specific thing. What the habitual, anonymous, visible loop adds is a baseline. It catches the honest signal that would otherwise stay unsaid, from the people who would never have answered your broadcast, and it keeps catching it after the novelty wears off.

Final thoughts

The instinct, when a feedback request gets ignored, is to take it personally or to read it as a checked-out team. Everything I have seen, and almost every source I looked into, points the other way. The silence is structural. It comes from diffusion of responsibility, from a power gap that makes honesty risky, and from a memory of past input that led nowhere.

You can fight that one message at a time, naming names and adding deadlines, and you should when it counts. But the more durable fix is to stop relying on the broadcast at all. Make input small enough to become a habit, safe enough to be honest, and visible enough that people watch it lead to action. Do that and the response rate stops being something you have to chase.

FAQ

Why does my team ignore my feedback requests?

Usually because of diffusion of responsibility. When you ask a whole group, no single person feels personally responsible for answering, so everyone assumes someone else will. Vague asks, competing notifications, and the risk of disagreeing with a manager make it worse. It is rarely apathy.

Is silence a sign my team is disengaged?

Not necessarily. HR practitioner Mikki Forbes argues silence is often a rational, learned response. If people have raised input before and watched nothing change, staying quiet becomes self-preservation. The problem is usually credibility, not engagement.

What is the best way to ask for feedback so people actually respond?

Stop broadcasting to a group. Address a specific person, ask for one specific thing rather than “feedback,” and add a deadline. This pattern is sometimes called Assignment, Request, Constraint. It removes the ambiguity and the diffusion of responsibility that cause silence.

Why do people want feedback but avoid giving it?

Harvard Business School research found people consistently overestimate the discomfort of giving feedback and underestimate how much the receiver wants it. In one study, only four of 212 people pointed out a stranger’s visible facial smudge. The appetite to receive input is far larger than the willingness to offer it.

How does TeamMood help get more honest input?

It removes the three things that cause silence. Check-ins are habitual and arrive individually, so diffusion of responsibility does not apply. Comments are anonymous, which lowers the risk of being honest with a manager. And TeamMood makes trends and comments visible over time, so the team can see input leads to action, which is what rebuilds the credibility that keeps people responding.

Learn more about TeamMood
and sign up here

Header photo by Johannes Plenio