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.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

OCTOBER 4, 2008

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.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JUNE 22, 2009

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. Although I wish I could take credit for these pivots, the reality is that they were not caused by my singular insight or that of my other co-founders.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

SEPTEMBER 14, 2008

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. Case Study: Continuous deployment makes releases n. Most of the people building our product werent themselves target customers.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

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.

Audio 118

Audio San Francisco Video Continuous Deployment 118