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. I think Drucker said it best. Its hard to get buy in.

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

I think this idea is particularly appealing to those of us from an engineering background. 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. The solution is to change our focus from outputs to inputs.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# Constructing a working business model is a form of ecosystem design.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

MAY 7, 2009

Initially, IMVU sought to quickly build a product that would prove out the soundness of their ideas and test the validity of their business model. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. Heres the key point. And that was not a lot of fun.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

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

www.vccafe.com

MARCH 11, 2013

A group of Seedcamp entrepreneurs started a startup tools wiki for that purpose, and we thought it would be well suited here. An additional list of business resources for startups is available here. Firebase : Are all your developers front-end engineers? Google Custom Search Engine. Google App Engine.

Software Review 53

Software Review Technical Review Startup 53

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. April 23, 2010 in San Francisco.

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. Most startups arent so fortunate. March 13, 2009 11:20 PM Urs E.

San Francisco 168

San Francisco PR Lean Early Stage 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

MAY 17, 2009

There are so many engineers with bright ideas, but dont know how to start. If you are an engineer with bright ideas, consider Lean Startup to build confidence while building your startup. Identify a profitable business model faster and cheaper than your competitors. What about the rest of us? Bring your questions.

Lean 60

Lean San Francisco Continuous Deployment DC 60

Startup Lessons Learned

JUNE 21, 2010

Many startups don’t innovate at all in the product dimension, but use other kinds of innovation: repurposing an existing technology for a new use, devising a new business model that unlocks value that was previously hidden, or even simply bringing a product or service to a new location or set of customers previously underserved.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

AUGUST 16, 2010

Because the SlideShare team was used to giving away a high-value product, engineers balked at charging for a clearly imperfect product. With careful and continuous learning processes, SlideShare is inverting that idea and going to market with a validated product. That is the essence of proving the business in micro-scale.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

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

Startup Lessons Learned

AUGUST 8, 2009

I love the business model. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. We went to Eric's second workshop and have since spent a ton of time implementing lean startup practices within our company. We are really looking forward to this.one day wasn't enough! Great idea.

Lean 102

Lean Programming San Francisco Continuous Deployment 102