Startup Lessons Learned
JUNE 15, 2009
Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Startup Lessons Learned
JULY 29, 2009
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 30, 2008
What does your Chief Technology Officer do all day? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim." And what about if deployment takes forever?
Startup Lessons Learned
JUNE 2, 2010
Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much?
Startup Lessons Learned
SEPTEMBER 10, 2008
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?
Startup Lessons Learned
APRIL 29, 2013
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”). For example, when your company adds ano ther blade to its disposal razors , the product’s technical development, marketing and sales will follow relatively predictable paths.
Startup Lessons Learned
JUNE 17, 2010
I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. As a technical fix, it was brilliant. I remember one such meeting vividly. So they react in two ways.
Expert insights. Personalized for you.
167 
Let's personalize your content