Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 12, 2008

In an enterprise sales context, this is called a "repeatable and scalable sales process" - once you know how to do this, your company can graduate from early adopters and make an attempt at the mainstream. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 15, 2008

If you are trying to find a product that sells, than each test would require a different product to be created (or at least a different sales page).in This adds to the complexity of decision making since you dont know its the ad, sales page, product, keywords and so on. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

DECEMBER 7, 2008

And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Even with the highest standards imaginable, theres no way to hire just genius hackers. Hire a CTO or VP Engineering. Worst of all, your teammates are constantly wanting to have meetings.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94