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.
Both Sides of the Table
MAY 27, 2013
In this period (less than 2 years) he has brought on incredibly talented senior execs is sales, marketing, product management, client services, finance, vp engineering and more. You may know how much to pay in cash or equity for your new VP Engineering. But asking your board will keep them engaged. Between Board Meetings.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 9, 2009
It uses principles of agile software development, open source and web 2.0, 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. Expo SF (May.
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
JULY 29, 2009
The human tendency to moralize about debt affects engineers, too. I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Side-effects that reduce agility are the most damaging symptoms of technical debt.
Steve Blank
AUGUST 27, 2012
Tossing their agile development process and at times their entire business model in the air, the company would go into fire-drill mode and engineering would start working on whatever his latest insight was. Some of the engineers figuring if the founder was declaring they were toast in 90 days were updating their resumes.
Startup Lessons Learned
SEPTEMBER 14, 2008
Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Establish a customer advisory board. Expo SF (May.
Expert insights. Personalized for you.
151 
Let's personalize your content