Categories

There’s no single approach to product strategy that is ideal for everyone, and you can never know how things might have gone if you sequence your product work differently.

…the purpose of product discovery is to make sure we have some evidence that when we ask the engineers to build a production-quality product, it won’t be a wasted effort.

Much of the key to effective product discovery is getting access to our customers without trying to push our quick experiments into production.

Customers don’t know what’s possible, and with technology products, none of us know what we really want until we actually see it.

We need to [validate our ideas] before we spend the time and expense to build an actual product, and not after.

…we need to embrace product discovery as the most important core competency of the startup.

If you find your customers using your product in ways you didn’t predict, this is potentially very valuable information.

…landing pages are incredibly important to bridging the gap between expectations and what the product does.

One of the biggest possible wastes of time and effort… is when a team designs and builds a product, yet, when they finally release the product, they find that people won’t buy it.

…qualitative testing of your product ideas with real users and customers is probably the single most important discovery activity for you and your product team.