Design Systems Leader · Coppell, TX
I take Figma libraries and design tokens all the way to production code. Four systems shipped. No handoff gap. No drift.
Each system is a different org, a different stack, the same bet: tokens as the contract between design and code.
Owned the system end to end — Figma libraries and design tokens through a versioned component package engineering imports across four products.
Drove full adoption across 4–5 B2B product lines and wired design tokens into the shared component library so design and code stayed one source of truth.
Led UX for US and European retail during a headless migration, and built Ember to unify the brand’s commerce experience across regions.
Scaled Momentum from UI kits to framework-level engineering while managing a team of eight designers across B2C, B2B, and international products.
A small, live system
Choose three semantic colors, then tune the supporting tokens. The component preview updates as you go.
Contrast check
Hands-on systems design and people leadership in the same seat — governance, mentoring, and still deep on token architecture.
Color, type, and radius are contracts — not decoration. If it isn’t a token, it isn’t in the product.
Figma libraries, tokens, and production APIs are the same system. Engineers import a package. Designers don’t throw files over a wall.
A system that ships and isn’t used is a styleguide. Governance, mentoring, and component APIs are the work.