How can I collect feedback from quieter team members about a new process?
Quick answer
Offer several ways to respond, such as a short private message, a written form, or a facilitated team conversation. Ask about specific moments in the process, give people time to think, and explain what you will do with their input and when you will report back. Participation should be optional where possible; silence does not tell you what someone thinks, and feedback is not a performance measure.
The question, the details, the next step.
We introduced a new process, but the same few people speak up in meetings. How can I hear from quieter team members without putting them on the spot?
Make the invitation explicit and offer more than one route to respond. For example, tell the team they can share a written note privately with you, use a short form, or discuss feedback in a meeting. Give everyone the same questions and a reasonable window to think; do not interpret a quiet meeting or an unanswered prompt as agreement.
Keep the questions about the process rather than about who is a “quiet” person. Ask what happened during a particular step, what helped, and where someone got stuck. If you invite comments in a group, let people pass and avoid calling on individuals to explain their choice.
What should I say so people know why I’m asking and what will happen to their comments?
Be specific about the purpose, who will review the feedback, how you will use it, and when you will share a response. Do not promise confidentiality or anonymity unless you can genuinely provide it. If comments may be shared with the team, say so in advance, and offer a way to raise a point directly if someone does not want to discuss it in a group.
Copyable invitation (adjust the bracketed details):
“Could you share feedback on the new [process] by [date]? I’m looking for specific steps that are working well, causing friction, or unclear. You can reply to me in writing, use [form or channel], or bring a point to our [meeting]. I’ll review the feedback with [people or group], use it to decide whether to adjust the process, and share a summary of themes and next steps by [date]. Please don’t include details you aren’t comfortable sharing through these options.”
How do I make the questions useful instead of just asking whether people like the process?
Ask about observable moments so people can give concrete feedback without needing to make a broad judgment. Keep the set short, and let someone answer only the questions they can speak to. For example:
- Which step was easiest to complete, and what made it clear?
- Where, if anywhere, did you have to wait, repeat work, or ask for clarification?
- What information or handoff would have helped at that point?
- If we changed one thing before the next cycle, what would you suggest?
For a hypothetical process with a new request form, someone might write: “I could submit the request, but I wasn’t sure which priority option to choose.” That points to a possible clarification to consider; it does not by itself prove that the whole process is failing. Look for patterns across input and check ambiguous comments with the person where appropriate.
Once I have responses, how can I show people their input mattered without promising every suggestion will be adopted?
Close the loop on a stated date, even if the decision is to keep the process unchanged for now. Summarize themes without attributing comments unless you have permission, explain which changes you will try and why, and name suggestions you cannot take forward along with the reason. Separate a suggestion from a confirmed issue; feedback can guide a review, but it may not settle every disagreement.
For instance, a follow-up might say: “Several comments pointed to confusion at [step]. We’ll clarify [specific instruction] for the next cycle and review how it works on [date]. We’re not changing [other step] right now because [reason]. If that creates a problem in practice, please share a specific example through [option].” Then provide the same routes for further feedback. Do not treat response rates or silence as a score of anyone’s engagement or performance.
A practical checklist
State why you are collecting feedback, who will review it, and when you will report back.
Offer at least two practical ways to respond, including a written option.
Ask a short set of questions about specific steps, delays, unclear information, and possible improvements.
Give people time to respond and make clear they may pass; do not treat silence as agreement.
Summarize themes and explain what you will change, keep, or review later.
A few more useful answers
Should I collect feedback anonymously?
Use an anonymous option only if you can actually collect and review responses without identifying contributors. Otherwise, explain who can see responses and offer a private route without promising anonymity.
What if only a few people respond?
Share the options again or offer a different format, but do not infer what nonrespondents think. Note that the feedback reflects the responses received, not necessarily everyone’s view.
Should I ask for feedback during a team meeting?
You can, but make it one option rather than the only one. Share questions beforehand, allow people to pass, and provide a written follow-up route for anyone who would rather reflect first.