article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.

article thumbnail

Startup Suicide – Rewriting the Code

Steve Blank

With a few more questions I learned that the code base, which had now grown large, still had vestiges of the original exploratory code written back in the early days when the company was in the discovery phase of Customer Development. Filed under: Customer Development , Technology , Venture Capital.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Ardent 1: Supercomputers Get Personal

Steve Blank

Unlike Intel chips, MIPS chip architecture also made it possible to plug in a math co-processor. Some of the other founders had sold minicomputers to scientists and engineers, but no one knew or understood the unique class of applications and customers of supercomputers. to move their applications to our unique machine architecture.

article thumbnail

Lean Meets Wicked Problems

Steve Blank

This meant the class was team-based, Lean-driven (hypothesis testing/business model/customer development/agile engineering) and experiential – where the students, rather than being presented with all of the essential information, must discover that information rapidly for themselves.

Lean 294
article thumbnail

[Review] The Lean Startup

YoungUpstarts

Such direct experiences allows one to test critical “leap-of-faith” assumptions about what customers like and dislike. Customer development (the understanding of customer needs) must be married to agile development (a process which drives waste out of product development).

Lean 193
article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? That means knowing whats written and whats not, what the architecture can and cant support, and how long it would take to build something new. Thats more than just drawing architecture diagrams, though.

CTO 168
article thumbnail

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

Steve Blank

For example, complex new semiconductor architectures, (i.e. a new type of graphics architecture, or a new communications chip architecture) mean you may not know if the chip performs as well as you thought until you get first silicon. How would that change my company strategy?

Vertical 147