Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can easily take from it whatever makes sense for your business, and leave the rest. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Steve Blank

MARCH 3, 2015

It has replaced how to write a business plan with hands-on Lean Startup methods. Traction and evidence from customers were what investors were looking for – even in “slow” sectors like healthcare and energy. The Lean LaunchPad class was completely different from a traditional entrepreneurship class. Today the U.C.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

Startup Professionals Musings

JANUARY 12, 2018

The “valley of death” is a common term in the startup world, referring to the difficulty of covering the negative cash flow in the early stages of a startup, before their new product or service is bringing in revenue from real customers. Consider licensing your product or intellectual property, and “white labeling.”

Intellectual Property 134

Intellectual Property Technical Review Startup Incubator 134

YoungUpstarts

JULY 23, 2017

As a result, we need to give our little startups as much chance as possible to grow into healthy product and service shipping machines. This is where keeping your startup lean comes in. A lean startup only spends money on things it absolutely needs. If you fail to meet expectations your customers can provide feedback.

Lean 193

Lean Startup Salary Programming 193

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Up and Running

JULY 6, 2016

For plans and pitches, we look for the patents, customer testimonials, and backgrounds and achievements of the team as validators. We want to see those for sure, and we expect good summaries as part of the business plan discussion of product-market mix, or company background (in either section, whichever seems better to the founders).

Technical Review 72

Technical Review Software Review Business Plan Development Team Review 72

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Hence, cutting corners often paid huge dividends.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

JANUARY 6, 2014

Agile is a tremendous advance in reducing time, money and wasted product development effort – and in having products better match customer needs. But businesses are finding that Continuous Deployment not only changes engineering but has ripple effects on the rest of its business model.

Continuous Deployment 331

Continuous Deployment Customer Agile Cloud 331

A Smart Bear: Startups and Marketing for Geeks

APRIL 5, 2010

When we demand overwhelming customer outcry before committing to the slightest product change, we're in danger of losing the value of creating a cool feature that takes too much effort but people just love. We're "lean" but we're not stirring hearts. Customers generally prefer the right features over more features.

Software Review 226

