How do you handle design critique and feedback?

What They’re Really Asking

Can you depersonalize feedback, extract useful insights, and use critique to improve design outcomes?

Strong Sample Answer

I approach critique as a collaborative tool, not a personal attack. At Google, I led a daily standup where designers and engineers reviewed prototypes in Figma. I used the GROW model to structure each session: first clarifying the goal (e.g., improving task completion), then stating the reality (current conversion rate was 52%), exploring options like simplifying a multi-step form based on feedback, and committing to a revised prototype. In one case, a developer pointed out a subtle accessibility gap in a button contrast ratio. I ran a UserTesting session with 12 users, which confirmed a 15% drop in clickability. I iterated to AA compliance, raising conversion by 22%. I always record critiques with consent, synthesize patterns in Mural, and share a summary with the team. This approach reduces rework by 30% and builds trust, as measured by our quarterly satisfaction surveys. My rule: listen 80% of the time, ask clarifying questions, then act within one sprint cycle.

Common Mistake to Avoid

Company-Specific Variants