A New Way to Teach Entrepreneurship: Class 1 at Stanford’s Lean Launchpad
For the past three months, we’ve run an experiment in teaching entrepreneurship.
In January, we introduced a new graduate course at Stanford called the ” target=”_blank”>Lean LaunchPad. 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.
We thought it would be interesting to share the week-by-week progress of how the class actually turned out. This post is part one.
A New Way to Teach Entrepreneurship
As the students filed into the classroom, my entrepreneurial reality distortion field began to weaken. What if I was wrong? Could we even could find 40 Stanford graduate students interested in being guinea pigs for this new class? Would anyone even show up? Even if they did, what if the assumption – that we had developed a better approach to teaching entrepreneurship – was simply mistaken?
We were positing that 20 years of teaching “how to write a business plan” might be obsolete. Startups, are not about executing a plan where the product, customers, channel are known. Startups are in fact only temporary organizations, organized to search–not execute–for a scalable and repeatable business model.
We were going to toss teaching the business plan aside and try to teach engineering students a completely new approach to start companies – one which combines customer development, agile development, business models and pivots. (The slides below and the syllabus ” target=”_blank”>here describe the details of the class.)
Get Out of the Building and test the Business Model
While we were going to teach theory and frameworks, these students were going to get a hands-on experience in how to start a new company. Over the quarter, teams of students would put the theory to work, using these tools to get out of the building and talk to customer/partners, etc. to get hard-earned information. (The purpose of getting out of the building is not to verify a financial model but to hypothesize and verify the entire business model. It’s a subtle shift but a big idea with tremendous changes in the end result.)
We were going to teach entrepreneurship like you teach artists – combining theory – with intensive hands-on practice. And we were assuming that this approach would work for any type of startup – hardware, medical devices, etc. – not just web-based startups.
If we were right, we’d see the results in their final presentations – after 8 weeks of class the information/learning density in the those presentations should be really high. In fact they would be dramatically different than any other teaching method.
But we could be wrong.
While I had managed to persuade two great VC’s to teach the class with me (Jon Feiber and Ann Miura-ko), what if I was wasting their time? And worse, what if I was going to squander the time of my students?
I put on my best game face and watched the seats fill up in the classroom.
A few weeks before the Stanford class began, the teaching team went through their Rolodexes and invited entrepreneurs and VCs to volunteer as coaches/mentors for the class’s teams. (Privately I feared we might have more mentors than students.) An hour before this first class, we gathered these 30 impressive mentors to brief them and answer questions they might have after reading the mentor guide which outlined the course goals and mentor responsibilities.
As the official start time of the first class drew near, I began to wonder if we had the wrong classroom. The room had filled up with close to a 100 students who wanted to get in. When I realized they were all for our class, I could start to relax. OK, somehow we got them interested. Lets see if we can keep them. And better, lets see if we can teach them something new.
The First Class
The Lean LaunchPad class was scheduled to meet for three hours once a week. Given Stanford’s 10 week quarters, we planned for eight weeks of lecture and the last two weeks for team final presentations. Our time in class would be relatively straightforward. Every week, each team would give a 10-minute presentation summarizing the “lessons learned” from getting out of the building. When all the teams were finished the teaching team lectured on one of the 9 parts of the business model diagram. The first class was an introduction to the concepts of business model design and customer development.
The most interesting part of the class would happen outside the classroom when each team spent 50-80 hours a week testing their business model hypotheses by talking to customers and partners and (in the case of web-based businesses) building their product.
Selection, Mixer and Speed Dating
After the first class, our teaching team met over pizza and read each of the 100 or so student applications. Two-thirds of the interested students were from the engineering school; the other third were from the business school. And the engineers were not just computer science majors, but in electrical, mechanical, aerospace, environmental, civil and chemical engineering. Some came to the class with … Next Page »
Trending on Xconomy
By posting a comment, you agree to our terms and conditions.