“Success is not delivering a feature; success is learning how to solve the customer's problem.”

Why it was said

Eric Ries quotes this line from Mark Cook, then vice president of products at Kodak Gallery, in the part of The Lean Startup that defines validated learning. Cook's team had been judged by how many features it shipped on schedule, and the line marks the moment he changed what counted as progress.

What it actually means

A team can be busy, on time and wrong. Shipping a feature proves only that the team can build; it says nothing about whether anyone's problem got smaller. Cook's sentence moves the finish line from the release to the evidence: what did we learn about the customer, and did their behaviour change? That shift changes the questions asked before any work starts, such as which assumption this feature tests and how we will know. It also makes a failed experiment useful rather than embarrassing, because a clear no is learning too. Ries borrows the line because it names his whole method in one breath.

How to use it

1. 1Before the next feature is scheduled, write the customer problem it should shrink and the one number that would show it did.
2. 2At the end of a sprint, report what you learned about customers before you report what you shipped.
3. 3In Istanbul, a small food-delivery team could stop counting new screens and start counting how many restaurants in Kadıköy reorder within a week.