Complexity is inevitable.Confusion isn’t.

Nobody should need a manual for the tools they use every day. I design so they don’t, making even the most complicated products feel obvious.

View selected work

What I Do

For teams at lululemon, SAP, and MoxiWorks, I’ve designed through three recurring kinds of complexity.

01

Organizational

Systems too big for any one person to hold in their head.

02

Behavioral

Asking people to trust something unfamiliar.

03

Interaction

Dense interfaces where every detail competes for attention.

The case studies below take one each.

How I Work

Good software doesn’t become simpler by removing complexity. It becomes better by organizing complexity into systems people can understand.

Systems thinking

Organizing complexity into structures people can understand, not hiding it.

Close collaboration

Working in lockstep with Product and Engineering from problem to ship.

Rapid exploration

More directions, earlier: prototyping in hours what used to take days, then throwing most of it away on purpose.

Continuous validation

Testing decisions with real customers and iterating on what they reveal.

The result is 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.