Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design - designing too early what a program should do.
Criticism per se does not worry me. I've always solicited it as part of the design process.
So much in design is presented as a big miracle when it's just a repetition of what's been happening for 80 years.
With products the form is almost the finished piece, but with architecture it is not.
I mean, making simulations of what you're going to build is tremendously useful if you can get feedback from them that will tell you where you've gone wrong and what you can do about it.
I think in terms of the work we're doing now a lot of the UI cleanup... I see it getting much prettier.
I tried a dozen different modifications that were rejected. But they all served as a path to the final design.
We have an opportunity with the Model S to refine the design language, the surfacing, and all aspects of functionality.
I think, as a designer, what you have to do is challenge yourself to do what you do, but better.
I am aware of changes gradually taking place in my own designs as part of my thinking on this matter.
A small change at the beginning of the design process defines an entirely different product at the end.
I really don't over-theorize about design. I'd rather feel it than talk it to death. A lot happens as you unroll the design.
