Design Systems / Email

Email Design
System

MasterClass Ongoing Role: Manager, Front-End Engineering masterclass.com ↗
40+ Components replacing one-off files
3 Awards for email design in education
45% Fewer tracked events after the schema audit
Preview

Every email in the program used to be a file - opened, copied, hand-edited. That works for a handful of sends and collapses under a full lifecycle program. It looked like a design problem for years. It was an architecture problem.

The full study covers the rebuild: design tokens and a real component library, personalization moved from copy into structure, the tooling that catches errors before a human does, the Segment and warehouse work underneath it, an LLM-backed recommendation engine built with the data team - and the organizational change that made all of it stick.

Protected case study

The rest of this one is private.

My MasterClass work covers internal architecture, tooling and numbers, so the full write-up is shared on request rather than published openly. Email me and I’ll send the passphrase - usually the same day.

No passphrase?
Request access →

One passphrase unlocks every MasterClass study on this site.