What others say about my leadership →
Most of what determines whether a team succeeds gets decided before anyone opens a design tool: how goals connect to the business, how the team is structured relative to how the business is actually changing, and how decisions get made when priorities conflict. I build the operating models, shared goal frameworks, and team structures that fit the moment with an eye to the future rather than the org chart from six months ago. I've rebuilt this more than once, through an airline alliance integration, a company-wide restructuring, aggressive year-long M&A activity, and the aftermath of a company's dissolution. Each time, the model that worked during stability didn't survive disruption unchanged, and the work was rebuilding it so the team could keep functioning anyway.
A design system is only as durable as the organization built to sustain it. I've built four from the ground up, at a Fortune 500 company, an airline, a fast-scaling startup, and a company mid-IPO, and in every case, the hardest part was never the components. It was recruiting the right team, earning executive confidence before the system was mature enough to prove its value, and hiring for range rather than sameness so the team could scale into ambiguity. One of these systems had to be rebuilt entirely after significant team turnover. Another had to hold together through three reorganizations in under three years. Systems that only work in stable conditions aren't really infrastructure. Onboarding, career growth, and team composition are what make systems work last past the disruption that tests them, and past the person who built them.
Design organizations are being reshaped by AI faster than most operating models can adapt to it. I focus on integrating AI into product design and design operations in ways that strengthen the discipline rather than hollow it out: embedding it into documentation and day-to-day workflows, using it to expand what a smaller team can credibly own, and staying honest about where it helps and where it doesn't yet. The organizations that adapt well to AI will be the same ones with the operating discipline to adapt to anything else.
People stay and grow inside organizations that make progress legible. I build career frameworks that turn individual growth into an organizational asset: clear paths, structured feedback, and language that helps managers have real conversations about advancement. This work has to survive reorganizations and leadership changes, or it wasn't really infrastructure to begin with.
A team that doesn't trust each other won't stick around, regardless of what they're building, and that trust matters most when a team is stretched by change rather than when things are calm. I create the deliberate and informal spaces, critique sessions, cross-functional touch points, guest speakers, where trust actually forms, and I stay open to the team telling me what they need instead of assuming I already know.
Design earns influence by being clear to the rest of the business, not by asking for a seat at the table. I build the recurring rhythms, reviews, showcases, documented decision points, that let stakeholders see design's reasoning in real time, which is what actually earns trust before it's needed, particularly when priorities shift quickly.
Operations is the infrastructure most people only notice when it's missing. I keep a close eye on how work actually gets done and whether that process is visible to the people depending on it, because hidden process is usually process that's about to break under pressure.
I write and speak about the organizational work behind design leadership, the parts that don't usually show up in a portfolio. If you're building something in this space, or want a perspective for your next event or publication, reach out.
