Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JUNE 5, 2009

It’s entirely possible for the startup to be a massive success without having large aggregate numbers, because the startup has succeeded in finding a passionate, but small, early adopter base that has tremendous per-customer behavior. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. First of all, it means that most aggregate measures of success, like total revenue, are not very useful. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

FEBRUARY 22, 2010

Two others – that each team member give their input independently and that the results be objectively aggregated – are also key parts of building a meritocracy. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 14, 2009

In an ecosystem, each participant acts according to its own imperatives, but these selfish actions have an aggregate effect. This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151