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

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

JULY 28, 2010

It is written using the information that the company voluntarily shared, and therefore reflects their current thinking and recollections. It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. Do you find it helpful?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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. Very good and informative.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JANUARY 12, 2010

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. I continue to believe that the explosion of interest in the lean startup has very little to do with me.

Lean 146

Lean San Francisco Wiki Startup 146

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

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

JULY 6, 2009

Before I close, let me quote just one additional bit of twitter feedback from one of the video beta-testers: bmeschke : @ ericries This is such GREAT information. Say you're not creating a product but doing a service? Slides are below: The Lean Startup fbFund Edition View more documents from Eric Ries.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

OCTOBER 4, 2008

Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. Your blogs are full of rational thoughts and has nuggets of information. It is encouraging to know someone with your reputation and connections is evangelizing truly valuable information for start-ups.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 28, 2008

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Most important slide: lessons learned Working product Key questions: what does the product do? whats the launch plan?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

AUGUST 24, 2009

Because of the incredible array of information available, we have a desperate need for filtering mechanisms. Mass blasts of information are ineffective, because the broadcast channels are suffering from information overload (even in social media). There are too many products clamoring for attention. No longer.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. Sometimes an early negative result from an experiment is a harbinger of doom for that product, and means it should be abandoned.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 19, 2009

Lessons Learned by Eric Ries Monday, October 19, 2009 Inc Magazine on Minimum Viable Product (and a response) Inc Magazine has a great new piece up about the increasing use of the Minimum Viable Product by businesses (and not just startups). Like many companies, TPGTEX rolls out new products several times a year.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Up and Running

JULY 3, 2014

If you would like to find out more about the author, the book, or about exporting in general, Laurel’s blog is an excellent source of information. We will export purple widgets to France.”. “We We will consider making other type widgets, say in red, if a customer in France is large enough to justify the change.”.

Business Plan 74

Business Plan Widget France Global 74

Startup Lessons Learned

MARCH 17, 2009

It wont even get passed the registrant information screen to even get to selecting what you want to register for. March 19, 2009 6:11 PM Anonymoussaid. website works ok - you have to select the hall pass option for $100 and put in the code - then you get it for free. Ill be there! March 19, 2009 9:03 PM Anonymoussaid. Nope, no love.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

JUNE 17, 2010

The art team would often be involved in the specification phase of a new feature, since they were responsible for the look-and-feel of the product. When the art team would review the final product, they were inevitably outraged – it deviated from the spec in ways they considered major. Here’s why.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JANUARY 6, 2012

His method advocates the creation of rapid prototypes designed to test market assumptions, and uses customer feedback to evolve them much faster than via more traditional product development practices. It is changing the way companies are built and new products are launched. For iGAP participants only. See you in Europe!

Ireland 157

Ireland North America Lean Taiwan 157

Startup Lessons Learned

MAY 27, 2009

Sorry about this being out of context but I wonder if youve read "What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services". The presentation was informative, insightful, and humorous - as you pointed out the many ridiculous assumptions we make as entrepreneurs! Thanks for an enjoyable evening.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 18, 2008

You can find out what it would take for them to adopt your product, and then follow up a week later and see if they did. Same with finding out what it would take to get them to recommend your product to a friend. I agree with the other comments, more information on yourself and what topics youll focus on would be helpful.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JANUARY 18, 2010

Continuous Flow Manufacturing is a Lean technique that boosts productivity by rearranging manufacturing processes so products are built end-to-end, one at a time (using singe-piece flow), versus the more prevalent batch and queue approach. No one wants to be solely responsible for bringing a production system down.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

MARCH 4, 2009

Today, Id like to spend some time on two techniques: the problem presentation and learning what channels of information reach customers. If this was a startup, Id be asking it of a sample of customers even more often, because getting a regular tracking result is helpful for informing your decision loop. Thats an early adopter.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

APRIL 26, 2010

