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. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). This report is set up to tell you about new customers specifically. One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

SVPG

NOVEMBER 22, 2013

But one of the real advantages from a product point of view is that there’s no legacy to drag along, there’s no revenue to preserve, and there’s no reputation to safeguard. However, once your product develops to the point that it can sustain a viable business (congratulations!), Protect Employees and Customers.

Product 67

Product NDA Continuous Deployment Reputation 67

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. Talking to potential customers and competitors customers.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 8, 2009

Because of the extreme unknowns inherent in startup situations, we are all blind – to the realities of what customers what, market dynamics, and competitive threats. For example, a recent event I held started with a customer validation exercise (actually, this example is fictionalized for clarity). What’s happening?

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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

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

AUGUST 24, 2009

Customers will get to consume the content they want, and support the producers of that content directly, rather than having to rely exclusively on intermediaries. Now, helping potential customers discover new things they might like is the job of the discipline of marketing. There are too many products clamoring for attention.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 4, 2009

Ive previously written about the advantages of having a pathetically small number of customers , and how to get started with customer segmentation. it seemed time to return to the subject of investigating who my customers are. Thats a common pattern to gaining customer insight. Customer knows they have a problem.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 7, 2013

A few of the detailed case studies include: Tech legend Bill Gross building an MVP in 1999 to test demand for online car sales, which grew into CarsDirect.com. The Embrace infant warmer was developed - by getting out of the country -- and how Rob Emrich learned and scaled his non-profit, Road of Life. Social entrepreneurs take note!)

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

AUGUST 16, 2010

It requires separating the product launch from the marketing launch (see Dont Launch ) as well as other staple Lean Startup tactics: minimum viable product, split-testing, customer development and the pivot. Those tools, combined with focused customer interviews, have turbo-charged the company’s ability to learn.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

OCTOBER 19, 2009

Unfortunately, after months or even years of development, many companies discover that customers arent willing to buy their new wares. Thats why some entrepreneurs are trying another approach to product launches: marketing a product online before spending much on research and development or inventory.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

OCTOBER 30, 2008

Over-communicate with employees, investors, customers. This can take the form of a traditional sales pipeline or a registration-activation-revenue chart. Theres no better way to learn what customers want (or hate!). The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

FEBRUARY 28, 2009

Customers dont care if you have good metrics, only if you have a good product. And while its true that metrics sometimes can lead to a better product, in my experience just as often they had led to no insight whatsoever, like fancy reports that nobody reads or after-the-fact rationalizations (with graphs!)

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

APRIL 9, 2009

Rather than use boring section headers, I thought Id just quote from actual customers, in their own words. Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

MARCH 13, 2009

Announce a new product, start its PR campaign, and engage in buzz marketing activities. Marketing launch) Make a new product available to customers in the general public. Product launch) In todays world, there is no reason you have to do these two things at the same time. Do your customers really read TechCrunch?

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 8, 2009

I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens. Similarly, government purchasing is a frustrating series of hoops, even compared to enterprise sales.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 7, 2008

At the end of the day, the product development team of a startup (large or small) is a service organization. It exists to serve the needs of customers, and it does this by offering its capabilities to other functions in the company, and partnering with them. Case Study: Continuous deployment makes releases n.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

OCTOBER 23, 2009

Lessons Learned by Eric Ries Friday, October 23, 2009 Case Study: Using an LOI to get customer feedback on a minimum viable product How much work should you do on a new product before involving customers? But other times, the right way to learn is actually to show a product prototype to customers one-on-one.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

OCTOBER 11, 2008

Your challenge will be incentivizing your developers to create, and managing the volume of their output. How do you help customers find the best of the best? You may have to staff up a large customer service department to review and approve all of the items. And what do you do with the rest? Subscription or a la carte payments?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 16, 2008

Lessons Learned by Eric Ries Tuesday, December 16, 2008 Engagement loops: beyond viral Theres a great and growing corpus of writing about viral loops, the step-by-step optimizations you can use to encourage maximum growth of online products by having customers invite each other to join. Synthetic notifications. Organic notifications.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

JANUARY 28, 2009

They have a product that has a moderate number of customers. Its well done, looks professional, and the customers that use it like it a lot. Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MARCH 22, 2010

These companies produced over $52 billion dollars in sales in 2005, and employed 450,000 workers that year. These companies produced over $52 billion dollars in sales in 2005, and employed 450,000 workers that year. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

FEBRUARY 12, 2009

To wit: achieving product/market fit , getting customer validation , making something people want , things that matter , and of course the many excellent books on the topic, of which Ill mention just two of the best, Crossing the Chasm and The Innovators Dilemma. Is a market a set of paying customers? Tough sell.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

SEPTEMBER 11, 2009

There are many articles by many experts ( myself included ) extolling the virtues of listening to customers. In fact, there are so many of these propaganda pieces that this question might naturally cross your mind: if listening to customers is so great, why do we need so much propaganda? We did not take this step lightly.

Community 158

Community Management Lean Software Review 158