How to Give Feedback That Builds Trust (Even When the Answer Is No)

Feedback is the part of idea management that most organisations either skip entirely or get badly wrong. And it is the part that determines whether people submit ideas the next time you run a campaign.

People can handle a no. What they cannot handle is silence. Or a generic thank you for your contribution that tells them nothing about whether their idea was actually considered. Or finding out three months later that the program moved forward with something completely different and nobody told them.

The feedback templates in this guide are designed to be honest, specific, and short. They do not require a lot of time to write, and they pay back every time you run another campaign.

The One Phrase to Strike From Your Template Library

Delete this phrase from every feedback template you ever send: we cannot move forward at this time.

It is meaningless. At this time implies there will be another time, when there probably will not be. It does not tell the person why their idea was declined. It sounds like a form letter, because it is. It makes the person feel like their submission went into a black hole with a polite cover note.

Replace it with the actual reason. Every time.

The Three-Part Feedback Formula

Good feedback, even when it is a no, has three parts:

Part 1: Acknowledge the thinking
Name something specific about the submission that shows you actually read it. Not the idea is interesting, which is generic. Something specific: the part you found most compelling, the problem they identified correctly, the angle that the team had not considered before.

Part 2: Explain the actual reason
One or two sentences, honest and direct. See the templates below for the most common scenarios.

Part 3: Leave the door open (when it is genuine)
If the idea might be relevant in a different context or a future cycle, say so specifically. If it will not be, do not add a hollow invitation to resubmit because it feels polite. That costs trust, not earns it.

Five Ready-to-Send Feedback Templates

Template 1: Moving forward

Hi [Name],

Your idea [describe in 3 to 5 words] has been selected to move forward. We particularly valued [specific element: e.g., the clear problem statement, the implementation path you described, the insight about which customers would benefit most].

Next steps: [name the owner and the immediate next action]. We will update you on progress at [specific milestone or timeframe].

Thank you for taking the time to put this together.

Template 2: Parking for later

Hi [Name],

We reviewed your idea on [topic] and we want to be direct with you: we are not moving forward with it in this cycle.

This is not a rejection of the underlying thinking. [Specific element] reflects a real problem we care about. The reason we are not acting on it now is [actual reason: e.g., we have already committed resources to three other initiatives this quarter that overlap with this area, and adding a fourth would mean none of them get done properly].

We are keeping this in our backlog and plan to revisit it in [timeframe]. If the circumstances change before then, we will reach out.

Template 3: Not a fit right now

Hi [Name],

We reviewed your idea on [topic]. We are not going to move forward with it, and we want to give you a real reason rather than a form letter.

[Specific reason: e.g., This falls outside the scope of what we can change in the current system without a significant infrastructure investment that is not in this year's budget. / This addresses a problem that is on our radar, but our current improvement plan already has a solution in progress that covers the same ground. / We tried a version of this approach in [year] and found that [specific issue]. That does not mean this version would have the same problem, but it means we would need more evidence before investing in it.]

If you have more context that would change the picture, we would genuinely like to hear it.

[Your name]

Template 4: Needs more development

Hi [Name],

We reviewed your submission on [topic]. The problem you are identifying is real and worth solving. What we need before we can move it forward is more clarity on [specific gap: e.g., how it would work in practice / what the cost to implement would be roughly / how it would affect the people in [department] who currently own this process].

Would you be willing to spend 30 minutes developing it further? If you can add that detail, we will put it back in the evaluation in the next review cycle on [date].

[Your name]

Template 5: Duplicate of an existing initiative

Hi [Name],

Your idea on [topic] landed on a problem we are actively working on. You are not wrong about the issue. We already have [brief description of existing initiative] in progress, which addresses the same root cause.

We are going to close your submission as a duplicate rather than evaluate it separately. But if you have a perspective on the approach we are taking that you think we are missing, we would genuinely welcome that as input to the work already underway. Let [name or team] know.

[Your name]

The One Thing You Can Do Publicly

Individual feedback builds individual trust. Public communication builds programme trust.

After every campaign cycle, post a brief summary somewhere visible: what we heard, what we are doing, and what we decided not to pursue. Not a long report. Three or four sentences in a shared channel or on your intranet. This signals to everyone, including people who did not submit, that the programme produces real outcomes. It is the single most effective thing you can do to increase participation in your next campaign.

Common feedback mistakes to avoid

Being too soft. "We loved this idea!" followed by rejection is confusing and frustrating. Be clear about what you actually thought and why you said no. Honesty builds trust. Sugar-coating destroys it.

Taking too long. Feedback given three months after submission is worse than useless. It feels like the idea was lost, found again, and then evaluated half-heartedly. Target feedback within 30 days. If evaluation will take longer, tell the submitter upfront.

No specific reasoning. Vague rejection language like "does not align with our priorities" means nothing. Specific reasoning: "This would require us to rebuild our reporting system, which is not in the roadmap for 2026" tells the person exactly why and implicitly suggests when they might resubmit a similar idea.

Forgetting to acknowledge the effort. Even if the idea is not moving forward, acknowledge that the person cared enough to think about it and write it down. "Thank you for thinking about this" is genuine and costs nothing.

Frequently asked questions

Should feedback always be written?

Not always. Quick conversations work for ideas from close colleagues or ideas that need dialogue to develop further. But for any formal campaign submission, written feedback is critical. Written feedback: creates a record the submitter can reference later, ensures consistency (the submitter knows everyone got the same process), and signals to the broader organisation that the process is serious and documented.

How specific does the feedback need to be?

Specific enough that the submitter understands the reasoning. If your feedback could apply to any rejected idea ("does not fit our strategy"), it is too generic. Specific feedback references details from the submission and explains exactly why those details matter to the decision.

What if the decision was made quickly or without much consideration?

Do not pretend you gave it more thought than you did. You can still provide specific feedback: "We screened this against your strategic focus and realised we have already committed this quarter's resources to similar work. We are parking it for Q3 review." This is honest and specific without claiming you did a deep evaluation.

How long should feedback take to write?

A good feedback message takes 2-3 minutes to write. Pick a template, fill in the blanks, and send. If you are spending 20 minutes on feedback, you are over-thinking it. Speed signals that the process is running smoothly. Slow feedback signals that ideas are bottlenecked.

Should you offer to discuss the decision?

Yes, but be genuine about it. "If you want to discuss this, let me know" only works if you actually mean it. If you are overwhelmed and cannot have a conversation, do not offer. A clear decision with no dialogue is better than an invitation to discuss that never materialises.

How do you handle feedback when the decision is not final?

Be clear about what is final and what is not. "We are moving forward with this idea. Implementation is scheduled for Q3." is clear. "We think this is worth exploring further but we are not committing to it yet" is also clear. Ambiguous feedback damages trust.

The goal of feedback is simple: make the submitter understand the decision and feel respected in the process, even if the answer is no. When you achieve that, people contribute ideas to the next campaign. When you do not, they do not.

Learn how to build an idea collection system that generates enough good ideas to evaluate.