Eric Ries

In the world of software, the agile development methodologies I had practiced until that time had their origins in lean thinking. They were designed to eliminate waste too

Would it have been possible to learn the same things with less effort? Clearly, the answer is yes

We could have conducted an experiment, offering customers the chance to try something and then measuring their behavior

The more pertinent questions are “Should this product be built?” and “Can we build a sustainable business around this set of products and services?”

I come across many startups that are struggling to answer the following questions: Which customer opinions should we listen to, if any? How should we prioritize across the many features we could build? Which features are essential to the product’s success and which are ancillary? What can be changed safely, and what might anger customers? What might please today’s customers at the expense of tomorrow’s? What should we work on next

begins with a clear hypothesis that makes predictions about what is supposed to happen. It then tests those predictions empirically.

The two most important assumptions entrepreneurs make are what I call the value hypothesis and the growth hypothesis

The value hypothesis tests whether a product or service really delivers value to customers once they are using it.

For the growth hypothesis, which tests how new customers will discover a product or service

I try to push my team to first answer four questions:

1. Do consumers recognize that they have the problem you are trying to solve?

2. If there was a solution, would they buy it?

3. Would they buy it from us?

4. Can we build a solution for that problem?”