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. Thats what business is designed to do.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

APRIL 14, 2009

What matters is proving the viability of the company’s business model, what investors call “traction.&# Of course this is not at all true of many profitable small businesses, but they are not what I mean by startups.) In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 5, 2009

One way to conceive of our goal in an early-stage venture is to incrementally “fill in the blanks&# for the business model that we think will one day power our startup. For example, say that your business model calls for a 4% conversion rate – as ours did initially at IMVU.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

JANUARY 28, 2009

Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. On the one hand, I think they have an urgent problem, and need to invest 100% of their energy into finding a business model (or another form of traction). Great post, Eric.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. This presentation will empower entrepreneurs and managers to: -Identify a profitable business model faster and cheaper than your competitors.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

APRIL 18, 2010

Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation. That process involves rapid hypothesis testing, validated learning about customers , and a disciplined approach to product development.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

MARCH 13, 2009

You have to know your business model. Most startups launch before theyve figured out what business theyre in. If the product needs to be tweaked just a little bit in order to convert users into customers, you want to figure that out before the launch. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

FEBRUARY 7, 2013

Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile. Therefore, we needed a new management toolkit designed explicitly for iteration, scientific learning, and rapid experimentation.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

JUNE 21, 2010

A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty. Most businesses – large and small alike – are typically excluded by this context. Startups are designed to confront situations of extreme uncertainty.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

JULY 15, 2010

We can’t even rely on a suite of line-extension products. We have to continually invent new categories of products, new platforms, and new business models – all extremely risky bets. Comprehensive means it has to address all aspects of a startups life: marketing and product development, especially.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. Because of the cost and intensity of this program, it is designed for startups with significant venture backing or who have reached profitability. I love the business model.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

AUGUST 16, 2010

Designed for large businesses, the channels let a company share several types of documents, brand the channel with their own design elements, and then include display advertising, contest promotions, blog aggregation, social media integration and metrics reporting. That is the essence of proving the business in micro-scale.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

MAY 17, 2009

Identify a profitable business model faster and cheaper than your competitors. Continuously discover what customers want to buy before building or making follow-on investments in new features. Case Study: Continuous deployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Lean 60

Lean San Francisco Continuous Deployment DC 60

Startup Lessons Learned

JULY 9, 2009

No business model, either. All my products and ideas focus on early cash and a business model that works from the first day. You made me remember that maybe, and just, MAYBE, the early days is not at there to earn money, but rather understand your user and improve your product. What was different this time?

San Francisco 94

San Francisco Lean Continuous Deployment DC 94