Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
How do we know what’s the right direction [for computers to take]?
Ultimately it comes down to taste. It comes down to trying to expose yourself to the best things that humans have done, and then trying to bring those things in to what you’re doing.
Picasso had a saying: “Good artists copy, great artists steal.” And we (at Apple) have always been shameless about stealing great ideas. And I think part of what made Macintosh great was that the people working on it were musicians and poets and artists and zoologists and historians who also happened to have been the best computer scientists in the world. But if it hasn’t been for computer science, these people would all be doing amazing things in life in other fields. And they brought with them — we all brought to this effort — a very liberal arts air, a very liberal arts attitude, that we wanted to pull in the best we saw in these other fields into ours.