femke.design on YouTube · Open on YouTube
Senior product design: owning outcomes · Proficient · Lesson 65 of 99 · 10 min video, then about 2 hours of practice
Design QA and shipping to production quality
After this you can run a structured design QA pass on a build, file issues engineers can act on, and decide which defects block launch.
Why it matters
Owning an outcome means owning what actually ships, not what was in the Figma file. Design QA is a review of the built product against the design and its intent: states, edge cases, responsive behaviour, content, accessibility, motion. The senior part is triage: separating launch-blocking defects from polish, filing issues with screenshots and expected behaviour, and pairing with engineers rather than handing them a list. Trap: discovering problems after launch because QA was a single pass on the happy path the day before release.
How to use this resource
A working designer's actual QA process with engineering: when it happens, what gets checked, how issues are filed and prioritised. Published 2020; the process has not changed, only the tools around it.