How do you turn research findings into design decisions the team actually acts on?
What the interviewer wants to hear
- Involve the team during research
- Synthesise into clear insights with evidence
- Prioritise by impact and frequency
- Link insights to design opportunities and metrics
- Share short, visual readouts and track follow-through
Model answer
I involve engineers and the product manager early, inviting them to observe sessions, because people act on what they saw themselves. After synthesis I write a small number of insights, each a clear statement backed by evidence such as quotes, clips and counts. I prioritise them by how many users were affected and how severe the impact is. Then I turn each important insight into "How might we" questions and concrete design opportunities, ideally with a metric we could move. I share a short readout, a page or a few slides with video clips, rather than a long report, and run a workshop to agree next steps and owners. Insights go into a research repository so they can be found later, and I check in a few weeks on what changed.
Can you answer it under time pressure?
Take a timed medium round and get scored on every answer.
More medium UI/UX Designer questions
- You have only one week to design a new feature. How do you include user research?
- A stakeholder gives feedback on your design that you disagree with. How do you handle it?
- How do you measure whether a design change was successful?
- Why are empty, loading and error states important, and how do you design them?
- An engineer says your design will take three times longer to build than planned. What do you do?
- How do you plan and run user interviews for a new feature?
- You are asked to restructure the navigation of a large website with hundreds of pages. How do you approach it?
- A team wants a custom styled dropdown instead of the native select. How do you make sure it is accessible?
- How do you run a design critique session that is useful rather than a debate about taste?