Avoid This Common Feedback Pitfall
Welcome to the #culturedrop. Every Tuesday, Galen Emanuele emails tools to advance leadership skills, team culture, and personal growth. No spam, just great content. Sign up now to get it in your inbox.
A common pitfall around feedback that’s good to be aware of.
This week's #culturedrop is about a specific dynamic I see semi-often with teams and leaders around feedback that's good to be aware of. This dynamic always comes from a good place, but in the words of Admiral Ackbar, "It's a traaaap!"
It’s subtle, but it can create a surprising amount of friction if you’re not aware of the dynamic. It has to do with how we solicit feedback and give it, and it applies to leaders and non-leaders alike. If you work on a team, this is relevant to have on your radar.
The “Conjured Feedback” trap.
Here’s the pattern.
A leader creates something or has an idea of a direction they want to take, etc. Maybe it’s a strategy doc, a new process, a deck, or a proposal. They want the team to feel included and to have a voice. So they share it with the team and ask, “Any feedback?”
“When people are asked for feedback, they often feel like they have to give some. Even if they don’t actually have strong opinions.”
That sounds healthy, and it certainly comes from a good place.
But here’s the potential catch: when people are asked for feedback, they often feel like they have to give some. Even if they don’t actually have strong opinions, or nothing feels particularly off, or the feedback isn’t all that important. So sometimes, to contribute, they conjure something up.
On the other side, the leader can receive a flood of comments and now wonder, “If I don’t address all of this, will people feel ignored?”
It’s not a guarantee that this will happen, and it doesn’t happen every time, but it can and does happen. Now both sides feel pressure. Employees feel pressure to contribute. Leaders feel pressure to incorporate the input from the team. It can gum up and really complicate the process.
That’s the trap. So here are some tips to avoid this dynamic.
Be clear about what kind of feedback you want.
One simple way to avoid this is to be more intentional about the kind of feedback you’re asking for and open to.
Instead of a broad “Any feedback?”, try qualifying it with questions like:
“Is there anything glaring that needs to be addressed?”
“Am I missing anything, are there any major issues or risks you see?”
“Does anything here feel misaligned with our goals?”
That framing does two things:
It narrows the scope.
It signals that you’re looking for meaningful input, not minor preferences.
When you’re clear about what kind of feedback you want, people don’t feel obligated to nitpick. They’re more likely to focus on what truly matters.
“When you’re clear about what kind of feedback you want, people don’t feel obligated to nitpick. They’re more likely to focus on what truly matters.”
Ask how important it is.
Here’s another practical tool: ask people to rate the importance of their feedback.
For example:
“On a scale of 1 to 10, how important is this change to you?”
This adds helpful context.
Sometimes someone will say, “This is probably a 2 out of 10, but I noticed it.” That’s useful. It tells you the comment exists, but it’s not that critical.
Or you might hear, “This is a 9 for me. I think this could create a real issue.” That’s meaningful and should be addressed in a totally different way.
Without that context, everything can look equally urgent.
If you’re providing feedback, you have agency too.
This isn’t just about leaders. If you’re asked for feedback, you don’t have to manufacture it.
It’s completely acceptable to say:
“I don’t have any major feedback.”
“Nothing glaring stands out to me.”
“Overall, this looks solid.”
You can also add context to your own comments:
“This is minor.”
“This is more of a preference than a concern.”
“This is low priority, but worth noting.”
That kind of clarity helps leaders make better decisions without feeling like they’re dismissing you.
In my observations, highly analytical or detail-oriented, or engineer-minded team members are especially likely to generate a lot of feedback. That can be incredibly valuable, but not all feedback carries the same weight, and it helps to use some of these tools to signal the difference.
Context matters.
“In many day-to-day business scenarios, what’s needed is targeted, prioritized feedback.”
There are situations where broad, open-ended, creative feedback is exactly what you want. Early brainstorming, sensitive decisions. big strategic shifts.
But in many day-to-day business scenarios, what’s needed is targeted, prioritized feedback. Without that clarity, teams can get stuck in cycles of over-editing, second-guessing, and unnecessary revision.
A smarter way to think about and solicit feedback.
Leaders can:
Be explicit about what kind of feedback they want.
Clarify whether they’re looking for major issues or minor tweaks.
Ask how important each piece of feedback is.
Team members can:
Avoid creating feedback just to participate.
Be honest when nothing stands out.
Provide context about how strongly they feel about their input.
It’s a small shift. But it can reduce pressure on both sides and lead to better, cleaner decisions, and better alignment.
Keeping this pitfall/dynamic in mind the next time you ask for or give feedback, it may make the process feel much smoother for everyone involved and save a good amount of time and energy.
Related Blogs:
Feedback as a Relationship Dynamic
Increase Input & Participation From Your Whole Team (Not Just Extroverts)
Want more?
This article was created by Galen Emanuele for the #culturedrop. Free leadership and team culture content in less than 5 minutes a week. Check out the rest of this month's content and subscribe to the Culture Drop at https://bit.ly/culturedrop
MORE
