I’ve learned that the hardest design problems rarely live on a single screen. They live in the spaces between screens—between teams, markets, policies, edge cases, and the moments where real people have the least patience for ambiguity. That’s where I do my best work: building systems that make complex experiences reliable, especially when trust and accessibility aren’t “nice-to-haves,” but the baseline.

My path toward systems thinking started with a familiar pattern: well-intentioned fixes that worked in one place, then broke somewhere else. A small variation in language would change behavior. A market nuance would invalidate a flow. A support workaround would become a permanent dependency. Over time, I realized the problem wasn’t effort—it was fragmentation. The solution wasn’t another patch; it was a foundation.

As a senior product designer, I approach reliability and accessibility like infrastructure. I define clear decision criteria early—what “good” means for users, what trade-offs we won’t accept, and what constraints we must respect. Then I translate ambiguity into reusable patterns: principles that scale, components that teams can adopt, and guardrails that prevent regressions. I focus on governance because systems only work when people can use them without me. That means documentation that’s actually read, adoption paths that fit real team rhythms, and review mechanisms that protect quality without slowing shipping to a crawl.

Measurement is part of the design, not an afterthought. When teams rely on proxy signals, they can’t see why an experience fails—only that it failed. I push for experience-level instrumentation and feedback loops that turn “something’s wrong” into actionable insights, while remaining careful about privacy and operational realities. I’ve led cross-functional alignment across product, engineering, operations, and policy by making the invisible visible: mapping risks, naming tensions, and proposing system-level moves instead of debating opinions in circles.

At the end of the day, systems thinking is a form of empathy at scale. It’s designing so that people don’t have to negotiate the product every time they use it—and so teams don’t have to reinvent clarity every time they ship.

If you’re building trust-critical products and want a designer who can turn complexity into a foundation your organization can scale, I’d love to connect. You can reach out directly or download my CV to learn more.