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

In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. Similarly, it’s easy to generate large aggregate numbers by simply falling back to non-disruptive or non-sustainable tactics (see Validated learning about customers for one example). June 8, 2009 1:16 AM Colin said.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. First of all, it means that most aggregate measures of success, like total revenue, are not very useful. Time-to-complete-a-sale is not a bad metric for validated learning at this stage. People talk about funding funding funding, bootstrapping, etc.,

Customer 167

Customer San Francisco Lean Hockey Stick 167

www.subelsky.com

FEBRUARY 25, 2010

Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system. This isnt Rails-specific, but we use SimpleDB for dumping a lot of important metrics data, like performance measurements, which we then turn into metrics.

Lean 41

Lean Baltimore Ruby Maryland 41