Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 The three drivers of growth for your business model. Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. Ive been there: is it me or my cofounder thats crazy? Use some customer development to find out. Iterating at whiteboard !=

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

JUNE 22, 2009

Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. Although I wish I could take credit for these pivots, the reality is that they were not caused by my singular insight or that of my other co-founders.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 2, 2009

Retention cohort analysis. My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. My startup business (web development) is being shunned by virtually every other potential investor I approached thus far. Funnel averages over time. I am chugging along.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

SEPTEMBER 29, 2008

Lessons Learned by Eric Ries Monday, September 29, 2008 Q&A with an actual reader One of my favorite things about having a blog is the feedback I get in comments and by email. Question 1: When youre adding features to a product used by an existing user base, do you still do split testing to determine usage patterns?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 14, 2009

What these products all have in common is the question their minimum viable product is attempting to answer: does this product have high natural retention built-in? Take the minimum viable product , for starters. Minimum viable product is a tactic for mitigating risk. Founders struggle with this question.

Customer 156

Customer San Francisco Viral Lean 156