Remove Architecture Remove Engineer Remove Product Development Remove Vertical
article thumbnail

Vertical Markets 2: Customer/Market Risk versus Invention Risk.

Steve Blank

Steve,&# he said, “you’re missing the most interesting part of vertical markets. is whether there is a customer and market for the product as spec’d. For example, complex new semiconductor architectures, (i.e. The real risk in markets like Web 2.0 In these markets it’s all about invention risk.

Vertical 144
article thumbnail

Convergent Technologies: War Story 1 – Selling with Sports Scores.

Steve Blank

Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. Their engineers hated us.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The curse of prevention

Startup Lessons Learned

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. In this scheme, all of the data related to a specific feature of a product are stored on the same machines. In the end, they fall into three broad categories: Vertcal partitioning.

article thumbnail

Technology, Innovation, and Modern War – Class 8 – AI – Chris Lynch and Nand Mulchandani

Steve Blank

Nand changed the culture of the JAIC, bringing in Silicon Valley tools for product development, product management and for the first time a culture that focused on UI/UX, MVPs and continuous integration and deployment. Now the problem is, in the diagram below on the left, this is what our DOD architecture looks like today.