What should I tell a team after collecting feedback on a change?

Close the loop in a few clear moves: thank people for contributing, summarize the main themes, then explain the decision and what happens next. Separate the feedback you heard from the action you’re taking. That helps the team see that their input was considered without suggesting every request can be accommodated.

For each theme, say whether it led to a change, will stay as planned for now, or still needs a decision. Give a brief reason in work-related terms, such as timing, scope, or a dependency, if that explains the choice. Avoid promising more than you know. If you cannot share a decision yet, say what is still being considered and when you expect to provide an update.

Group comments by topic rather than repeating them one by one. Use neutral wording that captures the concern without exaggerating agreement: for example, “Several comments raised questions about the handoff,” rather than “Everyone opposes the handoff.” Only describe how common a view was if your notes support that description.

You can mention a concern as a theme without attaching it to a person. If a specific suggestion matters to the decision, describe the idea rather than naming its contributor, unless naming them is necessary and appropriate. Keep the summary short enough to scan, but include a theme that materially shaped the decision—even if the final choice is not the one suggested.

Make the split explicit. For each important theme, state the response and a concise reason. For example: “We’ll add a short handoff checklist based on the questions raised. We’ll keep the launch date unchanged because moving it is not part of this decision. We’re still checking whether the reporting step needs an owner; I’ll share an update by [date].”

That is a hypothetical example: replace the details with your actual decision and avoid stating a reason that is not true. If the decision-maker has not confirmed an item, label it as unresolved rather than presenting it as settled. If a suggestion cannot be adopted, acknowledge the underlying concern and explain what, if anything, will address it.

Use this copyable template and fill in only confirmed details:

“Thanks for sharing feedback on [change]. I heard three main themes: [theme one], [theme two], and [theme three].

Based on that input, we will [specific change]. We will keep [part of plan] as planned because [brief, accurate reason]. We are still deciding [open question]; [person or role responsible] expects to update the team by [date or milestone].

If I’ve missed an important theme, or if you have a question about how this affects your work, please [reply in channel / raise it at meeting] by [date]. I’ll share the next update through [place or method].”

Before sending, check that the themes are fair, the decision is approved, and the promised date is realistic. If there is no open decision, remove that sentence. Keep the invitation focused on corrections or practical questions; do not imply that the decision will be reopened unless it actually will be.