2008 Advisory Board Continuous Deployment Metrics 
Startup Lessons Learned
OCTOBER 26, 2009
Lessons Learned by Eric Ries Monday, October 26, 2009 A real Customer Advisory Board A reader recently asked on a previous post about the technique of having customers periodically produce a “state of the company&# progress report. One example is having a real Customer Advisory Board.
Startup Lessons Learned
OCTOBER 4, 2008
Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. October 13, 2008 6:47 PM Luke G said. December 4, 2008 4:43 PM Valto said. Case Study: Continuous deployment makes releases n.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 9, 2009
If youre interested in being part of my "customer advisory board" for this presentation, please get in touch. Eric, if youre looking for any help as a "customer advisory board", Id love to do anything I can to help. I would love to be on your advisory board. And thats where the call for help comes in.
Startup Lessons Learned
SEPTEMBER 14, 2008
Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Establish a customer advisory board. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JUNE 22, 2009
Each cycle was punctuated by a meeting of our Business Advisory Board (BAB). Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment? It was painful.
Startup Lessons Learned
OCTOBER 11, 2009
Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. Any team that creates an experiment must monitor the metrics and customer reactions (support calls, forum threads, etc) while the experiment is in-progress, and abort if something catastrophic happens. It promotes rapid iteration.
Startup Lessons Learned
OCTOBER 5, 2009
If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. Case Study: Continuous deployment makes releases n. We can also ask: how would we fix the problem if it does occur?
Expert insights. Personalized for you.
151 
Let's personalize your content