Rebuilding the Dow Jones design system from React-only to universal — twenty brands, five platforms, reimagined from first principles.
Kevin Muldoon · Design Systems Architect · Farther
1
Before We Begin
I work at the seam between design and code.
I’m Kevin Muldoon — a design-systems architect working across visual design, production engineering, and information architecture. I architected the Dow Jones Design System, host the Design Systems Rodeo podcast, and build open-source tooling like Genome.
What follows is highly compressed — years of problem-solving at Dow Jones, distilled. Less a tour of screens than the way I approached the work.
2
The 11 PM Problem
Right now, someone is rebuilding a new date picker for the fifth time.
It belongs nowhere but that one screen — a copy-paste one-off, tweaked just enough to ship — and somewhere a design-systems person dies a little. But the usual cure is worse than the disease: if fixing it means filing a ticket to touch the system, the tax outweighs the mess.
I’ve been on both sides of that fear. Here’s what I learned actually makes it better.
3
The Only Job
A System Has One Job: Make Life Easier.
The moment it introduces a rule or a ceremony that adds more work than it removes, it has lost the game. Everything that follows is in service of that one test — and most of what people call “governance” fails it.
4
The Real Metric
You don’t measure it by how many components you built.
You measure it by adoption — the Token-First strategy: a token counts only when every platform has it.
1,467
tokens defined
×
5
platforms
×
20
brands
=146,700correct values, compiled from one source — none maintained by hand.
The ×5 was mine. Before me it was ×1 — React-only, 29,340 values. Same tokens, five times the reach.
Start with the palette, then expand outward — never all at once. The real product is the cognitive load you removed.
5
What To Let Pass
Some components aren’t meant to be tamed.
The date picker is the worst example a design system ever adopted — every workflow wants a different pattern, and mobile is a different UI entirely. Governance isn’t a two-week ticket queue. It’s the judgment to know what to standardize, what to let pass, and what just needs to ship tomorrow. Without it, the loudest voice wins.
Date picker
let pass
File upload
standardize
Data table
standardize
Notification
standardize
Filter menu
standardize
Pagination
standardize
6
Servant Leadership
Call us. We’ll help you ship it.
At Dow Jones — twenty brands to serve from one white-label system — the design-system team worked as production artists and advocates, never gatekeepers. My roots are in print and retouching, where the whole job is making the person downstream’s life easier. Office hours, outreach, ethnography, every day. You know it’s working when people start calling you.
Office hours
a standing open door
›
Outreach
we come to you
›
Ethnography
watch the real work
›
They call you
the signal it’s working
7
Move The Win
Win at the Token. Not the Component.
A determined designer will always roll their own at 11 PM. So don’t fight the component battle. Move the definition of a win: build whatever you need — if it sits on our primitives, we’ve already won. No mandate email. No enforcer. The system wins by default.
8
Craft & Tooling
One token becomes every platform.
Permeation only works if a token is effortless to consume. A Figma Variable holds the intent; a custom Style Dictionary pipeline compiles that one definition to SCSS, NewsKit, SwiftUI, Compose, and email. A designer names the decision once — and it ships, unaltered, to every surface. No hand-translation, no drift at the boundary.
Identical structure — only the tokens change. Real UDS values, three of twenty brands.
10
What Actually Happened
I took Dow Jones from React-only to universal.
It began as a web-and-React design system. I re-founded it on first principles — tokens as the source of truth, a CTI+ taxonomy — and scaled it into a universal one: twenty brands across five platforms, all drawing from a single source. A change made once reached every brand, on every platform. Duplicate bugs were caught before release; dual licenses fell away.
The win wasn’t components. It was the cognitive load that disappeared.
Not a metric anyone handed me. An architecture I can defend.
11
The Smallest Unit
The deepest version of “make the right choice the easy choice” lives in a single number.