Startup Lessons Learned

MAY 27, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, No departments The Five Whys for Startups (for Harvard Business R.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

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. Brant Cooper and Patrick Vlaskovits are among the earliest adopters of new ideas such as Lean Startup and customer development.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

APRIL 18, 2010

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. Myth: Lean Startups replace vision with data or customer feedback. Myth: Lean Startups replace vision with data or customer feedback.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

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

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. I love the business model. "Lean Startups" just jumped the shark and became consultingware, like "agile" did. August 9, 2009 10:28 AM Chris said. Great idea.

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. “But it never happened.&# [Alas, customers dont know what they want!

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

JULY 15, 2010

We have to continually invent new categories of products, new platforms, and new business models – all extremely risky bets. We have to continually invent new categories of products, new platforms, and new business models – all extremely risky bets. Expo SF (May.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

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? Expo SF (May.

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? Expo SF (May.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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

San Francisco 168

San Francisco PR Lean Early Stage 168

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.&# The amount of traditional business modeling will vary.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JANUARY 28, 2009

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). Labels: agile , product development , Test-driven development 11comments: William Pietri said. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79