Remove Advisory Board Remove Cofounder Remove Continuous Deployment Remove Customer Development
article thumbnail

A real Customer Advisory Board

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: About the author

Startup Lessons Learned

He previously co-founded and served as Chief Technology Officer of IMVU. 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. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The lean startup @ Web 2.0 Expo (and a call for help)

Startup Lessons Learned

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.

Lean 68
article thumbnail

How to listen to customers, and not just the loud people

Startup Lessons Learned

Most of the people building our product werent themselves target customers. So there was simply no substitute for seeing actual customers with the product, live. Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" Establish a customer advisory board.

article thumbnail

Embrace technical debt

Startup Lessons Learned

To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Are the engineers in the customer development team allowed to push quick and dirty "prototypes" to production?

article thumbnail

A large batch of videos, slides, and audio

Startup Lessons Learned

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.

Audio 118
article thumbnail

Pivot, don't jump to a new vision

Startup Lessons Learned

Each has its own iterative process: customer development and agile development respectively. Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. IMVU had a roughly two-month-long development cycle.