Getting honest feedback in a design community can be tough, but it is essential for growth and improvement. Use these ready-to-go templates to spark valuable conversations, gather diverse insights, and make your members feel heard.
Plan your content calendar and auto-post to Skool, Circle, or Mighty Networks
Inviting community feedback creates a sense of ownership and belonging among members. When designers are asked for their opinions, they are more likely to contribute, share their experiences, and feel invested in the community's direction. Open-ended feedback prompts encourage critical thinking and creative problem-solving, which are core skills in design.
Feedback-driven posts also help community managers identify trends, uncover hidden issues, and surface fresh ideas. By making feedback a regular, low-pressure activity, you lower the barrier for participation and create an environment where every voice matters. This not only improves engagement but can lead to meaningful improvements in community content, tools, and culture.
What do you think about our latest color palette update? Let us know your honest thoughts.
💡 Example: "What do you think about our latest color palette update? Let us know your honest thoughts."
How do you feel about the new resource library layout? What works and what could be better?
💡 Example: "How do you feel about the new resource library layout? What works and what could be better?"
Which design tool has helped you most this month? Share your experience.
💡 Example: "Which design tool has helped you most this month? Share your experience."
If you could change one thing about our design challenge format, what would it be?
💡 Example: "If you could change one thing about our design challenge format, what would it be?"
Do you prefer light or dark themes in your design software? Why?
💡 Example: "Do you prefer light or dark themes in your design software? Why?"
What topics should we cover in our next design webinar?
💡 Example: "What topics should we cover in our next design webinar?"
On a scale of 1-10, how useful are our weekly inspiration posts?
💡 Example: "On a scale of 1-10, how useful are our weekly inspiration posts?"
What feature would make our community platform easier for you to use?
💡 Example: "What feature would make our community platform easier for you to use?"
Have you found the project critique sessions helpful? Why or why not?
💡 Example: "Have you found the project critique sessions helpful? Why or why not?"
What is one thing you wish you knew when you first joined this community?
💡 Example: "What is one thing you wish you knew when you first joined this community?"
Which of our design resources do you use the most?
💡 Example: "Which of our design resources do you use the most?"
Share your thoughts on our community guidelines. Are they clear and helpful?
💡 Example: "Share your thoughts on our community guidelines. Are they clear and helpful?"
How could our event reminders be improved for better attendance?
💡 Example: "How could our event reminders be improved for better attendance?"
What design trends do you want us to spotlight next month?
💡 Example: "What design trends do you want us to spotlight next month?"
Is there a resource you wish we had in our collection?
💡 Example: "Is there a resource you wish we had in our collection?"
Tell us about your experience with our recent design tool review post.
💡 Example: "Tell us about your experience with our recent design tool review post."
How can we make our feedback process more comfortable for new members?
💡 Example: "How can we make our feedback process more comfortable for new members?"
Which design podcasts would you recommend to others here?
💡 Example: "Which design podcasts would you recommend to others here?"
What type of tutorials would you like to see more of in our community?
💡 Example: "What type of tutorials would you like to see more of in our community?"
How can we better recognize members who contribute regularly?
💡 Example: "How can we better recognize members who contribute regularly?"
Has our design inspiration channel sparked new ideas for you?
💡 Example: "Has our design inspiration channel sparked new ideas for you?"
Which design topic should we discuss in our next live session?
💡 Example: "Which design topic should we discuss in our next live session?"
What was your biggest design challenge this week and how did you solve it?
💡 Example: "What was your biggest design challenge this week and how did you solve it?"
How easy is it to find what you need in our resources section?
💡 Example: "How easy is it to find what you need in our resources section?"
If you could add any feature to our platform, what would it be and why?
💡 Example: "If you could add any feature to our platform, what would it be and why?"
How do you prefer to receive updates about community news or events?
💡 Example: "How do you prefer to receive updates about community news or events?"
What makes you feel most welcomed when joining a design community?
💡 Example: "What makes you feel most welcomed when joining a design community?"
Share one thing that surprised you about our last design challenge.
💡 Example: "Share one thing that surprised you about our last design challenge."
What do you want to learn next in your design journey?
💡 Example: "What do you want to learn next in your design journey?"
If you could invite any guest speaker, who would you choose and why?
💡 Example: "If you could invite any guest speaker, who would you choose and why?"
Are our community rules easy to find and understand?
💡 Example: "Are our community rules easy to find and understand?"
How would you improve our design critique process?
💡 Example: "How would you improve our design critique process?"
What kind of design content keeps you engaged here?
💡 Example: "What kind of design content keeps you engaged here?"
Do you feel comfortable sharing unfinished work in this space? Why or why not?
💡 Example: "Do you feel comfortable sharing unfinished work in this space? Why or why not?"
Which community event has been most valuable for your growth?
💡 Example: "Which community event has been most valuable for your growth?"
Are there any accessibility improvements you would like to see in our resources?
💡 Example: "Are there any accessibility improvements you would like to see in our resources?"
How often do you participate in our design challenges?
💡 Example: "How often do you participate in our design challenges?"
What is your favorite way to give feedback to other designers?
💡 Example: "What is your favorite way to give feedback to other designers?"
If you could change our community's visual identity, what would you tweak?
💡 Example: "If you could change our community's visual identity, what would you tweak?"
How clear are the instructions for submitting design work here?
💡 Example: "How clear are the instructions for submitting design work here?"
What is one thing we can do to make this community more inclusive?
💡 Example: "What is one thing we can do to make this community more inclusive?"
Pick a template that matches your current needs, customize the topic or feature for your community, and post it as a discussion or poll. Encourage replies by tagging relevant members or sharing your own responses first. Follow up with a summary of the feedback and highlight any changes you plan to make, so members see their input in action.
These templates work across all platforms. On forums and Slack, post as threads and tag members for input. On Discord, use dedicated feedback channels or run quick polls. In Facebook or LinkedIn groups, pin your feedback post for visibility and encourage reactions or comments. Always adapt your language to suit your platform's culture and features.
To differentiate feedback between UX and visual aesthetics, customize prompts within your template to focus on each area separately. For example, include questions like 'How intuitive was the navigation flow?' for UX, and 'Do the color palettes and typography support the brand identity?' for visual elements. This helps members provide relevant, actionable feedback tailored to each discipline.
Use a versioned feedback template that prompts members to compare specific elements between iterations, such as 'What improvements do you notice in the layout from v1 to v2?' or 'Does the updated iconography enhance clarity?' Highlighting the changed design assets in the post and asking for targeted input ensures feedback is relevant to the current iteration.
Integrate dedicated sections in your template asking about accessibility features, such as color contrast ratios, font legibility, and keyboard navigation. For example: 'Do you see any areas where the design may not meet WCAG 2.1 AA criteria?' This invites members with accessibility expertise to share insights and ensures that compliance is part of the group’s collective review.
Include a section in your feedback template specifically referencing the design system or style guide in use. Ask questions like 'Does this component align with our established button hierarchy?' or 'Are the spacing and grid systems consistent with our style guide?' Providing a link to the style guide within the post also helps reviewers anchor their feedback in established standards.
Add prompts in your template about file structure and designer intent, such as 'Is the Figma/Sketch file organized and labeled clearly for team handoff?' or 'Are the prototype's user flows and annotations easy to understand?' This ensures feedback encompasses both the visual output and the collaborative process, helping members improve their workflow.
Include explicit prompts in your feedback templates asking about interactive elements, for example: 'Did you notice any missing or unclear micro-interactions, such as loading spinners or hover transitions?' or 'Are interactive cues (like button states) consistent and intuitive?' This encourages reviewers to look beyond static visuals and assess the full user experience.
Skool · Circle · Mighty Networks