Quotes About Iteration

If you are not embarrassed by the first version of your product, you've launched too late.

the value of prototyping: Potential users of ideas are more comfortable sharing their honest reactions when it's rough

All of the things we learned on 'Coraline' we applied to 'ParaNorman,' and all of the things we learned on 'ParaNorman' and 'Coraline' we applied to 'The Boxtrolls.'

One of the Scrum rules is that work cannot be pushed onto a team; the Product Owner offers items for the iteration, and the team pulls as many as they decide they can do at a sustainable pace with good quality.

Organizations want small changes in functionality on a more regular basis. An organization like Flickr deploys a new version of its software every half hour. This is a cycle that feeds on itself.

When you make an animated film, you make it over and over and over. We almost do ten versions of the film.

Somebody like a Piggy or a Kermit, there needs to be several versions and so there will be several of them.

At Pixar, we do a million versions of the movie, and every one of them goes through their awkward teenage phase where it's terrible and doesn't make sense, and we just keep working on it.

'Paranormal Activity' had fifty versions because it was $250 to reshoot. We'd screen it, see one thing wrong, shoot for an hour, fix it, and then screen it again. You don't have to be disciplined about it. On a regular movie, you have to screen it and think of every problem, reshoot for three days and solve every problem, and then you're done.

Whether it's with a 'Metroid' experience or a 'Donkey Kong' experience, we're constantly looking to push the envelope on the IP versus doing sequential small iterations with a particular franchise.

What if we had a chance to do it again and again, until we finally did get it right? Wouldn't that be wonderful?

Paris has long been a palimpsest of different cities, each new iteration grafted on top of the still visible last, spanning the extremes of human excellence and beauty and, just as crucially, filth and squalor.

It is an iterative process that goes something like this: * Screen it * Discuss it * Get the feeling that you don't know what you're doing * Weep openly * Tear it apart * Correct it * Re-board it * Rebuild it * Screen it again * Repeat as necessary

The best design tool is a long eraser with a pencil at one end.

The design process is about designing and prototyping and making. When you separate those, I think the final result suffers.

The habit of calling a finished product a Design is convenient but wrong. Design is what you do, not what you've done.

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

We should not try to design a better world. We should make better feedback loops.

Every record I do is a learning process for how I want to do the next one.

Generally, our first idea of what our business is going to be is not the right one. It takes a few iterations; to get there, you have to be able to let go.

Even if the first versions of a product are well done, human-centered, and focused upon real needs, it is the rare organization that is content to let a good product stay untouched.

Feedback is several orders of magnitude more important in product development than it is in manufacturing.

What kind of programmer is so divorced from reality that she thinks she'll get complex software right the first time?

Do it, fix it, try it.