My experience spans a range of industries, and each one has shaped how I think about systems. In agency work, I learned to move fast across wildly different clients and needs. In telehealth, I designed patterns that had to account for patients with a range of mental health needs, where a design decision could genuinely affect someone’s care. In white label fintech, efficiency and quality drew on tight, reusable systems that could be trusted across multiple brands without sacrificing precision.
Constraints have always sharpened my thinking. I treat them as the starting point for good systems design, not obstacles to work around. That means digging into the why behind a limitation until the right solution becomes clear. Sometimes that’s a token architecture. Sometimes it’s a governance model. Sometimes it’s a coaching conversation with a designer on my team.
I also believe no two design systems should look the same. There’s no single solution that fits every organization. So I spend real time understanding how a company already works before building anything, so the system grows in a way that’s sustainable and actually adds value.
Lately that means rebuilding systems from the token level up, so they can support AI-generated design and code without breaking consistency or accessibility. I set that direction, but the real work is getting teams to actually adopt it. That includes shaping the programs behind it with clear contribution and intake models, mentoring designers, and building shared ownership. It also means making the system easy enough to use that people choose it instead of working around it.
