Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. Thats when this approach can pay huge dividends. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 2, 2009

When customers are affected, try to have someone who experienced the customer problem first-hand, like the customer service rep who took the calls from angry customers. For example, a site outage may seem like it was caused by a bad piece of code, but: why was that code written?

San Francisco 164

San Francisco Lean Technical Review Software Review 164