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

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JANUARY 28, 2009

Lessons Learned by Eric Ries Wednesday, January 28, 2009 Refactoring yourself out of business Let me start out by saying I am a big fan of refactoring , the ongoing process of changing code so that it performs the same behaviors but has more elegant structure. Its an essential discipline of good software development, especially in startups.

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 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.) And what of the product development team? Every board meeting, the metrics of success change.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

MARCH 13, 2009

Do some Customer Development instead. You have to know your business model. Most startups launch before theyve figured out what business theyre in. Hold yourself and your PR agency accountable for developing a high level of understanding of these questions ahead of time. Help you raise money. But dont be too sure.

San Francisco 168

San Francisco Lean PR Early Stage 168

Startup Lessons Learned

APRIL 18, 2010

That process involves rapid hypothesis testing, validated learning about customers , and a disciplined approach to product development. What differentiates them is their disciplined approach to determining when to spend money: after the fundamental elements of the business model have been empirically validated.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

The Next Web

AUGUST 6, 2013

They didn’t validate their business model before investing so much in it and under-estimated the “last mile” problem. Facebook does it – they push new code to their platform at least twice a day and this includes changes to their API, which has over 40,000 developers using it for building apps. Contrast this to Zappos.

Lean 132

Lean Startup Continuous Deployment Open Source 132

Startup Lessons Learned

FEBRUARY 7, 2013

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. 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.

Lean 167

Lean Entrepreneur San Francisco Agile 167

Startup Lessons Learned

JULY 15, 2010

For software companies especially, scaling distribution and development is comparatively cheap. We have to continually invent new categories of products, new platforms, and new business models – all extremely risky bets. For software companies especially, scaling distribution and development is comparatively cheap.

IPO 166

IPO San Francisco Lean Silicon Valley 166

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 8, 2009

Heres the pitch: a group of 10 companies would meet once a month for six months to develop their capacity to run lean. Each company would enroll two leaders in the series, one on the technology side, one on the business side. I love the business model. No departments The Five Whys for Startups (for Harvard Business R.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

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. That is customer development. 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Want to learn more about me?

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. So, the idea of starting without a business model is good ? It doesn't matter what business model you have thought about, in the early day. And Google?

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

SoCal CTO

JANUARY 5, 2011

Some really great stuff in 2010 that aims to help startups around product, technology, business models, etc. First Principles. Steve Blank , January 25, 2010 10 Tips for Adding Game Mechanics to a Non-Gaming Service - ReadWriteStart , September 21, 2010 Startups & VCs: Learn How to Design, Market, & Eat Your Own. -

Startup 378

Startup Silicon Valley Term Sheet Venture Capital 378