2002 Customer Development Design Product Development 
Steve Blank
FEBRUARY 23, 2009
This product development diagram had become part of the DNA of Silicon Valley. That’s in stark contrast to the traditional Product Development Model where it’s expected a customer is already there and waiting and it’s simply a matter of [.] familiar with Customer Development you should be.
Steve Blank
NOVEMBER 1, 2010
And they rolled all of this up into a set of financial forecasts with a “size of market” forecast from brand name management consulting firms that said they’d have 42 million customers by 2002. Second, since it knew the solution, it went into a 8 -year Waterfall engineering development process. It All Came Crashing Down.
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
MAY 14, 2009
The response so far has been nothing short of overwhelming, and I want to especially thank those of you who participated in the survey and customer validation exercise that helped shape this event. We changed our model to B2B and adopted Agile around 2002. For now, Id like to ask a favor. It was a disaster.
Startup Lessons Learned
OCTOBER 19, 2009
It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002. Read the rest. Read the rest.
Expert insights. Personalized for you.
143 
Let's personalize your content