Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept. Great post!

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. The Customer Development process (and the Lean Startup) is one way to do that.

Lean 263

Lean Silicon Valley Startup RSS 263

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Customer Development 255

Customer Development Developer Customer Silicon Valley 255

Steve Blank

SEPTEMBER 3, 2009

This post describes how the traditional product development model distorts startup sales, marketing and business development. The meaning of alpha test , beta test, and first customer ship are pretty obvious to most engineers. Here’s what the product development diagram looks like from a sales perspective.

Customer Development 229

Customer Development Developer Silicon Valley Customer 229

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. They never understood Market Type. Why does Market Type matter?

Customer Development 221

Customer Development Developer Customer Silicon Valley 221

Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. That’s in stark contrast to the traditional Product Development Model where it’s expected a customer is already there and waiting and it’s simply a matter of [.] familiar with Customer Development you should be.

Product Development 161

Product Development Developer Silicon Valley Product 161

Steve Blank

SEPTEMBER 24, 2009

New strategic direction in companies with loyal customers have different consequences then when you had no customers Acquiring new customers are a lot more expensive that converting existing ones. on July 9, 2010 at 12:50 pm Said: [.] Fire might be a strong word.

Customer 217

Customer Silicon Valley RSS California 217

Steve Blank

FEBRUARY 23, 2009

I was between my 7th and 8th and final startup; licking my wounds from Rocket Science, the company I had cratered as my first and last attempt as a startup CEO. We’ve managed startups like this forever; there is no other way to manage them.”

Silicon Valley 132

Silicon Valley RSS Venture Capital Customer Development 132

Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. The answer depends on your answer to two questions: which step in the Customer Development process are you on?

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

AUGUST 31, 2009

After 20 years of working in startups, I decided to take a step back and look at the product development model I had been following and see why it usually failed to provide useful guidance in activities outside the building – sales, marketing and business development. So what’s wrong the product development model?

Customer Development 245

Customer Development Developer Customer Silicon Valley 245

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention.

Vertical 165

Vertical Silicon Valley Marketing Customer 165

Steve Blank

MARCH 3, 2015

Berkeley in 2010 to run the Lester Center for Entrepreneurship in the Haas School of Business we were teaching entrepreneurship the same way as when I was a student back in 1995. The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

AUGUST 24, 2009

Home Books for Startups Secret History-Bibliography Steve Blank Startup Resources Steve Blank Entries RSS | Comments RSS Categories Air Force (9) Ardent (9) Big Companies versus Startups: Durant versus Sloan (29) California Coastal Commission (3) Conservation (2) Convergent Technologies (1) Customer Development (98) Customer Development Manifesto (..)

Silicon Valley 213

Silicon Valley PR Technical Review RSS 213

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

JULY 30, 2009

And other startups are in a New Market — creating a market from scratch (like Apple with the iPhone, or iPod/iTunes.) (“Market Type&# radically changes how you sell and market at each step in Customer Development. It’s one of the subtle distinctions that at times gets lost in the process.

Silicon Valley 144

Silicon Valley RSS California Customer Development 144

Steve Blank

MAY 18, 2009

Next, you have to deal with the daily crisis of product development and acquiring early customers. And here’s where life gets really interesting, as the reality of product development and customer input collide, the facts change so rapidly that the original well-thought-out business plan becomes irrelevant.

Founder 312

Founder Silicon Valley RSS China 312

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. In those cases, the product may stay mostly the same, but the positioning, marketing, and - most importantly - prioritization of features changes dramatically. Ajay January 24, 2010 6:15 AM Matthew Ogston said.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Steve Blank

MAY 7, 2009

My two cents is that a business plan is the single place to collect your thinking about about your: business model, distribution channel, demand creation plan, financial assumptions, and customer and product development plan. If you’re text averse like i am, try to diagram these key items and then write-up the diagrams.

Business Plan 158

Business Plan Silicon Valley RSS Venture Capital 158

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already).

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. My first time at your blog. You are a great blogger.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 4, 2008

Customer development. Its not enough just to build a product with great features - you have to figure out if there is a market for it. For those interested in getting started with agile or customer development, I thought Id include a few links. This speeds up the Ideas-Code-Data feedback loop. Excellent ideas!

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Thoughts on scientific product development Lo, my 5 subscribers, who are you? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. May 30, 2010 1:34 AM Poker Workout said. Its incredibly hard to do.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

MARCH 9, 2010

Lessons Learned by Eric Ries Tuesday, March 9, 2010 Startup Lessons Learned - the Conference (April 23, 2010 in SF) Today we are opening up registration for the first ever Startup Lessons Learned Conference on April 23, 2010 in San Francisco. Im incredibly excited. Im incredibly excited.

San Francisco 151

San Francisco Lean Continuous Deployment Startup 151

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

NOVEMBER 7, 2008

If you cant find any , maybe that means you havent figured out who your customer is yet. And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. What is customer development?

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Check your assumptions, what went wrong?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158