This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
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.
Lessons Learned by Eric Ries Monday, June 15, 2009 Why ContinuousDeployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuousdeployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
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.
Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. What started as a technical problem actually turned out to be a human and process problem. So-and-so made a mistake why did his mistake get checked in?
Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuousdeployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Code reviews and pairing Great practices.
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?
Heres my diagnosis of his problem: He has some automated tests, but his team doesnt have a continuous integration server or practice TDD. And has the tension goes down, it will be easier to get the whole team (including the MBAs) to embrace TDD and other good practices as further refinements. I'm a die hard believer in TDD.
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 continuousdeployment, youd better be able to certify that build too, which brings us to. For more on continuousdeployment, see Just-in-time Scalability. Can you make a build in one step?
I was the junior guy on a project team; I was called in to do some technicalduediligence 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.
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuousdeployment with downloads One of my goals in writing posts about topics like continuousdeployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.
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?
That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.
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.
Its had tremendous impact in many areas: continuousdeployment , just-in-time scalability , and even search engine marketing , to name a few. When operating with continuousdeployment, its almost impossible to have integration conflicts. However, a technological solution cant necessarily resolve all human root causes.
Over time, such teams either explode due to irreconcilable differences or dramatically slow down. No vanity metrics should be looked at. Even in the narrow field of giant tech companies, their early products were wildly different. Over time, such teams either explode due to irreconcilable differences or dramatically slow down.
Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. And I’ve seen companies fail the other way – the so-called Friendster effect: having a high-profile technical failure just when customer adoption is going wild.
The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.
In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Case Study: Continuousdeployment makes releases n. I know it's going to help me immensely!
And a special thanks is due to all of our presenters, panelists, and mentors. Although many of the non-technical folks in the room didnt understand what was happening in the moment, plenty of hackers were on high alert. If thats true, its primarily due to your hard work, building companies and testing new ideas. We all owe you.
That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. There would be no Microsoft, Sun Microsystems, or countless other job-creating tech companies today if early computers required corporate authorization to use.
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?
Wow, great review! Thanks for the informative review. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuousdeployment makes releases n. I look forward to reading it.
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. You can follow some of that debate here and here ; I continue to believe that this idea is correct.
Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Case Study: Continuousdeployment makes releases n. but rest assured they would be.
I continue to believe that the explosion of interest in the lean startup has very little to do with me. Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it.
Im also excited to share two long-form reviews from actual attendees. Inspiring ideas: real-time biz metrics; safe continuousdeployment; A/B split testing. Technically you argue it goes back 30 years when StorageTek was founded. Case Study: Continuousdeployment makes releases n.
Playing with new technologies. Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. The irony is that while dates early on are unreliable, continuing to create and reach for deadlines seems absolutely necessary from a motivational/productivity standpoint. Seeing whats possible.
Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world. Case Study: Continuousdeployment makes releases n. Try it, you just might like it.
Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.
for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason.
From a technical point of view, its amazing. All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. But even clicking through to see a screenshot and some reviews is incredibly time consuming, given the hundreds of apps in most categories.
Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process.
They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.
Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I joined a financial services tech startup in 1999. May 14, 2009 5:23 AM David said.
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: Continuousdeployment makes releases n.
However, it made me remember that Im tired of technology arguments. I believe that if you practice TDD, continuous integration, and active refactoring from the start, you can write maintainable code in any language. Case Study: Continuousdeployment makes releases n. January 16, 2009 2:02 PM Chrissaid.
Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. As far as I know, there are no products that are immune from the technology life cycle adoption curve. Departments were built and were even metrics-driven. We can skip the chasm. Fail faster.
I think this is one of your better posts this year, because you are addressing a risk that you face AFTER some early success, when your guard is down and you are more inclined to believe that you know what you are doing and therefore do not need to be as diligent at framing your hypotheses and how you plan to verify them.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content