2002 Customer Development Product Product Development 
Steve Blank
FEBRUARY 23, 2009
This product development diagram had become part of the DNA of Silicon Valley. Were startups failing because of product failures or was there some other failure mode? a customer before you try and build a business. Is there any way to predict success or failure?
Steve Blank
NOVEMBER 1, 2010
When it was spun out as a a separate company, Iridium’s 1990 business plan had assumptions about potential customers, their problems and the product needed to solve that problem. Second, since it knew the solution, it went into a 8 -year Waterfall engineering development process. Motorola Dynatac 8000x ~1987. Lessons Learned.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JULY 30, 2009
During the same period (1987 – 1990) and I did some work at MIT under Eric von Hippel on “user driven innovation with regard to software development&# which today would probably fall under the heading of “open source software development approaches.&# No departments The Five Whys for Startups (for Harvard Business R.
Startup Lessons Learned
OCTOBER 19, 2009
Lessons Learned by Eric Ries Monday, October 19, 2009 Inc Magazine on Minimum Viable Product (and a response) Inc Magazine has a great new piece up about the increasing use of the Minimum Viable Product by businesses (and not just startups). Like many companies, TPGTEX rolls out new products several times a year.
Startup Lessons Learned
MAY 14, 2009
Through case studies, exercises, and discussions, Eric Ries will guide entrepreneurs of all stripes through the key areas that determine success for startups: product, engineering, QA, marketing, and business strategy. This workshop presents a new methodology that will allow you to bring new products -- and companies -- to life.
Expert insights. Personalized for you.
159 
Let's personalize your content