Good enough beats perfect

It's really to help me combat this perfectionism because perfect doesn't exist and you should instead go with good enough because when you ship, that's the moment when you get to learn a lot from your users and you just can't anticipate it.

The biggest enemy of good enough is perfect. You don't need to be perfect. You need to be good enough in order to win the market.

Time you're planning is not the time you're shipping, and the best is the enemy of the good.

Write out the list of features that are necessary in your MVP. Cut it in half and cut it in half again and build that. Most people's natural idea of what is necessary is so laughably wrong. People are naturally off by usually one or two orders of magnitude.

Laura is discussing rapid experimentation strategy where "the first thing" refers to their embarrassing MVP solution of kicking users out of the onboarding portal to a docs page.

If it's not embarrassing, you've gone too far. Got to be embarrassing. The first thing, that was embarrassing.

Quality is not luxury. Quality is not perfection. Quality means meeting spec, and if you meet spec, you're done. If you don't think the spec is good enough, make a better spec.

When you have to make a choice, think more and ship better. Most experiments should be thought experiments.