Startup Lessons Learned

NOVEMBER 13, 2008

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. This is completely typical.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

View from Seed

MARCH 1, 2016

Investors and smart hires will always do appropriate diligence before investing money and time, but they won’t bother doing that unless they are excited about your story. Are you bringing an army of algorithm authors to attack a sleep non-technical industry? He played for the New York Yankees between 1920 and 1934.

Founder 120

Founder Technical Review Cofounder Non-Compete 120

Startup Lessons Learned

SEPTEMBER 10, 2008

Plus, as product development teams in lean startups become adept at learning-and-discovery (as opposed to just executing to spec), its clear that some bugs shouldnt be fixed. We always have to avoid that dysfunction - even the lean manufacturing greats realized that they couldnt afford to see their manual-labor workforce that way.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 15, 2008

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. Thanks for writing this article.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

DECEMBER 7, 2008

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. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. All is not lost, though.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

AUGUST 2, 2008

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. The Lean Startup Intensive is tomorrow at Web 2.0. but rest assured they would be.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

OCTOBER 20, 2008

It was my own failure to ship quality software in the early days of IMVU that really got me thinking about this problem in a new way. I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MAY 14, 2009

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 have a lot of good news to report on this front. It was a disaster.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

AUGUST 8, 2009

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. It had a pretty good technical design. That "good design" turned out to be technical debt, after all.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JANUARY 30, 2009

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.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 15, 2010

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.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 24, 2009

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. Or follow all of the New York Times columnists equally? There are too many products clamoring for attention.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 7, 2010

for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. Although much of it will sound familiar to readers of this blog, whats new is my first step towards the " new entrepreneurship " that is my goal for 2010.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 10, 2008

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. For example, take the lean dictum of working in small batches.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

FEBRUARY 11, 2009

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. The Lean Startup Intensive is tomorrow at Web 2.0. Heres my heuristic for deciding who to approach.

Software Review 68

Software Review Software Hiring San Francisco 68

www.women2.org

MARCH 8, 2012

Published on: July 13, 2011 Posted By Angie Tags: Elizabeth Knopf , Finding A Co-Founder , FounderDating , Sorced , Technical Co-Founder , Tips & Tricks. Consequently, I either needed a tech co-founder or to pay someone to develop the product. Thus, I embarked on the journey to find a technical co-founder.

Cofounder 47

Cofounder Technical Review San Francisco Founder 47

crowdSPRING Blog

MARCH 8, 2013

5 Customer Experience Metrics Every Successful Company Tracks | The Buffer blog – [link]. More founders reject VC money | Crain’s New York Business – [link]. Why Aren’t More Women Entrepreneurs in Tech Accelerators? Glaser-Harvard Business Review – [link]. People First – [link].

Social Media 105

Social Media Small Business Design Media 105

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. The United States is locked in a new arms race for that most precious resource -- the future entrepreneurs upon whom economic growth depends. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. 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. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. No vanity metrics should be looked at. I won’t apologize for this aspect of the Lean Startup methodology.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 10, 2009

Code reviews and pairing Great practices. However, hindsight indicates we forgot to do something important when developing IMVU: When the product changed, we did not update the code to reflect the new product, leaving us with piles of dirty code. The Lean Startup Intensive is tomorrow at Web 2.0. But it worked. We made it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? Expo SF (May. for Harvard Business Revie.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. So when we start checking in code more often, release more often, or conduct more frequent design reviews, we can actually do a lot to make those steps dramatically more efficient. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Im also excited to share two long-form reviews from actual attendees. In the meantime, let me keep my promise of some multimedia.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Hearpreneur

DECEMBER 29, 2021

This will help those who lost work due to the pandemic. We are successfully dominating the core markets within the Dubai Real Estate arena and our recent growth into New York, Los Angeles, and Miami is proving to be extremely successful. One of the key metrics of success in Real Estate is having a large market share.

Entrepreneur 137

Entrepreneur Social Media Employee Los Angeles 137

Startup Lessons Learned

OCTOBER 5, 2009

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.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JUNE 15, 2009

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 22, 2009

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.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 18, 2008

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. Expo SF (May.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 12, 2009

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. The Lean Startup Intensive is tomorrow at Web 2.0. January 16, 2009 2:02 PM Chrissaid. Nice article. Expo SF (May.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 16, 2009

This is a great example of lean startup thinking. Its design goals arent geared towards efficiency in terms of technical costs. The system would monitor their data and if it looked within norms gradually offer the release to a small number of new users (who had no prior expectation of how the product should work). Expo SF (May.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 11, 2009

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.

Community 158

Community Management Lean Software Review 158