Product Iteration Quotes

You may be trying to drive in a particular direction that people don't necessarily understand at first. In our case, we knew the users we had in mind for this product. So in the early days, we looked at our customers, really just testers at that point, and we paid extra attention to the teams we knew should be using Slack successfully.

I've long believed that if you're not embarrassed by your first product release, you've released too late.

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

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.

The Googly thing is to launch products early on Google Labs and then iterate, learning what the market wants - and making it great. The beauty of experimenting in this way is that you never get too far from what the market wants. The market pulls you back.

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

Get the 1.0 out as soon as possible...even if it sucks.

Once your product is working, switch from not caring about this to caring about this a little bit.

In their infancy, startups need geniuses who fit their current tight-knit culture and will iterate quickly as they push towards an ambitious vision - and they need a scaffolding of advisors, strategists, early users, and product-thinkers around these savants to guide them.

Before product/market fit, your only job that matters is to build a great product.

Because Techstars is an intensely productive three-month program in which product development and iteration are primary goals, we're constantly looking to streamline our program to help entrepreneurs avoid recurring obstacles.

We're on the brink of the next industrial revolution. Instead of buying things, you can make them on a printer. When you have a 3D printer, you can iterate more - what used to take months, now takes hours.

The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.

In our product development cycle, we ask and listen to our customer about what she wants.

The most important thing in startups is getting a product to market, as imperfect as it may be, and then iterating on it and continually making it better. A first rev of a site that has a few typos may not be perfect, but it was the start of something that I deeply believed in.

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

One of the hard parts about building a service that you use yourself is that it's easy to forget what it was like the very first time someone signs up. Every once in a while, I'll create a brand new account and give it a try and see how hard it is to find things that I really love, see if I'm using it or thinking about it differently.

You've got to stay super focused on shipping product. There isn't a version two or three if there isn't a great version one.

Original visions are often wrong. Companies have to morph as they learn what customers don't want.

Get a minimum viable product out there, test it out, see how customers respond.

If I look at my own growth, I started in product design. And we grew and created new products, and we were also able to change the idea of design a few times.

What that means initially is that you have alot of products that are only slightly better games in the same genre on another machine - and the titles that really take advantage of the machine come along later.

It only took me two weeks to build the first version of Facebook because I had so much stuff before then.