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.&# Weve got slides , video , audio and twitter commentary.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. Expo SF (May.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Steve Blank

FEBRUARY 23, 2009

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. It’s very different than the traditional product development model.

Product Development 152

Product Development Developer Silicon Valley Product 152

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.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Steve Blank

NOVEMBER 25, 2013

Teams use the Lean Startup toolkit: the Business Model Canvas + Customer Development process + Agile Engineering. These three tools allow startups to focus on the parts of an early stage venture that matter the most: the product, product/market fit, customer acquisition, revenue and cost model, channels and partners.

Oakland 329

Oakland Incubator Lean Metrics 329