Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. It usually looks like this: the can-do attitude and high-bandwidth communication that characterized the first few iterations have produced magic. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MARCH 4, 2009

Your writings are so very thought provoking, and now reading them will take a slice of my ever diminishing bandwidth. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Dear E, so good to come across this. I had wondered about your whereabouts :-).

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 16, 2009

Then we could render the whole site with much less latency, bandwidth usage, and server cost. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? It would be a lot more efficient to send down a compressed packet with the entire sites data and presentation in an optimized format.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Steve Blank

MAY 9, 2017

The second thing that’s changed is that we’re now Compressing the Product Development Cycle. In the 20 th century startups I was part of, the time to build a first product release was measured in years as we turned out the founder’s vision of what customers wanted. We now have specific management tools to grow startups.

Restful 222

Restful Silicon Valley Puerto Rico San Jose 222