Handling Feedback

Key Points

• •Feedback comes in three types: Directional, Specific, and Emotional—each requires different handling
• •Response framework: Listen fully, Ask clarifying questions, Acknowledge their perspective, Propose alternatives
• •The "Yes, and..." approach transforms adversarial dynamics into collaboration
• •"Make the logo bigger" usually means "I'm worried about brand visibility"—translate surface requests to goals
• •"I don't like the colors" could mean brand misalignment, accessibility concern, or personal preference
• •Change resistance is natural—address it with transition plans and demonstrations rather than argument
• •[FIGURE — Feedback response framework] Shows: Flowchart from receiving feedback through listen → clarify → acknowledge → propose cycle. Teaches: Structured response prevents defensive reactions and uncovers the real concern. Reproduce as: Interactive feedback handling decision tree.

Guidelines

• ✓Never respond to feedback immediately with a defense — pause, acknowledge, then ask "Can you help me understand what specifically concerns you?"
• ✓Separate "what" feedback (the underlying need) from "how" feedback (the proposed solution) — stakeholders often suggest solutions when they mean to describe problems
• ✓When someone says "Can't we just copy [competitor]?", acknowledge what they admire, then explain how your context, users, and goals differ
• ✓Keep a parking lot for feedback that can't be addressed immediately — shows respect while maintaining focus
• ✓After resolving feedback, follow up to confirm the concern was actually addressed — this builds trust for future conversations
• ✓If feedback contradicts user research, share the data respectfully: "That's an interesting instinct. Our testing actually showed the opposite — here's what we found..."

Related Topics