.jpg)
The Real Difference Between Good and Bad Feedback
Three things separate feedback that gets acted on from feedback that gets discarded:
It is specific. "Great idea, but let us table it for now" is not feedback. "We love the direction, but you are assuming customers will tolerate a two-week wait, and our support data shows they will not" is feedback.
It is connected to a future action. "This does not fit our current priorities" might be true, but without a next step it is a dead end. "This does not fit our current priorities, but we should revisit it in Q3 when we have more capacity in the engineering team" is feedback with a path forward.
It is a conversation, not a pronouncement. You do not announce a decision and then move on. You explain the thinking and then listen to the response. Sometimes the feedback is wrong or incomplete, and you need to adjust.
The most important thing leaders and evaluators often miss: the person who submitted the idea is often the first expert on whether the feedback makes sense. They may know something about the idea, the market, or the company that you do not. That does not mean you have to accept their push-back, but you have to listen to it.
Five Ways to Give Feedback That Builds Trust
1. Start with what is good about the idea, even if it did not make it. This is not about being nice. It is about accuracy. If an idea did not make it because the timing was wrong, say that. Do not imply there is something fundamentally wrong with the thinking.
2. Be specific about what the decision was based on. "This did not advance because we prioritized ideas that can be tested within 60 days, and your idea requires a six-month implementation cycle." That is feedback someone can actually use. It either points them toward refinements (could this be tested in a smaller way first?) or toward a different forum (maybe this belongs in strategic planning, not innovation).
3. Acknowledge the legitimate constraints that shaped the decision, even if they are frustrating. "We received 47 ideas and could only advance 5. Here is how we made the choice." People accept constraints. What they do not accept is feeling like decisions were arbitrary or political.
4. If the idea has merit but the timing is wrong, name the future decision point.** "We are parking this in the Q3 review. It will be the first one we look at if resource availability opens up." Or, "This is a good candidate for our strategic planning process in the fall. Here is who you should talk to there." Do not leave people hanging.
5. Invite a conversation if the person disagrees with the decision. Most people will not do this. They will accept the decision and move on. But a small percentage will have a legitimate point you missed. Make space for that.
The Feedback Loop That Predicts Future Participation
Here is what kills innovation momentum in a program: people submit ideas, do not hear anything for three months, and then get a form letter saying "thanks for your input." Those people do not submit again. Their friends do not either.
Here is what builds momentum: people know when they will hear back (a specific date), they get actual feedback (not just a yes/no, but reasoning), and they see movement (even if their idea did not advance, they see other ideas advancing and things actually happening).
Set a feedback deadline and stick to it. Communicate progress in aggregate. "We are advancing ideas 1, 3, and 7. Here is what we learned that ruled out the others." And then do what you said you would do.
The person whose idea did not advance does not have to be happy about it. They have to feel like the process was fair, honest, and connected to actual work.
Related Guides
- How to Write an Idea Challenge That Actually Gets Relevant Ideas
- How to Prioritize Ideas When Everything Feels Important
- The Internal Communication Toolkit: Templates for Every Stage
→ See our full comparison of the 10 best idea management tools
.jpg)
.jpg)
