Quote

I have always believed that technology should do the hard work - discovery, organization, communication - so users can do what makes them happiest: living and loving, not messing with annoying computers! That means making our products work together seamlessly.

The problem is that at a lot of big companies, process becomes a substitute for thinking. You're encouraged to behave like a little gear in a complex machine. Frankly, it allows you to keep people who aren't that smart, who aren't that creative.

I think the best work flows out of a collaborative environment.

I describe the design process as like the tip of the iceberg. What you don't see is the long haul: all the endless auditing and things like that.

Work is a way of bringing order to chaos, and there's a basic satisfaction in seeing that we are able to make something a little more coherent by the end of the day.

It's a matter of reducing the work to its very simplest possible state, eliminating all of the things that lead away from the guts of the work, the thing the work is really about. Anything that's there must build towards its over-all organization and meaning.

I think that every project offers an opportunity to reinvent process as well as content.

Building technical systems involves a lot of hard work and specialized knowledge: languages and protocols, coding and debugging, testing and refactoring.