“Define what the product will do before you design how the product will do it.”

I’m an ‘evolve or die’ kind of a musician. I think it’s cool to try new things.

There’s only one thing you can use against pure logic, and that’s common sense.

If you are not going to produce albums then you are not going to produce new fans. It’s impossible.

I’m a huge believer in putting music out as quickly as early as possible.

It’s harder than you might think to squander millions of dollars, but a flawed software development process is a tool well suited to the job.

Keep it simple: In general, interfaces should use simple geometric forms, minimal contours, and a restricted color palette comprised primarily of less-saturated or neutral colors balanced with a few high contrast accent colors that emphasize important information.

We don’t fight about music. We don’t fight about artistic direction.

Form follows function straight to hell.

A powerful tool in the early stages of developing scenarios is to pretend the interface is magic.

We seem to be keeping old fans and are bringing on new fans that are teenagers. I think that is amazing.

My computer’s memory stores a million phone numbers with perfect accuracy, but I have to stop and think to recall my own.

No matter how beautiful, no matter how cool your interface, it would be better if there were less of it.

Design principle: Take things away until the design breaks, then put that last thing back in.

If your persona has goals and the product has magical powers to meet them, how simple could the interaction be? This kind of thinking is useful to help designers look outside the box.

Just how do I design if not with prototyping? An excellent question. The short answer is ‘on paper.’

Typography should not vary widely in an interface.