Remove Continuous Deployment Remove Product Development Remove Sales Remove Technical Review
article thumbnail

Embrace technical debt

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Technical debt works the same way, and has the same perils. I won’t pretend that there aren’t teams that take on technical debt for bad reasons.

article thumbnail

How to Get Picked as a Speaker for The Lean Startup Conference

Startup Lessons Learned

Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”). Although every organization faces some uncertainty in developing new stuff, the conditions are not always extreme.

Lean 165
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: The hacker's lament

Startup Lessons Learned

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Of course, the sales folks had new features as their #1 priority.

article thumbnail

Lessons Learned: The one line split-test, or how to A/B all the time

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

article thumbnail

The new startup arms race (for Huffington Post)

Startup Lessons Learned

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. Case Study: Continuous deployment makes releases n.

article thumbnail

Lessons Learned: The four kinds of work, and how to get them done.

Startup Lessons Learned

Playing with new technologies. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. We also try to communicate the initial due date with as few people outside our company (investors, customers, etc) as possible to avoid losing credibility.