Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 24, 2009

The customer is known, the product is known, and all we have to do is act. The customer is unknown, the product is unknown, and startups must be built to learn. What happened when we got early press (circa 2004) in violation of our own no-PR rule. Case Study: Continuous deployment makes releases n.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

OCTOBER 16, 2013

Palantir is a deep technical play and we had a lot of code to write just to fill out the product vision that we had already validated with potential customers; it took us two straight years of development to go from early prototypes to software that could be used in production. So what was going on?

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JANUARY 12, 2009

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Add onto that the incredible amounts of infrastructure code that we reused, and we were able to bring our product to market months earlier. In most cases, simple changes are simple to make.

PHP 166

PHP Software Review Ruby San Francisco 166