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. October 3, 2008 2:23 PM schubie said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 7, 2008

Lessons Learned by Eric Ries Friday, November 7, 2008 Using AdWords to assess demand for your new online service, step-by-step If you want to build an online service, and you dont test it with a fake AdWords campaign ahead of time, youre crazy. November 7, 2008 7:36 PM nitesh said. November 7, 2008 7:41 PM nitesh said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 The three drivers of growth for your business model. Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. Choose one. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. If you are attempting to apply lean startup ideas in your own business - you are not alone.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. My path to lean startups began with Kent Beck and extreme programming.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. November 13, 2008 8:59 PM eisrael said.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 7, 2008

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. Warm Regards Sean Murphy www.skmurphy.com September 19, 2008 4:35 PM Eric said. Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation. Another terrific post, Eric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. November 9, 2008 5:40 PM Chris said. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. kaChing launched a virtual portfolio management game on Facebook in January 2008 and a similar version shortly thereafter on kaChing.com.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. Just like in lean manufacturing, its generally more efficient to drive down the batch size. Please leave feedback!) Its incredibly hard to do.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. I won’t apologize for this aspect of the Lean Startup methodology. Pivot or persevere?

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" He doesnt put out crappy, buggy products and then ask for feedback. So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. October 6, 2008 9:41 PM Eric said.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

DECEMBER 8, 2008

Lessons Learned by Eric Ries Monday, December 8, 2008 Continuous integration step-by-step Lets start with the basics: Martin Fowlers original article lays out the mechanics of how to set up a CI server and the essential rules to follow while doing it. As with many lean startup practices, its getting started thats the hard part.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 Lo, my 5 subscribers, who are you? September 19, 2008 2:08 PM gmlk said. September 19, 2008 2:25 PM Eric said. Thanks again, Eric September 19, 2008 2:26 PM Eric said. September 19, 2008 2:27 PM gmlk said. September 19, 2008 2:35 PM gmlk said.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Ideas. Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. At the heart of Brant and Patricks interpretation of Customer Development is their belief that its fundamental teaching is to question assumptions.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

FEBRUARY 10, 2009

This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general. The Lean Startup Intensive is tomorrow at Web 2.0. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. The Lean Startup Intensive is tomorrow at Web 2.0.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. Another great article.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94