I make complicated softwarefeel obvious.
Nobody should need a manual for the tools they use every day. I work on the products where that is hardest: dense, high-stakes, and used daily.
View selected workWhat I Do
For teams at lululemon, SAP, and MoxiWorks, I’ve designed through three recurring kinds of complexity.
Organizational
Systems too big for any one person to hold in their head.
Behavioral
Asking people to trust something unfamiliar.
Interaction
Dense interfaces where every detail competes for attention.
The case studies below take one each.
Case Studies
Designing Brand Governance for Enterprise Scale
How do you help thousands of agents stay on brand without relying on manual processes?
View case study
Designing a Passwordless Authentication Experience
How do you convince people to trust a sign-in method they’ve never used before?
View case study
Designing an Accessible Rail Booking Experience
How do you simplify one of the most information-dense experiences in travel?
View case study
How I Work
Good software doesn’t become simpler by removing complexity. It becomes better by organizing complexity into systems people can understand.
In practice that means I map the system before I draw a screen, and spend about as much time at a whiteboard with engineers as I do in Figma.
I build five directions when one would do, because the quickest way to find the right one is to make the other four and throw them away. Whatever survives that goes in front of a real customer before I trust it.
Software people trust on the first try, and rely on every day after.
About
I enjoy solving the kinds of product problems that don’t have obvious answers.
I work closest to the hard middle of products, where the system design, the interaction details, and the business logic all have to agree. Most days that means whiteboards with engineers and calls with customers.
Also shipped work at Microsoft (6 inventor patents), Electronic Arts, and SAP Jam.
