Describe a time you received critical feedback on your design work from a senior team member or stakeholder that you initially disagreed with. How did you process that feedback, and what steps did you take to understand their perspective and ultimately incorporate or address their concerns?
on-site interview · 3-4 minutes
How to structure your answer
CIRCLES Method: Comprehend the situation (feedback context, stakeholder role, project goals). Investigate the user (who is impacted by the feedback, what are their pain points/needs). Research competitive solutions (how do others address similar issues). Consider constraints (technical, business, time). Lead with a hypothesis (potential solutions). Experiment and iterate (test proposed changes). Synthesize and summarize (present revised design with rationale).
Sample answer
I recall presenting an early wireframe for a new user onboarding flow where a senior product manager felt the steps were too numerous and 'hand-holding,' advocating for a more streamlined, self-discovery approach. My initial reaction was that the current design provided necessary guidance for novice users. To process this, I applied the CIRCLES Method. First, I Comprehended the feedback by asking clarifying questions about their underlying concerns regarding user drop-off and their vision for user autonomy. I then Investigated the user data, reviewing analytics on existing onboarding completion rates and common points of friction. This led me to Research competitive solutions, observing how other successful platforms balanced guidance with exploration. Considering our project Constraints (tight timeline, limited dev resources), I developed a hypothesis: a hybrid approach, offering optional guided tours while allowing immediate exploration. I then Experimented with two variations in low-fidelity prototypes. Synthesizing my findings, I presented a revised flow that reduced initial mandatory steps by 30% while still offering contextual help, which the product manager enthusiastically approved, aligning with both user needs and business goals.
Key points to mention
- • Demonstrates active listening and open-mindedness to feedback.
- • Shows a structured approach to processing and incorporating criticism (e.g., using a framework like CIRCLES or STAR).
- • Highlights the ability to balance personal design vision with team/stakeholder input.
- • Emphasizes data-driven decision-making and iterative design.
- • Illustrates problem-solving skills and a commitment to user-centric design.
Common mistakes to avoid
- ✗ Becoming defensive or dismissive of feedback without understanding its root cause.
- ✗ Immediately agreeing to change the design without critical evaluation or seeking further clarification.
- ✗ Failing to articulate the original design rationale.
- ✗ Not following up to ensure the incorporated feedback actually solved the perceived problem.
- ✗ Focusing solely on personal preference rather than user needs or business goals.