Lean mindsets and methods for innovation in any company a free webinar featuring: Eric Ries April 28, 2010 at 2:00 PM EDT The "Lean Startup" is the application of lean thinking to the process of innovation in startup companies — defined as a type of business where both the problem (customer need) and the solution (product) are unknown.

Lean 113

Lean San Francisco Continuous Deployment DC 113

Startup Lessons Learned

JULY 15, 2010

My belief is that the root cause of the IPO shortage is that successful startup companies cannot find productive ways to invest large amounts of money to scale anymore. For software companies especially, scaling distribution and development is comparatively cheap. New products become commoditized too fast.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

JANUARY 24, 2010

And, in the survey that was attached, I learned a lot of useful information about how to make this blog better. I sometimes use these surveys to test new product ideas and even to engage in some customer validation. And, in the survey that was attached, I learned a lot of useful information about how to make this blog better.

San Francisco 104

San Francisco Continuous Deployment Lean DC 104

Startup Lessons Learned

MARCH 23, 2009

Lessons Learned by Eric Ries Monday, March 23, 2009 Venture Hacks interview: "What is the minimum viable product?" So, the minimum viable product is that product which has just those features (and no more) that allows you to ship a product that resonates with early adopters; some of whom will pay you money or give you feedback.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

OCTOBER 4, 2010

Lessons Learned by Eric Ries Monday, October 4, 2010 Stop lying on stage Entrepreneurs crave information about successful startups, and they should. This is the same issue we see with vanity metrics : companies are giving the appearance of sharing information while actually engaging in spin or outright deception.

San Francisco 167

San Francisco Lean Metrics PR 167

Startup Lessons Learned

AUGUST 16, 2010

First, SlideShare is a fantastic product (that I use on a regular basis) and an impressive company example of Lean Startup practices in action. If your company is using minimum viable product , you’ve probably said the same thing yourself. But I have decided to make an exception today, for two reasons.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 8, 2010

Establish baseline metrics by building the minimum viable product — the minimum required to measure the response of early adopters. Then, in each development cycle, use the insights gained by studying customers to make improvements. Consider a scenario where a team makes a product change, and the very next month page views go up.

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. Use that data to make an informed choice about whether you want to change strategies. Is it that they act as free advertising for our premium product? 8comments: Anonymoussaid. October 8, 2009 3:30 AM Anton Zolotov said.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

JANUARY 1, 2009

My challenge for the new year is getting the word out about our product (AwayFind), while of course improving on conversions, etc. I see that as a great way for my product to grow, but while Ive partnered with companies in my consulting business, its not something Im as familiar with now that Im on the product side.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 5, 2008

Youd better be able to speak their language and translate what your product does into benefits that they understand. This blog is very informative for me. And once you understand who to talk to, youll also need to know how to convince them to do what you want. 1 comments: Desoja said. I became very pleasre to read it.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Beyond their brand, I want to argue that every product contains both tangible and intangible sources of value, and that everything you buy has at least some "virtual goods" component.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

JULY 31, 2009

They may not have an open req for a specific job, but if the right amazing person walks in the door, they will always find something productive for them to do. lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

AUGUST 20, 2009

Specially because of Twitter and this information overload, I think many people have been struggling to reduce the number of RSS feeds they actually follow (it is my case), so it´ll become easier for us to keep track of your writing even if we´re not reading those blogs that often. Eric, I do think you should cross-post them here.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

AUGUST 1, 2009

He doesnt put out crappy, buggy products and then ask for feedback. My normal answer is that I dont really think thats how Apple products are built. Thats what so many techniques that I advocate are all about: customer validation , minimum viable product , vision pivots , and even throwing away working code.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. And we’ve validated that learning by being able to demonstrate that when we change the product as a result of that learning, the key macro metrics improve. Let me illustrate.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. They cant present much information, unless you take the box off the shelf and look at it. Ive also been playing around with the App Store.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74