Bringing customer context into design quality
Using design review and customer jobs to improve product decisions.
Product quality depends on the decisions teams make before implementation. Design reviews gave teams a place to challenge assumptions, find usability problems, and spot inconsistencies while there was still time to change the work.
I used reviews to raise questions across experiment setup, zoning, dashboards, navigation, templates, and design-system components. The weekly cross-organisation format welcomed work at different stages and used silent reviews, clear questions, and focused feedback to keep discussion on improving the work.
Customer context mattered just as much. I contributed to efforts around Jobs To Be Done, use cases, journey mapping, Voice of Customer, and usability. A shared view of customer jobs across product lines could give teams a more consistent basis for prioritising work and evaluating product flows.
Together, these practices connected design critique to customer needs. They made quality a continuing part of product work rather than a final approval step.