When the brand director signed off, things started moving. I got time with Lippincott, one of our brand agencies, to help lay the foundations of the system — a grid at four breakpoints, a typography system, and an expanded color palette that finally broke free from the constraints of Pantone and CMYK values.
Then the pandemic hit. The engagement ended a week after the kickoff.
I thought I was going to lose the whole thing. Aviation didn't pause — it collapsed. Southwest, like every carrier, was in survival mode. Design systems are easy to believe in when business is good. They're a much harder sell when the company is fighting to stay solvent.
But out of the prep work we'd already done with Lippincott, and the exceptional partnership we'd built, we were able to salvage what mattered most — the color system, the typography, and the grid. It wasn't everything we'd planned. But it was a foundation. And a foundation was enough to keep going.
That's when I was connected to Vince Bratton.
Vince was a senior manager in technology with a small foundation team under him — engineers who understood reusable components in the context of React, since Vision had been built on it. But design systems as a discipline, as an organizational philosophy, was new territory for them. I was building the system and teaching the methodology at the same time, to people I was also depending on to help me build it.
We were laying philosophical and foundational groundwork. Structure. Shared language. The way of thinking about it. The engineering concept clicked early, which helped. But it was slow, and uncertain, and the business case had to be made over and over.
My argument was never abstract. Southwest's culture is built on cost discipline. So I spoke that language. Efficiency. Reduced rework. Faster delivery with fewer people. If we could do more with less, the system paid for itself.
That argument was slower to land. But it planted seeds.
Then 2023 happened.
We finally got Figma in the door, replacing Sketch, Abstract, and Zeplin in one move. I attended my first Config — Figma's annual conference — and it's hard to overstate the timing. That was the year Figma announced variables, modes, and Dev Mode from the Config stage. The tooling was finally catching up to the vision. I came back a different kind of energized.
What had been a slow burn started moving. Shortly after, I was asked to take what we'd built for responsive web and extend the system's thinking to iOS and Android. Both apps were heavily webview and hybrid at the time, which created its own challenges — but it also opened a door.
That's when the team started to take real shape. The foundation pod on the technology side became a consistent crew. A couple of native dev allies came on board. I got my first dedicated contractor. What had been a grassroots effort run mostly on conviction and borrowed time started to look, for the first time, like an actual program.
It wasn't official. But it was real.



