Peer Feedback Examples for Designers

"Sarah consistently frames her design presentations around user problems and business outcomes, not just aesthetics. In last week's review, she started with the user insight, walked through her exploration, and clearly explained why the final direction best addressed the core need. The stakeholders left with full confidence in the direction."

"I've noticed Marcus takes feedback remarkably well. When I questioned his navigation approach, he didn't get defensive—he asked clarifying questions, took notes, and came back the next day with a thoughtful response that addressed my concerns while explaining constraints I hadn't considered."

"When engineering asked about the complexity of the animation, Priya didn't just say "trust me, it matters." She pulled up the user research showing how micro-interactions affected perceived performance, quantified the implementation cost, and proposed a simplified version that captured 80% of the value."

"Alex has become the designer that PMs request to work with. He attends sprint planning, understands technical constraints before designing, and proactively flags when a design might cause scope issues. His work rarely needs rework because he's collaborated throughout."

"Jordan's design work is excellent, but presentations often lose the audience. Last month's review spent too much time on process details that stakeholders didn't need. Focusing presentations on the "what" and "why" rather than "how" would help—stakeholders want to understand the decision, not the journey."

"When feedback challenges Taylor's designs, I notice a pattern of immediate justification rather than listening. This can shut down valuable input. Pausing to fully understand the concern before responding would help—the feedback might reveal something the explanation would have dismissed."

"Riley sometimes struggles to articulate why one design direction is better than another. When pressed, the response is often "it feels right" or "it's better UX." Building a vocabulary around design principles and tying decisions to specific heuristics would strengthen credibility."

"Casey tends to work in isolation until designs are polished, then present finished work. This sometimes leads to rework when engineering or PM constraints emerge late. Earlier, rougher collaboration—even with messy sketches—would prevent misalignment."