I design the infrastructure of product work: the tokens, the components, the documentation, and the contracts between design and code that let teams ship with less ceremony. My focus is scaling patterns and practices alongside the evolving needs of the product orgs I join — for internal customers who build with the system and external customers who live in the surfaces it produces.

I'm a senior design systems practitioner specializing in token architecture, scalable documentation, and AI-augmented workflows. Most recently I've been leading Apollo.io's Token Northstar — a modernization initiative built to carry the product org through its IPO-readiness transition, grounded in accessibility audits, usability research, and competitive analysis. Scope spans 18 designers, 50+ engineers, and 6 feature teams.

Before Apollo I contributed to Chewy's Chirp design system as the product org more than doubled (42 to 93 designers), and before that I formed the Slick! design system team at RealPage — a group of design system evangelists that raised consistency, adoption, and coverage across the RP Living Suite.

How I work.

I start with the contract. Before a component, there's a name. Before a name, there's a definition. I spend a disproportionate amount of time on the parts that don't render — token primitives, documentation structures, usage guidelines, accessibility specs — because systems are trust machines, and trust is built on clarity.

I lean heavily on AI-augmented workflows. LLMs are now a staple of how I draft boilerplate documentation, synthesize designer feedback, and process token mappings across legacy libraries. Used well, they compress months of migration planning into weeks — and free the team to focus on the judgment calls that still need a human.

I partner closely with engineering and brand. The best systems I've seen aren't maintained by designers throwing Figma files over a wall; they're co-owned, with a shared source of truth, a deploy story, and a visual identity that runs across product and marketing as one surface.

Philosophy.

My approach rests on four threads I try to weave into every project. User-centered design — empathy, research, interviews, and data analysis — keeps the work honest about who it's for. Story-driven design — personas and journeys — keeps the work legible to partners who don't live inside the Figma file. And qualitative user testing paired with quantitative experimentation — A/B tests, preference studies, and the analytics partnerships that make them stick — keeps the work accountable to real behavior, not to taste.

Experience.

Education.

Core competencies.