How might we create an embedded solution inside Figma to function as a QA assistant for designers, which is engaging, useful, and rewarding to use—and might help them see the short and long-term value in using it?
Key themes that emerged from internal interviews:
Designers trust automation when it's transparent and explainable
Inline highlights and comments are more actionable than reports
Teams need help seeing where they’ve deviated from system rules
Testing & Iteration
We ran 3 rounds of moderated usability tests with 12 designers using real design files. Several trends emerged:
Opt-In Control Builds Trust
Designers preferred to initiate audits manually rather than having them run automatically. To support this, we introduced an on-demand trigger and added optional reminders at key moments like pre-handoff—giving teams full control over when and how audits are run.
Scoped QA Improves Focus
Whole-file audits felt overwhelming and unnecessary. Designers wanted the ability to limit scans to specific frames or components. We addressed this by allowing scoped audits—letting them select exactly what to check before triggering a review.
Feedback Must Be Visual & Actionable
Designers responded better to suggestions that were visible, contextual, and easy to understand. Each flagged issue now includes inline canvas highlights, tooltips with rationale, and side-by-side comparisons with Shield-compatible components—making it easier to spot and correct issues quickly.
Manual Fixing Builds Confidence
Auto-repair introduced anxiety around unintended changes. To maintain trust, we avoided forced auto-corrections and instead offered a “Fix” button—allowing designers to preview, copy, and manually apply compliant components on their own terms.
Reflection
Challenges I faced
One of the biggest challenges was defining a problem that had long been tolerated: quiet misalignment with the Shield Design System across hundreds of teams. Rallying support for a proactive solution required shifting mindsets, not just process. I also had to balance ideal UX behaviors with real technical limits inside Figma—advocating for scalable improvements while ensuring the tool felt intuitive, respectful, and immediately useful to the teams it served.
