Giving good design feedback is a skill that takes deliberate practice. The difference between feedback that improves work and feedback that demoralizes a teammate often comes down to how you frame your observations. This lesson provides a practical framework for delivering feedback that is honest, useful, and respectful.
The Specific, Actionable, Kind Framework
Every piece of design feedback should pass three tests:
Specific — Does it identify a concrete element or behavior? "The spacing feels off" fails this test. "The 8px gap between the headline and the subtext makes them feel disconnected" passes it. Specificity gives the designer a clear target.
Actionable — Can the designer do something with this feedback? "This doesn't feel right" is not actionable. "Consider increasing the visual weight of the primary CTA so it stands out from the secondary actions" gives a clear direction. Even when you do not prescribe a solution, actionable feedback points toward what needs to change.
Kind — Is the feedback delivered with empathy and respect? Kind does not mean dishonest or sugarcoated. It means acknowledging the effort, framing suggestions constructively, and choosing words that open conversation rather than shut it down.
Practical example: Instead of "This page is way too cluttered," try "The number of elements competing for attention on this page might overwhelm users trying to find the main action. What if we explored a clearer visual hierarchy?"
Focusing on Goals, Not Preferences
The most common mistake in design feedback is confusing personal taste with objective evaluation. When you say "I would make this red," you are expressing a preference. When you say "The current color does not create enough contrast against the background to meet our accessibility standard," you are evaluating against a goal.
Questions to ask yourself before giving feedback:
- Does this feedback connect to a user need, business goal, or design principle?
- Would this feedback change if someone with different taste were giving it?
- Am I reacting to the design or to the fact that I would have done it differently?
If your feedback is primarily about personal preference, either reframe it as an objective concern or keep it to yourself. Preference-based feedback wastes review time and erodes trust.
Practical tip: Prefix goal-connected feedback with the goal: "For our goal of reducing first-time setup to under 2 minutes, the five-screen wizard might be adding unnecessary friction." This makes your reasoning transparent.
Examples of Good vs Bad Feedback
Seeing concrete examples clarifies the difference between helpful and unhelpful feedback:
Bad: "I don't like the font." Good: "The decorative font choice for body text may reduce readability for extended reading sessions. Our content pages have an average reading time of 4 minutes, so a more legible typeface could improve the experience."
Bad: "Make the logo bigger." Good: "The logo feels underemphasized relative to the navigation items. Since brand recognition is a priority for this marketing page, we might explore giving it more visual prominence."
Bad: "This is confusing." Good: "I was not sure whether the blue text is a link or just styled text. If it is clickable, an underline or button treatment would make the affordance clearer."
Bad: "Can you just copy what Stripe does?" Good: "Stripe's pricing page handles the comparison of plan tiers really clearly. The way they highlight the recommended plan might be worth exploring for our use case."
Bad: "This needs more pizzazz." Good: "The page feels visually flat, which might not convey the energy of our brand. Adding contrast through typography scale, color accents, or imagery could help establish the right tone."
The Feedback Sandwich (and Why to Avoid It)
The "feedback sandwich" — positive comment, negative comment, positive comment — is widely taught but often backfires. People learn to ignore the positive parts and wait for the criticism. It can feel formulaic and insincere.
Instead, try honest sequencing:
- Start by acknowledging what the design does well and why those elements work
- Transition naturally to areas for improvement with clear reasoning
- End with a forward-looking suggestion or question
The difference is subtlety. You are not padding criticism with fake praise. You are genuinely recognizing good work before exploring where the design can grow.
Adapting Feedback to Context
Not all feedback situations are the same. Adjust your approach based on:
- The stage of the work — Early concepts need directional feedback about strategy and approach. Polished mockups need detailed feedback about execution and craft.
- The designer's experience — Junior designers may need more explicit suggestions. Senior designers often prefer you to identify the problem and trust them to find the solution.
- The relationship — With close collaborators, you can be more direct. With people you do not know well, invest more in framing and tone.
Key Takeaways
- Good feedback is specific, actionable, and kind — test every comment against these three criteria
- Connect feedback to user needs and business goals, not personal preferences
- Show concrete examples when possible rather than abstract suggestions
- Skip the feedback sandwich — be honestly sequenced instead
- Adapt your feedback style to the stage of work and the designer's experience level