Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? Products can find sources of validation with impressive stats along a number of dimensions, such as high engagement, viral coefficient, or long-term retention. Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Instead of these dead-ends, use the problem and solution team framework and then: pivot, dont jump.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

DECEMBER 16, 2008

I wrote about this challenge for iPhone developers, in an essay on retention competition : the battle over what icon the user will click when they go to the home screen. Our theory is that the key to long-term retention is creating an engagement loop where the reactivation rate exceeds the rate of fatigue. What do they get out of it?

Viral 140

Viral San Francisco Lean Continuous Deployment 140