Rapid Iteration Quotes

Learn to fail with pride - and do so fast and cleanly. Maximise trial and error - by mastering the error part.

I'm an investor in MakerBot, which is a good example of the 'thingiverse'. The idea of applying collaboration and rapid iteration to things that we interact with and hold in our hands every day is super revolutionary.

Startups are rapidly changing systems. If you use an annual review cycle, you aren't getting feedback at the same pace that you need to adapt and change the business.

In a start-up company, you basically throw out all assumptions every three weeks.

Test fast, fail fast, adjust fast.

He who makes the quickest, coolest prototypes reigns!

Get your product into users' hands as quickly as possible and incorporate the crowd's feedback to iterate. Your customers will provide the data you need to chart the best course for your company and bury any competitor that goes it alone.

Revolutionary products don't fail because they are shipped too early. They fail because they aren't revised fast enough.

There has to be a willingness to constantly accept critical feedback and rapidly iterate to make things better.

The job of a theoretical physicist is to make mistakes as fast as possible .

The way to succeed is to double your error rate.

We used to write this down by saying, 'move fast and break things.' And the idea was, unless you are breaking some stuff you are not moving fast enough. I think there's probably something in that for other entrepreneurs to learn which is that making mistakes is okay. At the end of the day, the goal of building something is to build something, not to not make mistakes.

Facebook has this famous poster that says move fast and break things. But at the same time they manage to be obsessed with quality.

Give me an entrepreneur with a lot of courage, gusto and who iterates rapidly, and I will back that person day in and day out.

My advice was to start a policy of making reversible decisions before anyone left the meeting or the office. In a startup, it doesn't matter if you're 100 percent right 100 percent of the time. What matters is having forward momentum and a tight fact-based data/metrics feedback loop to help you quickly recognize and reverse any incorrect decisions. That's why startups are agile. By the time a big company gets the committee to organize the subcommittee to pick a meeting date, your startup could have made 20 decisions, reversed five of them and implemented the fifteen that worked.

I love cities, and I love city governments in particular. But in politics it would have taken me 8 years from implementing a policy before I would get to see the feedback. With programming I could model the same policies and see the impact immediately. Technology is a far more efficient way to test.

Release early. Release often. And listen to your customers.

Being a solo founder allows you to move quickly - when you're going up against massive, entrenched competitors, you need to maximize speed and agility. Having just one person at the top allows for faster decision making.

No creator in modern times is going to stick around with a concept for 20 years. There are simply too many alternatives that writers want to pursue.

With people, if you see something you want to change, you can make the change immediately. And if that doesn't work, you can change it again half an hour later. You can't do that with a robot. They're terrible at experimenting.

The benefit of film is that you're shooting something for an intense period of time - and then it's over, and you move on to something else. In TV, you're doing the same thing over and over.

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.

I casually advise a few young companies, and I'm always surprised when I see them overthinking simple problems, adding too much structure too early, and trying to get formal too soon. Start-ups should embrace their scrappiness, not rush to toss it aside.

I basically apply with my teams the lean startup principles I used in the private sector - go into Silicon Valley mode, work at startup speed, and attack, doing things in short amounts of time with extremely limited resources.