The Lean LaunchPad at Stanford—The Final Presentations


(Page 2 of 2)

engineering process, not building a business. In the real world a startup is about the search for a business model or more accurately, startups are a temporary organization designed to search for a scalable and repeatable business model. Therefore we developed a class to teach students how to think about all the parts of building a business, not just the product.

There was no single class to teach aspiring entrepreneurs all the skills involved in searching for a business model (business model design, customer and agile development, design thinking, etc.) in one quarter. The Lean LaunchPad was designed to fill that void.

What’s Different About the Class?
The Lean LaunchPad class was built around the business model / customer development / agile development solution stack. Students started by mapping their assumptions (their business model) and then each week they tested these hypotheses with customers and partners outside in the field (customer development) and used an iterative and incremental development methodology (agile development) to build the product.

The students were challenged to get users, orders, customers, etc. (and if a web-based product, a minimum feature set) all delivered in 8 weeks. Our goal was to get students out of the building to test each of the nine parts of their business model, understand which of their assumptions were wrong, make adjustments and continue to iterate based on what they learned. They learned first-hand that faulty assumptions were not a crisis, but a learning event called a pivot —an opportunity to change the business model.

What Surprised Us?

  1. The combination of the Business Model Canvas and the Customer Development process was an extremely efficient template for the students to follow – even more than we expected.
  2. It drove a hyper-accelerated learning process which led the students to a “information dense” set of conclusions. (Translation: they learned a lot more, in a shorter period of time than in any other entrepreneurship course we’ve ever taught or seen.)
  3. The process worked for all types of startups – not just web software but from a diverse set of industries – wind turbines, autonomous vehicles and medical devices.
  4. Insisting that the students keep a weekly blog of their customer development activities gave us insight into their progress in powerful and unexpected ways. (Much more on this in subsequent blog posts.)

What Would We Change?

  1. In this first offering of the Lean Launchpad class we let students sign up without being part of a team. In hindsight this wasted at least a week of class time. Next year we’ll have the teams form before class starts. We’ll hold a mixer before the semester starts so students can meet each other and form teams. Then we’ll interview teams for admission to the class.
  2. Make Market Size estimates (TAM, SAM, addressable) part of Week 2 hypotheses
  3. Show examples of a multi-sided market (a la Google) in Week 3 or 4 lectures.
  4. Be more explicit about final deliverables; if you’re a physical product you must show us a costed bill of materials and a prototype. If you’re a web product you need to build it and have customers using it.
  5. Teach the channel lecture (currently week 5) before the demand creation lecture (currently week 4.)
  6. Have teams draw the diagram of “customer flow” in week 3 and payment flows in week 6.
  7. Have teams draw the diagram of a finance and operations timeline in week 9.
  8. Find a way to grade team dynamics – so we can really tell who works well together and who doesn’t.
  9. Video final presentations and post to the web. (We couldn’t get someone in time this year)

It Takes a Village
While I authored these blog posts, the class was truly a team project. Jon Feiber of Mohr Davidow Ventures and Ann Miura-Ko of Floodgate co-taught the class with me (with Alexander Osterwalder as a guest lecturer.) Thomas Haymore was our great teaching assistant. We were lucky to get a team of 25 mentors (VC’s and entrepreneurs) who selflessly volunteered their time to help coach the teams. Of course, a huge thanks to the 39 Stanford students who suffered through the 1.0 version of the class. And finally special thanks to the Stanford Technology Ventures Program; Tom Byers, Kathy Eisenhardt, Tina Selig for giving us the opportunity to experiment in course design.

E245, the Lean LaunchPad will be offered again next Winter. See you there!

Single PageCurrently on Page: 1 2 previous page

Steve Blank is the co-author of The Startup Owner's Manual and author of the Four Steps to the Epiphany, which details his Customer Development process for minimizing risk and optimizing chances for startup success. A retired serial entrepreneur, Steve teaches at Stanford University Engineering School and at U.C. Berkeley's Haas Business School. He blogs at Follow @sgblank

Trending on Xconomy