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. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

YoungUpstarts

NOVEMBER 20, 2013

by Dan Adams , president of Advanced Industrial Marketing and author of “ New Product Blueprinting: The Handbook for B2B Organic Growth “ Right now our economy and our nation feel anything but business-friendly. Innovation isn’t about flinging products willy-nilly against the wall to see what sticks.

Product 251

Product B2B Product Development Developer 251

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. (See

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

APRIL 4, 2010

Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Take a look and let me know what you think. Take a look and let me know what you think. Amazon PostRank

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 22, 2008

You get increasing growth by optimizing the viral loop , and you get revenue as a side-effect, assuming you have even the most anemic monetization scheme baked into your product. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

APRIL 29, 2013

Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. 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”). in ten years?

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. Five Whys has its origins in the Toyota Production System. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 20, 2008

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. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." Whats wrong with this picture?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Amazon PostRank

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. Similar results apply in product management, design, testing, and even operations. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

My biggest thanks goes to the people who generously sponsored scholarships for others to attend the dinner and workshop, Thank you so much! ericries : special thanks once again to @fancy_free and @KISSmetrics for sponsoring scholarships for the #leanstartup workshop in Boulder. Revisiting the Software Design Manifesto (and what.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 2, 2008

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JULY 30, 2009

On August 20th, Eric is leading a half day in-depth workshop on the Lean Startup. A very limited number of tickets are also available for this workshop. A discounted price is available for early stage entrepreneurs and students. This is a great chance to really go deep on some of the concepts behind building Lean Startups.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: product development 15comments: mukund said. Have you worked with or for a great CTO?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months. What’s going on?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. The temptation is try and build a toolkit of general pieces, which can be assembled into many kinds of final product. The basic idea is to avoid building something based on what you think it might need to do in the future. Amazon PostRank

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

AUGUST 8, 2009

One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. So the product development team was busy creating lots of split-tests for lots of hypotheses.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JUNE 12, 2009

Lessons Learned by Eric Ries Friday, June 12, 2009 Lean Startup Workshop scholarship program I havent had much time to write lately, and so havent been able to share much about the Lean Startup Workshop series I have been producing with OReilly in their Master Class division. Thank you all. Thats why Im so excited about this format.

Lean 60

Lean Programming San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Amazon PostRank

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Amazon PostRank

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 2, 2008

Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Take a look and let me know what you think. Take a look and let me know what you think. Amazon PostRank

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Customer development. This speeds up the Ideas-Code-Data feedback loop. Im sure youve noticed this yourself.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JULY 6, 2009

Say you're not creating a product but doing a service? Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Labels: events , slides , video 7comments: Eemo said.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. that we learned different.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 17, 2008

If you dont have customers, a product, investors, or a board of directors, you can pretty much stay focused on just one thing at a time. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Take a look and let me know what you think.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Please register to attend this event as space will be limited.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Austin Startup

MARCH 17, 2017

How do we build products/solutions that engage the customer and deliver an amazing experience? Engineer the experience so you can evolve the product. The entire organization has to be on the same page and needs to work together — from the birth of the idea to the actual delivery of better products. A VR experience?

Texas 54

Texas Software Engineering Austin Engineer 54

Startup Lessons Learned

JANUARY 7, 2010

Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Take a look and let me know what you think. Take a look and let me know what you think. Amazon PostRank

San Francisco 119

San Francisco Management Continuous Deployment Lean 119