Remove Agile Remove Architecture Remove Customer Development Remove Metrics
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. Ive attempted to embed the relevant slides below.

article thumbnail

[Review] The Lean Startup

YoungUpstarts

Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. Such direct experiences allows one to test critical “leap-of-faith” assumptions about what customers like and dislike.

Lean 193
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: Just-In-Time Scalability

Startup Lessons Learned

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

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. Labels: product development 15comments: mukund said.

CTO 168
article thumbnail

Intel Disrupted: Why large companies find it difficult to innovate, and what they can do about it

Steve Blank

As a consequence, corporations used metrics like return on net assets (RONA), return on capital deployed, and internal rate of return (IRR) to measure efficiency. These metrics make it difficult for a company that wants to invest in long-term innovation. Filed under: Corporate Innovation , Customer Development.

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.