Crit & feedback
Receiving design feedback as an engineer.
- Prepare work so a critique gets useful feedback
- Separate feedback on the work from feedback on you
- Turn critique into decisions and follow-ups
UX engineers show work to designers, other engineers and stakeholders all the time. Getting useful feedback, and taking it well, makes the work better and the collaboration easier.
Prepare the crit
Say what stage the work is at and what kind of feedback you need: "The layout is settled; I want feedback on the transition timing and the error state." Without a question, people comment on whatever they notice first, which is often the least important part.
Show it in the real medium. A running build, at real speed, with real data, gets better feedback than a static screenshot.
Listen for the problem
Feedback often arrives as a solution: "make it blue", "add a tooltip". Ask what's not working for them. The problem they describe is usually more useful than the fix they proposed, and there may be a better fix.
It's about the work
Critique is about the work, not about you. Take notes, ask clarifying questions, and avoid defending each choice in the moment. You can explain the reasoning later, once you've understood the concern.
Decide and follow up
Sort feedback into three groups: change it, discuss it, or decline it with a reason. Share that list afterwards so people know they were heard. Declining feedback is fine; ignoring it is what erodes trust.
Give feedback well, too
When you review design work, be specific, explain the reason, and suggest an alternative when you have one. "This button sits far from the field it submits, so it's easy to miss" is more helpful than "this feels off".
Before your next review, write the one or two questions you most want answered and share them up front. Afterwards, list every piece of feedback with what you'll do about it (change, discuss or decline with a reason), and share that list.