Steve Blank

SEPTEMBER 5, 2013

While our teams have mentors, socialize a lot and give great demos, the goal of our class final presentations is “ Lessons Learned ” – about product/market fit, pricing, acquisition/activation costs, pricing, partners, etc. Given something tangible, customers were able to start gauging their willingness to use and pay.

Lean 322

Lean Customer Development Sales Cycle Business Model 322

Steve Blank

OCTOBER 30, 2012

The class teaches founders how to dramatically reduce their failure rate through the combination of business model design, customer development and agile development using the Startup Owners Manual. And Udacity has put their awesome production resources behind the class and hosts the Lean LaunchPad online lectures.

Startup 335

Startup Lean Incubator Business Model 335

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 imagine how well that worked. On the minus side, that has made it a wee bit hard to understand.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. MVP, despite the name, is not about creating minimal products. We have to manage to learn something from our first product iteration.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

SEPTEMBER 16, 2014

While most of the early attention in a startup is paid to finding product market fit ( the match between value proposition and customer segment on the right-side of the canvas) it’s the left side of the canvas that will tell you what your founding team should look like. . Filed under: Customer Development.

Cofounder 335

Cofounder Founder Intellectual Property Business Model 335

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does.

San Francisco 158

San Francisco Management Software Review Product 158

Steve Blank

JANUARY 27, 2011

This startup search process is the business model / customer development / agile development solution stack. The traditional business plan is an essential organizing and planning document to launch new products in existing companies with known customers and markets. Business Model Versus Business Plan.

Business Model 285

Business Model Utah Intellectual Property Agile 285

Steve Blank

DECEMBER 13, 2010

Here’s the course announcement from Professor Vergara (in English): Customer Development Course in Chile – Lean Launchpad. The objective of this course is that groups of students finish with a completed software product that has real customers and an identified market.

Chile 241

Chile Silicon Valley Lean Agile 241

Steve Blank

APRIL 10, 2009

An example of a reversible decision could be adding a product feature, a new algorithm in the code, targeting a specific set of customers, etc. An irreversible decision is firing an employee, launching your product, a five-year lease for an expensive new building, etc. That’s why startups are agile.

Silicon Valley 309

Silicon Valley RSS Startup Agile 309

Steve Blank

DECEMBER 20, 2011

We taught them the business model / customer development / agile development solution stack. This methodology forces rapid hypothesis testing and Customer Development by getting out of the building while building the product. Unlike other incubators, our Lean LaunchPad Class had a specific curriculum.

Incubator 310

Incubator Government Silicon Valley Lean 310

Steve Blank

MAY 17, 2010

A business plan is the execution document that large companies write when planning product-line extensions where customer, market and product features are known. Most startups are facing unknown customer needs, an unknown product feature set and is an organization formed to search for a repeatable and scalable business model.

Business Plan 320

Business Plan Business Model Customer Development Deal Flow 320

Steve Blank

JUNE 3, 2010

He believed that large companies handle sustaining innovation – evolutionary changes in their markets, products, etc. valued by their existing customers – fairly well. Yet most research has shown that disruptive innovation, that is innovations that go after new markets, new customers, new technologies, etc.

Search 251

Search Agile Customer Development Technical Review 251

Steve Blank

MARCH 8, 2011

It was designed to bring together many of the new approaches to building a successful startup – customer development, agile development, business model generation and pivots. Even if they did, what if the assumption – that we had developed a better approach to teaching entrepreneurship – was simply mistaken?

Lean 307

Lean Business Model Customer Development Guinea 307

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. And most startup code and features end up on the floor as customers never really wanted them.

Lean 263

Lean Silicon Valley Startup RSS 263

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. Our mystery keynote is now revealed and I couldnt be more excited. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Steve Blank

MARCH 2, 2011

Working with him, I’ve been impressed to watch his small team embrace Customer Development (and Business Model Generation ) and search the world for the right product/market fit. They’ve tested their hypotheses with literally hundreds of customer interviews on every continent in the world. Corporate elephants can dance.

Silicon Valley 239

Silicon Valley Agile Customer Development Early Stage 239

Steve Blank

JUNE 26, 2014

We’re changing the order in which we teach the business model canvas and customer development to better-fit therapeutics, diagnostics and medical devices. “Customer Development” to test the hypotheses outside the building and. Teams talk to 10-15 customers a week and make a minimum of 100 customer visits.

Intellectual Property 290

Intellectual Property Lean IP Open Source 290

Steve Blank

APRIL 16, 2013

To fill this gap I wrote The Four Steps to the Epiphany , a book about the Customer Development process and how it changes the way startups are built. Eric Ries, who took my first Customer Development class at Berkeley, had the insight that Customer Development should be paired with Agile Development.

Technical Review 223

Technical Review Lean Venture Capital Customer Development 223

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Both Sides of the Table

NOVEMBER 1, 2009

They communicated this to product management who looked at all of the internal requirements we had generated (e.g. some came from our customer service, some were to improve performance / scalability from tech ops, some were bug fixes, etc.) and product management worked with me to decide what to build & when.

Customer 280

Customer Technical Review Software Review Mexico 280

Steve Blank

JUNE 11, 2009

Agile – you may find the real opportunities for your company was somewhere else. Passionate – is the company/product/customers the most important thing in your life? This means you still need to have a resilient personality, and be agile. How quickly will you recover? Can you recognize and capitalize on them?

Cofounder 230

Cofounder Founder Silicon Valley Technical Cofounder 230

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. During this period, the Palantir Gotham team grew from five developers to around 35. So what was going on?

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

MAY 9, 2017

And to today, when its major product is simply innovation. When the product and channel are bits, adoption by 10’s and 100’s of millions and even billions of users can happen in years versus decades. The second thing that’s changed is that we’re now Compressing the Product Development Cycle.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

Steve Blank

MAY 6, 2015

I am always surprised when critics complain that the Lean Startup’s Build, Measure, Learn approach is nothing more than “throwing incomplete products out of the building to see if they work.”. Repeat, learning whether to iterate, pivot or restart until you have something that customers love. Waterfall Development. Here’s how.

Lean 120

Lean Agile Business Model Customer Development 120

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MARCH 6, 2013

Vinod Khosla Founder Dave McClure Founding Partner Eric Ries Author Steve Blank Serial Entrepreneur & Professor Todd Park CTO Travis Kalanick CEO & Co-Founder Joe Zadeh Director of Product Sam Shank Co-Founder & CEO NEW! Seth Sternberg Co-Founder & CEO Scott Chacon CIO Kevin Hale Senior Product Manager NEW!

Lean 165

Lean Cofounder Startup Software Engineering 165

Steve Blank

JUNE 8, 2021

– while simultaneously building a series of minimal viable products. Unlike traditional demo days or Shark Tanks which are, “Here’s how smart I am, and isn’t this a great product, please give me money,” a Lessons Learned presentation tells the story of a team’s 10-week journey and hard-won learning and discovery.

Lean 417

Lean Security Asia SBIR 417

Steve Blank

APRIL 9, 2009

The other departments in marketing gave the same answers; the product-marketing department said their job was to write data sheets. But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. The same was true for the Product Marketing group.

Silicon Valley 271

Silicon Valley Technical Review RSS PR 271

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. So their management teams were insisting that they OEM (buy from someone else) these products.

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Labels: product development 15comments: mukund said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Have you worked with or for a great CTO?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

YoungUpstarts

APRIL 21, 2013

Creators of new products in environments of extreme uncertainty, startups face enormous risks. Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. As a startup owner, what can you do to improve your chances?

Lean 193

Lean Technical Review North America Startup 193