Remove Architecture Remove Customer Development Remove Product Development Remove Silicon Valley
article thumbnail

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

Steve Blank

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. The answer depends on your answer to two questions: which step in the Customer Development process are you on?

article thumbnail

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

Steve Blank

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention. Order Here. Now In Print!

Vertical 147
Insiders

Sign Up for our Newsletter

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

article thumbnail

Lessons Learned: Achieving a failure

Startup Lessons Learned

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Even a great architecture becomes inflexible.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system.

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? What is customer development? No departments The Five Whys for Startups (for Harvard Business R.

article thumbnail

What would you want to tell Washington DC about startups?

Startup Lessons Learned

Much of what makes the USA, and Silicon Valley in particular, such a great place to start a company is the result of good government policy. I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens.

DC 90