Advisory Board Continuous Deployment Customer Development Engineer 
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. Many companies seek to involve customers directly in the creation of their products.
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. Hey Someone else who is extending the agile/lean approach beyond just developing software.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 4, 2008
In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms.
Startup Lessons Learned
SEPTEMBER 14, 2008
It required hearing customers say it over and over again for us to take a serious look, and eventually to realize that social networking was core to our business. Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. Establish a customer advisory board.
Startup Lessons Learned
JULY 29, 2009
We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. Although it costs to pay down the principal, we gain by reduced interest payments in the future. One last thought.
Startup Lessons Learned
OCTOBER 6, 2009
Or watch my full #leanstartup presentation at Seedcamp in London: And two bonus videos that are well worth watching (weally): Timothy Fitz, who worked for me at IMVU, giving an in-depth presentation on the details of the continuous deployment system that we built there. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JUNE 22, 2009
Each has its own iterative process: customer development and agile development respectively. IMVU had a roughly two-month-long development cycle. Each cycle was punctuated by a meeting of our Business Advisory Board (BAB). As the CTO/VP Engineering, I was the worst offender. Heres what it looked like.
Expert insights. Personalized for you.
151 
Let's personalize your content