How does your team catch when the live implementation drifts from the Figma design?
We ship every two weeks and something always changes between the design handoff and what goes live.
The padding is off. The font weight is heavier. The button color shifted a shade. The error state never got built. Sometimes it's small stuff, sometimes it's a accessibility violation that makes it to production.
Right now our process is: designer opens Figma in one tab, live page in another tab, eyeballs the difference, screenshots issues, drops them in Slack. Takes about 20 minutes per screen and happens inconsistently.
I'm curious how other teams handle this:
- Do you have a formal design QA step in your workflow?
- Is it the designer's job or QA's job or engineering's job?
- Do you use any tools for this or is it all manual?
- How do you prioritize what's worth fixing vs what ships as-is?
For context, I ended up building a tool (Driftcheck.app) to automate this for our team, upload the Figma export, paste the live URL, get a pixel diff with annotated issues and CSS fixes in 30 seconds. But I'm genuinely curious what others do since this problem seems universal.