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. for Harvard Business Revie.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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

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

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. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. for Harvard Business Revie.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

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. for Harvard Business Revie. Their initial users were super early adopters who were willing to trade quality for access to new features. Amazon PostRank

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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. for Harvard Business Revie. Most startups arent so fortunate.

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

JUNE 21, 2010

I prefer to take the most expansive possible definition of product, one that encompasses any source of value for a set of people who voluntarily choose to become customers. This is equally true of a packaged good in a grocery store, an ecommerce website, a non-profit social service or a variety of government programs.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

MAY 17, 2009

Identify a profitable business model faster and cheaper than your competitors. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? for Harvard Business Revie.

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. for Harvard Business Revie.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

AUGUST 16, 2010

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. Well see if the marketing launch results follow the predictions of SlideShares validated business model. for Harvard Business Revie.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167