About Me
I’ve always wanted to be an inventor. Growing up, I watched a show called ‘Beyond 2000’ — a television program about what was coming next. New technologies, new ways of doing things that hadn’t existed the week before. There wasn’t one thing I could point to and say, ‘that’s it!’ It was all of it. I wanted to understand how every piece worked — and why someone decided it needed to exist.
That instinct pointed me toward industrial design — two degrees, one grounded in user-centered research and materials and process, the other that taught me to question the first. What I kept was simpler: a designer is an empathetic generalist. Someone who understands a person, understands the moment they’re in, and makes something genuinely useful for that moment — knowing the moment will change.
That idea never left. It just scaled.
I moved into user experience design because I wanted to solve more problems, faster. First at a small studio in Austin that became the original UX arm of frogdesign. Then to the Bay Area, working across Oracle, Cisco, SAP, Informatica, VMware — enterprise systems that run operations at scale. Analytics. Financial workflows. Human capital management. Cloud infrastructure. Data integration.
The surface where people make decisions. And the systems underneath that determine whether those decisions are even possible.
Over twenty years, the work shifted — from designing interfaces to defining interaction models, from features to systems, from systems to direction across products and teams. I’ve worked as an individual contributor and as a manager. Built things alone and led teams across organizations and time zones. The titles change. The scope changes. The core of the work doesn’t.
How I work
My role is to create clarity under pressure.
I focus on making system behavior legible at the moment decisions are made — exposing state, consequence, and constraint so people can act with confidence. That usually means defining interaction models, information architecture, and reusable patterns that hold together as the system grows.
I operate with high standards and low ego. I work across design, product, and engineering to establish shared models, raise the quality bar, and keep things moving. Whether as a contributor or a manager, the goal is the same: build something that remains useful over time, not just at launch.
What I bring
Direction, not just execution — setting interaction models, patterns, and quality standards across products and teams.
Systems thinking grounded in how things actually work — not abstraction, but the operational reality of tools people rely on under pressure.
Experience at scale — platform-level design across multiple products, organizations, and the full arc from individual craft to cross-team governance.
A focus on durability — what I build should still be working, and still make sense, when the team that ships it has moved on.
Currently
I’m working across enterprise products and AI-influenced workflows — helping teams integrate new capabilities without losing clarity, control, or trust.
What doesn’t change: people have problems. Companies see unmet needs. There’s something in me that has always wanted to close that gap — to observe carefully enough, understand deeply enough, and build something that actually helps.
That’s what got me here. That’s what keeps me here.
