I’m a Senior Product Designer and UX Architect with 20+ years of experience building enterprise-scale digital products — the kind where the stakes are high, the systems are complex, and the margin for bad UX is essentially zero.
My deepest domain expertise is healthcare: clinical workflows, health insurance platforms, revenue cycle management, and care delivery infrastructure. I’ve shipped work inside Epic-integrated environments, co-authored published clinical research presented at ASPHO 2024, and spent enough time with billing specialists, clinicians, and insurance coordinators to know that healthcare UX fails most often not because of bad design taste, but because of insufficient domain knowledge on the design side.
That said, the problems I’m drawn to aren’t exclusive to healthcare. Platform unification — bringing a fragmented suite of products or services into a coherent, governed system — is where I’ve done some of my most meaningful work. At Keysight, that meant a cross-product design system spanning 200+ hardware and software instruments, built in partnership with Georgia Tech’s research program. At Anthem, it meant a division-wide design system serving Medicare and Government Retirement products. The pattern is consistent: large organizations with inherited complexity, needing someone who can hold a system-level view while staying close enough to the user to know when the system is failing them.
I work across the full research-to-delivery cycle. I’ve run ethnographic research, facilitated focus groups, designed and tested high-fidelity prototypes, written interaction standards, mentored design teams, and presented findings to executive stakeholders. I’m certified in Epic (CLN102) and CITI Human Subjects Research, which matters in regulated environments where design decisions carry real liability.
More recently, I’ve been integrating AI tooling — Claude, Lovable.dev, Figma’s AI features — into my design and prototyping workflow. Not as a novelty, but as a genuine acceleration layer. The quality of what comes out is still bounded by the quality of domain knowledge and design judgment going in. That part hasn’t changed.
How I got here
I came into UX sideways, the way most people of my generation did. I was writing HTML during the late-90s dot-com era without a clear sense of direction, until a co-worker handed me Edward Tufte‘s work and something clicked. The question of what goes where and why — not aesthetically, but structurally and functionally — turned out to be a question I couldn’t stop asking. Library science friends introduced me to information architecture. The rest followed from there.
My background before design includes a stint as a title examiner in real estate transactions — which, as it turns out, is excellent preparation for reading complex systems, tracing dependencies, and caring about whether the handoff between steps actually works.