Back to Documentation

Writing Good Feedback

Learn how to write effective, actionable feedback that helps developers improve their products.

The Art of Good Feedback

Good feedback is specific, actionable, and constructive. It helps developers understand not just what needs to change, but why and how. This guide will help you write feedback that makes a real impact.

Structure Your Feedback

1. Start with the Positive

Begin by acknowledging what works well:

"The color scheme is cohesive and the typography is very readable. I particularly like how the navigation feels intuitive."

2. Identify Issues Clearly

Be specific about what doesn't work:

"The submit button on the contact form is hard to find because it's the same color as the background. Consider using a contrasting color to make it more prominent."

3. Provide Solutions

Don't just point out problems—suggest improvements:

"Consider adding a loading state when the form is submitting, and a success message after submission. This will improve user confidence and reduce confusion."

Be Specific, Not Vague

Bad Feedback Examples

  • "The design is confusing" - Too vague, doesn't explain what's confusing
  • "I don't like the colors" - Personal preference without context
  • "It's broken" - Doesn't explain what's broken or how to reproduce

Good Feedback Examples

  • "The navigation menu is confusing because there's no clear hierarchy. The 'Settings' link is nested under three different menus, making it hard to find."
  • "The color contrast between the text and background doesn't meet WCAG AA standards. The gray text (#999999) on white background has a contrast ratio of 2.8:1, which may be difficult for users with visual impairments."
  • "When I click 'Submit' on the form, nothing happens and there's no feedback. I'm not sure if my submission went through. Adding a loading spinner and success message would help."

Consider Different Perspectives

Think about feedback from multiple angles:

  • First-time users: Is the interface intuitive for someone seeing it for the first time?
  • Accessibility: Can users with disabilities use this effectively?
  • Mobile users: How does it work on smaller screens?
  • Performance: Does it load quickly and respond smoothly?
  • Error handling: What happens when something goes wrong?

Use the Right Tone

Your tone matters. Be:

  • Respectful: Remember that developers have invested time and effort
  • Constructive: Focus on helping, not criticizing
  • Professional: Maintain a friendly but professional tone
  • Encouraging: Acknowledge good work while suggesting improvements

Include Visual Evidence

When possible, include:

  • Screenshots: Show exactly what you're referring to
  • Annotations: Mark specific areas in screenshots
  • Comparisons: Show examples of how it could be improved
  • Step-by-step: Document the exact steps to reproduce issues

Prioritize Your Feedback

Help developers understand what's most important:

  • Critical: Issues that prevent users from completing tasks
  • High: Significant usability problems that impact experience
  • Medium: Issues that should be addressed but aren't blocking
  • Low: Minor improvements and polish suggestions