Software Review Metrics Lean Algorithm 226

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Read the rest of The Five Whys for Start-Ups. Expo SF (May.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 5, 2008

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does. This post has been removed by the author.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. We finally settled on a $1.99

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. If we accept the verdict of customers instead of pundits, I think these claims are easy to dismiss.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 4, 2008

So if youre new, consider not paying any attention to the rest of this post, and just diving into the archives, if you havent already. Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Ive founded and self-funded a (lean) startup on my own.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 14, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference, who has created content for a number of startups. In our ongoing exploration of how people actually implement Lean Startup methods in their workplaces, we’re asking practitioners to share their techniques. But this is where the notion of "lean content" comes into play.

Lean 167

Lean Conversion Audience Design 167

Startup Lessons Learned

JANUARY 7, 2010

My most recent startup created a marketplace for customers to buy and sell virtual goods for their 3D avatar. Read the rest at The Conversation - Harvard Business Review. My most recent startup created a marketplace for customers to buy and sell virtual goods for their 3D avatar. Expo SF (May. . Expo SF (May.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. Talking to potential customers and competitors customers.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 2, 2008

but rest assured they would be. 0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. Read the rest here. Read the rest here. For a little while, the team can resort to the last defense of entrepreneurs in trouble: the promised hockey-stick.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Steve Blank

JULY 30, 2009

Your Customers are Not Who You Think For years I thought this “million unit chip sale by accident&# was a “one-off&# funny story. That is until I saw that in startup after startup customers come from places you don’t plan on. Your board nods sagely at your target customer list.

Silicon Valley 143

Silicon Valley RSS California Customer Development 143

Steve Blank

NOVEMBER 11, 2014

In the 20 th century corporate skunk works were used to develop disruptive innovation separate from the rest of the company. ——– In the 20 th century companies could be leaders in a market for decades by just focusing on their core product(s). They were the hallmark of innovative corporations. Lessons Learned.

Channel 292

Channel Customer Development Distribution Restful 292

Up and Running

SEPTEMBER 28, 2015

The word kanban means “signboard” or “billboard” in Japanese, and it’s a concept most commonly applied to “lean” or “just in time” production. Kanban is a scheduling system for “just in time” production. Scrum: a flexible way to manage product development. Supply only what is needed when it is needed.

SCRUM 60

SCRUM Japan China Agile 60

Startup Lessons Learned

AUGUST 24, 2009

But, as any startup can tell you, this opens up a tremendous set of opportunities for the rest of us. Customers will get to consume the content they want, and support the producers of that content directly, rather than having to rely exclusively on intermediaries. There are too many products clamoring for attention.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. Things started to slip.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

FEBRUARY 22, 2009

We spent the rest of our time pretending to work on the assigned homework, but really trying to do interesting side projects, like sending juvenile messages across the school network or building primitive video games. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. .

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JANUARY 2, 2009

For the rest of us, there is an alternative: to create credibility by building a lean startup. At IMVU, we were terrified by how early we shipped (and charged for) our first product. The core of the article is my first attempt to articulate the key metrics (in graph form) that I believe demonstrate customer value.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Steve Blank

MARCH 11, 2015

They’ve found product/market fit (what products customers want to buy). They’ve learned the best distribution channel to get the product from their company to the customer. and how to price the product. for new product development that emphasize immediate returns. Lessons Learned.

Widget 120

Widget Lean Business Model Metrics 120

Startup Lessons Learned

SEPTEMBER 10, 2008

Heres my favorite part: If youve got a team, part of the team should obsess about the backlist, honing it, editing it and promoting it, while the rest work to generate (as opposed to promote) the frontlist. You have customers, they are using your product, and you are trying to help them. But then what? And polish them more.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

APRIL 12, 2010

Lessons Learned by Eric Ries Monday, April 12, 2010 The Lean Startup Intensive at Web 2.0 So I am particularly excited that the Lean Startup is a big part of this years Web 2.0 And for those who want more than just the overview, were offering the Lean Startup Intensive on the first day of the conference: May 3, 2010.

Lean 129

Lean San Francisco Web Continuous Deployment 129

Up and Running

FEBRUARY 12, 2022

Learn why the traditional way of writing a five-year business plan is often a waste of time and how to use a Lean Plan instead for smarter, easier strategic planning to establish your long-term vision. They have to have some degree of faith and certainty about what customers are going to want in the future. Develop your Lean Plan.

Business Plan 83

Business Plan Lean Forecast Exit Strategy 83

Startup Lessons Learned

MARCH 4, 2009

Ive previously written about the advantages of having a pathetically small number of customers , and how to get started with customer segmentation. it seemed time to return to the subject of investigating who my customers are. Thats a common pattern to gaining customer insight. Customer knows they have a problem.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

OnlyOnce

AUGUST 12, 2013

Outside In: The Power of Putting Customers at the Center of Your Business , by Harley Manning and Kelly Bodine from Forrester Research, was a good read that kept crossing back and forth between good on the subject at hand, and good business advice in general. “Customer Experience is a journey, not a project. .”

Lean 94

Lean Agile B2B Metrics 94

Startup Lessons Learned

AUGUST 20, 2009

Lessons Learned by Eric Ries Thursday, August 20, 2009 The Promise of the Lean Startup Im honored to have a guest post on GigaOm to introduce the concept of the lean startup to their audience. The ultimate goal of a lean startup is to identify where its vision intersects with what reality can accommodate.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

JANUARY 14, 2015

Lately, I’ve been hearing from a lot of entrepreneurs experiencing pushback to the concept of minimum viable product. Their teams may disagree about what a product should look like, who the customer is, and which distributors to work with, but one thing they can all agree upon is: “We build high-quality products in this company.

Stealth 60

Stealth Engineer Leadership Design 60

Startup Lessons Learned

NOVEMBER 12, 2009

Lessons Learned by Eric Ries Thursday, November 12, 2009 New York: three straight days of Lean Startup (two of which are free) Greetings from Europe, where Im just wrapping up an incredible (and exhausting) speaking tour. Thanks to web2open , there are two Lean Startup sessions that are completely free and open to the public.

New York 94

New York Lean San Francisco Continuous Deployment 94

Startup Lessons Learned

MAY 17, 2009

Lessons Learned by Eric Ries Sunday, May 17, 2009 Last chance to register for The Lean Startup at HP on May 21 This coming Thursday, May 21, is the last time Im currently scheduled to give the full Lean Startup presentation in the Bay Area. What about the rest of us? Many startups are now following the Lean Startup process.

Lean 60

Lean San Francisco Continuous Deployment DC 60