At GM, I work in Design Ops on the design systems behind Buick, Cadillac, Chevrolet, GMC, Hummer, and Corvette. That means a lot of brands, model years, screen sizes, and teams pulling from the same shared source of truth.

At that scale, the work is less about drawing individual screens and more about keeping the system coherent and functioning. Most of my day-to-day work revolves around governance; which means finding the root cause when something breaks, then fixing it in the library and documentation so the issue does not keep repeating.

Across four system-wide initiatives, I helped resolve recurring issues in our shared Figma libraries, including cross-domain component behavior, mismatched icons, variables, typography, and specs that caused the same component to behave differently from file to file.

I also maintain our Display Usability Criteria documentation components in our Figma libraries. The DUC Overlay component is an integral part of in-vehicle designs. It overlays critical visual and reach criteria onto screen content so displays can be evaluated against requirements like cluster obscuration, reach, glare, reflection, and active area. Across six updates spanning four brand groupings, seven program areas, and four display contexts, I kept DUC Overlays current for instrument cluster and center-stack displays during ongoing migration efforts.

Another big part of the role is keeping the system shippable. I worked on migration and release-readiness work across our Sketch-to-Figma libraries and source files, including readiness checklists, change-log tracking, and handoff QA ahead of each cutover. When the same cleanup kept coming back, I turned it into reusable process to streamline things such as: relinking guidance, library maintenance steps, naming conventions, and tracking spreadsheets that made assets easier to find, audit, and hand off.

There’s also a quieter layer of the job that involves auditing templates, display files, and libraries before issues spread. Across eighteen items, I clarified requirements, confirmed completion, and re-scoped work so priorities stayed visible to everyone touching the system.

I wouldn't consider this the flashy part of design by any means. But it’s the work that helps a multi-brand vehicle OS feel like one cohesive system instead of fifteen.