ETL Speaker Series: Tom Eisenmann, Harvard Business School

Tom Eisenmann identifies six patterns that kill startups: Good Idea/Bad Bedfellows, False Start, and False Positive early on; Speed Trap, Cascading Miracles, and scaling failures later. He argues customer discovery before building and domain expertise prevent most failures, and that founders should fail with integrity.
Questions this video answers
Early investors did not or never will make money.
Good idea/Bad bedfellows; False start; False positive.
Speed trap (growing too fast — operational, cultural, LTV/CAC pressures and ethical risk).
Chapters
All right, thanks so much, Tom Eisenman, for being here today. My name is Tom Byers, so it is the Tom and Tom webinar or show for this Entrepreneurial Thought Leader Seminar series episode. It's the first of three this particular term, and I'm looking forward to spending the next 50 minutes or so with my good friend Tom Iserman from maybe I'll call it the Stanford of the east, the Harvard Business School, which needs no introduction as far as the university. I teach here at Stanford University in the Department of Management Science and Engineering and a been teaching entrepreneurship here for quite a few years, about the same number of years as our guest today, and I've always been such a big admirer. I want to get it right, though, with his proper titles, because they are significant.
Tom Iserman is the Howard H. Stephenson professor of Business Administration at the Harvard Business School, the Peter O. Crisp Chair of Harvard Innovation Labs, which is a terrific accelerator on campus, and a faculty co chair of the HBS Rock center for Entrepreneurship, which is our counterpart here at stbp. But there's more. He's just come from opening the Harvard Ms. MBA program for this year, which he's a faculty director of. And turns out he's the faculty director of the Harvard College Technology Innovation Fellows Program, which has a parallel here as well. So it's so cool. But the reason particularly excited is that he has a book out that is just super. And we're going to get into that in just a moment. But did I get that correctly? All of did I get all your titles right or did I miss anything?
Tom, no. Tom, thank you so much.
I know we've got some Mayfield Fellows listening. I'm proud of the Harvard College Tech Fellows. It only took us 25 years to copy what you're doing.
And we've done that a few times. I'm happy to say stay in your slipstream on a lot of these things.
Well, we've set some big, hairy, audacious goals, as Jim Collins used to say, for the next 45 minutes. There'll be time for questions from our audience later on, but I have a few, and we're going to range in a variety of topics. What's really interesting about our audience today tomorrow is that we have everybody from folks just getting introduced that you can actually learn entrepreneurship and, you know, of all ages to our colleagues around the world who teach entrepreneurship, which we've learned you can. And so.
There'S been a gap, though, and this is what makes me so excited about your book. And I'm going to hold it up because I get to do this. Why Startups Fail, a new roadmap for entrepreneurial success, which I really think is a seminal event. And for those of us who teach entrepreneurship and we're I'm going to do my best to let you speak mostly during this and I think we'll convince most people who have a chance to listen to this episode eventually because it is really, it's really something else. But let's start at the very beginning. Why do you want to potentially be labeled the professor of failure? Why does studying failure mean so much?
Yeah, it has scared off a few founders who might otherwise be looking for advice.
There's two ways to answer this, which is why should an aspiring entrepreneur learn about failure? And you know, the fact is.
The drivers of failure aren't simply the photo negatives of the drivers of success.
It's complicated, right? To succeed as an entrepreneur, you probably have to grow. But boy, if you want to find a leading cause of startup failure, it's growing too fast. So studying failure is important. But personally, why I started goes back to a team that I worked with. They were students of mine and a year after graduation, launched a venture, I was an investor after, after they graduated, had a lot of confidence in the team and they raised a million dollar seed round, wanted to raise a million and a half. That was part of the failure story and got the business going. Validated demand with the very best lean startup techniques we can teach them. And sure enough, after they launched, the demand was there and repeat purchases were there. Took them longer than they expected to get the operations under control. So they were burning through cash. And while they were making progress, they weren't making enough progress and shut down after a year. And I could point to a lot of things that went wrong, but I couldn't pinpoint the cause or the causes of failure. And that was a little disconcerting. Here I was a supposed expert on entrepreneurship. And in our field, depending on how you define a startup and how you define failure, 2/3, 3/4, 90% of startups fail, right? And so it's a really important phenomenon and I was a failure at explaining failure. So this goes back eight years. And so I set out to read everything anybody had ever written about startup failure, practitioners and academics, and interview lots and lots of failed founders and the investors who back them and do the survey work and write the cases that form the backbone of this book. So it only took eight years to pull it all together. Things move a little more slowly in academia than they do in startup land.
Well, I'm so glad you did. So let's do some definitions here. How do you define startup failure?
So startup failure in the book, the shorthand definition is early investors did not or never will make money. And that's important. The early investors. Right. Somebody can come in late with a liquidation preference. A lot of folks listening will know what that means. Is basically liquidation preference means you get your money back before anybody else that invested earlier gets money.
If you're at the bottom of a liquidation stack, the way we express it, you're the last in line. Series A seed and common.
So if the early investors didn't make money, the common didn't make money, which means the entrepreneurs didn't make any money. And that's a failure of some sorts of. We might ask, well, why the investors and not the founders? The reality is, by the time you get to series D, so four big rounds of financing and.
Maybe we're five years or seven years in, only 40% of venture capital backed startups at Series D still are run by a founder CEO. So you can't only take the founder's preferences and priorities as the measure of whether things worked or not. We could ask questions, and I know STBP is super interested in ethics from the perspective of society at large. We have startups that are financially successful, but we all wish they would disappear. They pollute, they exacerbate income inequality, they have addictive products in a bad way.
And we have some financially unsuccessful startups that actually contribute to society in the sense they show other entrepreneurs what not to do, which is important. And they train a whole cadre of managers and employees to go off and do new things, better things.
So the answer is, it's complicated. But if you want shorthand, early investors didn't make money, and that seems reasonable.
That'S what you studied. So let's go through some of the findings in the way you organize them. I believe if I got this right, there's three patterns of reasons that you extrapolated from the data and from the amazing amount of fieldwork on what went wrong at Early Stage Ventures. And then there's another three patterns for later stage, or what I think you call them.
At scale.
Yeah, exactly. You know, the folks here who've studied design or work as designers know that you always start with a lot more options. So the first or after the book had 50 patterns. It was going to be basically two page chapters. And it turns out if you keep combining and sort of looking for commonality, you can, you can Join all the way down to these six. So the early stage patterns, these are companies that are still searching for product market fit. One of them is, I call it Good idea, Bad Bedfellows, and this is the startup I mentioned that was the catalyst for this work. They had a good idea and they had actually validated it through lean startup MVP style testing. But they never got the bedfellows in the sense.
Investors. And a lot of entrepreneurs will talk about jockey and horse and the jockey meaning the founders and the horse being the concept. The point is bigger than that. It's not just the founders who have to be.
Ready to lead, but also the rest of the team has to be well equipped. There are investors who want to add value. You want them to add value beyond just the money. There's often strategic partners because the startup can't do it all. They borrow other people's capability.
And so there are some startups, unfortunately, that have a good idea, but they just never manage to marshal the full set of resources you need to pull it off. That's the Bad Bedfellows pattern. The second pattern, and this is probably the number one killer of early stage startups I call false start. So as we do this conversation, we're in the middle of the Olympics, so we're familiar with false starts and swimming and track and field. You jump the gun in an effort to get an edge. And lots of entrepreneurs do exactly that. They basically start building and selling their thing because that's what entrepreneurs do, right? Bias for action, passion, burning bright, sort of a conviction. They found the right problem solution pair and what they've done is they've skipped a whole bunch of upfront research, what your colleague Steve Blank would call the customer discovery phase, where you're basically exploring the problem, figuring out if you've found a problem worth solving. And then they've skipped the phase of generating lots of potential solutions, which is what a design user, experienced designer would do, and narrowing that, that big set of solutions down to the most promising one through prototype testing and getting user feedback and so forth. And so this is not work that needs to take a year. You can probably do this stuff in four weeks for many entrepreneurs. But in the interest of saving those four weeks, these folks have plunged straight in. And essentially the odds that the first version of the product, when you do that, is going to hit the mark, are low and might take you four months to build it, figure out how to sell it, see that it's not working, and figure out what to do next. So, you know, in order to save Four months, four weeks and just get going. You've wasted four months. And if you've only got a year's worth of money in the bank, like my founders I mentioned at the beginning, that's really boosts your failure odds. So that's the second one. Third one is a false positive. And again we, we've been through a lot of COVID recently, so everybody knows about false positives and false negatives. And for an entrepreneur that's a signal that your concept is right on target and.
It'S an invitation to step on the gas. And it often comes from the enthusiasm of your early adopters. Every entrepreneur needs early adopters to get going. And what's true is the early adopters needs are often different than the needs of the mainstream customers. Right. See this with a Dropbox would be a good example. Drew Houston, when he launched the business talked about building a product that would be simple enough that his mother could use it to store her recipes. His early adopters were software engineers who had incredibly sophisticated needs for sharing across many devices, collaborating big files, et cetera, et cetera. And they wanted features that Drew left out of the product. And he did that very deliberately. Not the only way to go, but it was very aware of the difference between the mainstream and the early adopters, other entrepreneurs and their zeal to serve. You want to keep the early adopters happy so they'll build a product that ends up being over engineered for the mainstream. So those are the three early stage patterns.
So let's pause right there and just take a little deeper dive because.
It'S phenomenal how.
Much of an impact the lean startup methods have had. Well as on teaching entrepreneurship and we've been lucky to have Steve Blank.
Start that course and spread it. Ten years ago you also had Eric Reese who is also one of the, I guess if there are such a thing of founders of the lean startup methods with Steve and he spent time with you. So it's. I was on a call with Steve Blank earlier today and we were part of a meeting at Stanford. We're very lucky he's been associated with us all these years with this happening. But I want to dive into a couple of the things you just talked about and how people embracing those methods can improve from what you learned from this statistically significant data set that you have from failure.
Yeah, so I mean the survey work that basically shows things like if you pivot too often or not often enough, that's going to boost your failure odds. So there's no surprise there. The big surprise was the false start. And you know, because we know what lean startup done well looks like. And certainly Steve's been teaching it and lots of people have been writing about it, we've been teaching it. And what's true is a lot of entrepreneurs think they are following lean logic because they are building fast. They're building in an agile method, they're getting their product to market fast and they're getting a lot of feedback on it. The problem is they've skipped the whole upfront phase, the phase that Steve calls, Steve Blank calls customer discovery. And they've jumped right to what Eric Ries in particular is, you know, the build, measure, learn part of Lean Startup. And you know, and you can sort of understand some of the psychological motivations here. Entrepreneurs have a bias for action. That's how they identify basically people who make things happen. What could be more natural than starting to build the thing? A lot of entrepreneurs are engineers, engineers love to build things. So.
What could be more natural than starting to build? And a lot of entrepreneurs are overconfident. So they're sure they've got, they can see around corners, they know the problem they want to work on, they got a vision of the solution. So let's start building it. And you know, and even I teach a lot of MBAs who are not technical. But what do they hear? They hear that you have to have great product to succeed. How do you get great product? You get an engineering team. How do you get an engineering team? You take those MBA networking skills and you go off and you find a co founder or you sort of scrape together enough money to outsource the thing, however you're going to do it, once those engineers are on board, you have to keep them busy. And how do you keep them busy? They start building. So there are all these pressures. And if you think about the full lean startup process, the MVP testing is actually the last stage of the process. You should really only do that after you've done a big round of customer discovery. The British Design Council has this double diamond design and the diamonds are side by side, are problem definition and solution development. And the diamonds go out divergent thinking. So you expand your understanding of the problem space. Lots of customer segments, lots of needs you might solve. And then you narrow in through proper user experience, research techniques and then the same thing with the solution. You know, generate a lot of solutions and then narrow them down. And it's only after you've done that narrowing do you start MVP testing. So these entrepreneurs skip a whole bunch of stuff. They think they're running lean, and they are in a sense, but they've skipped a lot of steps for very understandable but ultimately deadly reasons.
Thanks for that. And those are astute observations on how to improve the odds of. I mean, first, I know being an educator like yourself, all the stuff that we teach and work on in our active learning and experiential classrooms, both physical again someday as well as online, we're just working on increasing the odds for success. I mean, there's no one prescription. So I also like the style of your book, that it doesn't say, do this and you'll be guaranteed not to fail. I mean, so this is in the spirit of just adding additional probability of success to what is a great contribution to education with the whole lean startup thing the last 10 years. All right, so let's go back to the behaviors. Those are. We've been concentrating the last few minutes on early stage, the launching stage. Now let's talk about when it's time to hopefully get into scaling. What did you find there?
Well, you know, again, it's kind of shocking if, say, two out of three early stage startups, venture capital backed startups, fail in the sense that they don't yield positive return for the investors. You'd think that the failure rate would be lower for folks who get past the early stage, make it to, say, Series C and beyond. But it's still 1 in 3 odds of not making money for your investors. Sometimes that's because investors get in a bidding war for your shares. They get excited about the momentum that got you to Series C. But it turns out there's just an awful lot of things that can go wrong as you start to scale up. And.
I think that probably the biggest killer of late stage startups is what I call a speed trap. So, you know, picture the policeman with a radar gun at the side of the road and saying, your startup's going too fast. And this speed trap will often start when a company has a lot of early momentum. So the product is working, people are buying it, they're spreading the word, and that attracts the attention of investors. They pour a lot of money into the startup, hoping to basically ride the rocket ship and expecting that the team will sustain the momentum. There's some dynamics then. So as you try to keep growing, almost by definition you're expanding in a direction toward customers that are less interested in, in your product than the last round. Right. The first people on board are the people that really want what you've got. And as you move beyond that, they're going to be people that are, well, a little less interested. So you're going to have to cut the price. You may have to add features, you may have to market much harder so the customers become worth less and they cost more to acquire. So you get this squeeze on profits or the folks who've studied long term value of a customer LTV to CAC customer acquisition costs. You want that ratio to be over one and preferably over three or some number like that. And so you get an LTV CAC squeeze. Your very growth attracts competitors. The rivals come out of the woodwork. Big established companies sort of wake up to somebody doing something interesting in their space. Meantime.
You'Re growing. And if you've got the kind of business where humans have to do things, I mean, you might be lucky. And it's pure software, so that scales a little more easily. But a lot of businesses direct to consumer say you got people packing boxes, manufacturing things, answering the phones to handle customer service. All those people have to be brought on board. And they come on board into a company that has no systems, no processes, no nothing. So all that stuff has to be put in place, has to be put in place by entrepreneurs who are probably suspicious of bureaucracy, rightly so, and are probably resistant to putting in too much in the way of structure. You get cultural friction, tension between the old guard, the people that were present at the creation, and the new guard. Who are these new people? They're specialists. I'm a jack of all trades, generalist. The newcomers say that person down the aisle has $5 million worth of stock options. And I don't, but I seem to be working just as hard as they do. So you get fiefdoms between the functions and cross country, cross cultural, cross functional conflict. And so there's a lot of things that can start to go wrong, you know, when it goes really bad. But pressure, pressure, pressure for growth. And the growth is harder to come by. That's where you can hit an ethical slippery slope and you know, and see people cross the line misrepresenting their progress or just sort of cutting corners in ways that are dangerous for customers or illegal. And so that's the speed trap. And you can sustain it for a while, sort of. People can look the other way and assume you can fix it, but eventually you realize that it's growing, but it's not growing profitably and it probably never will. And at that point the investors skitter away and you can't find new ones and the thing can crash pretty quickly and leave this giant steaming Crater in the landscape. When a late stage startup fails, we notice it's hundreds, maybe even thousands of jobs and hundreds of millions of dollars. You know, when. When an early stage startup fails, it's heartbreaking for a few people and their friends and family, but the late stage hurts.
Yeah.
So I'd like to talk about one of those patterns, the Cascading Miracles, and elaborate on that. And particularly in the book you talk about Better Place, I went to. I'm using my.
My silver. I'm not shooting arrows at you. I don't on this one. Professor Eisenman, please. Let's chat about Better Place, because we had some of our Mayfield work study program fellows work there when it was in its heyday, I think it was headquartered here and.
Yeah, Palo Alto.
Yeah, yeah. So I remember going to the offices and it was, oh, wow. I mean it. So let's use that because frankly, the label you gave this pattern, Cascading Miracles, I think is just the best label ever.
It's going to thank you. I stole it from John Malone, who was the entrepreneur who built the biggest cable TV system operator in the country, and he got it from a mentor of his. So the notion. I'll explain Cascading Miracles in a minute, but we should probably say a little bit about Better Place. So Better Place, and you get a feel for the Cascading Miracles pattern if you understand this company. So Better Place, Shay Agassi was the entrepreneur, had the concept that to save the world, literally climate change, we needed electric cars everywhere. And the only way you could have them is if you could reliably recharge them when they were out on the road. So he wanted to deploy a network of charging stations everywhere, everywhere, including stations where a car would drive in, a robot would pull out the depleted battery and pop in a fully charged battery, all in five minutes. Same amount of time would take the gas up. And they deployed this network in Israel and Denmark, raised $900 million. And it was just too much. Too much in every dimension, too big a behavioral change for the customer. So let's step back and think what has to go right. And now you're. Our audience will see what we mean by Cascading Miracles. So think of an equation where you're going to multiply a bunch of things together. And if any of the things, any of the elements are at zero, the whole expression goes to zero. So a bunch of long shot probabilities or difficult probabilities, uncertainties that this company faced, you needed behavioral change on the part of consumers. This was 2008, before the only electric car out there was the. The Tesla Roadster, $110,000 little sports car. And you needed government subsidies for that, obviously, which hadn't happened yet. You needed the big car companies to design their cars to have the swappable batteries. Big deal. Big deal. To get Ford and Volvo and all these companies to change their car designs, imagine you needed to find places to put all these charging stations and battery swapping stations. You needed to raise.
Literally billions of dollars to deploy this thing. And you needed to have a team that could actually keep the wheels on as you were building and executing all this stuff. So you needed a bunch of things to go right. And you would need a cascade of miracles if all of them were going to go right. And they did get some things right. People did adopt electric cars. Eventually there were government subsidies. They got one oem, Nissan, Renault to design a car that had the swappable battery. But it just turned out that deploying the recharging station turned out to be much more expensive than they originally projected. And demand was, while growing, they only ultimately sold 1500 cars in the two countries, so with a long way from world domination. So, yeah, cascading miracles and the pattern. So sometimes, Tom, they work, right? I mean, Tesla was a case of cascading miracles. SpaceX certainly was. If we go back, you and I are old enough to remember when Federal Express was launched in the early 70s. It was the biggest venture capital launch in history at the time, and people thought it was insane to fly a package from Buffalo to Cleveland through Nashville, Tennessee.
But if you look into those stories, maybe I'd mend this to cascading just in time. Miracles.
Just the ones. You mentioned that.
There were some moments for Tesla that really came to a head, that they were staring at a different outcome.
And Federal Express nearly bankruptcy many times. So yeah, they're tough. They tend to be run by or led by truly charismatic founders who can spin up. You know, we use the expression reality distortion field about Steve Jobs and some other entrepreneurs. These are the best at it. And Shia Agassi was that. I mean, he could, he could mesmerize an audience just by sort of spinning a vision of a better. The world is a better place with, with his network deployed. But there can be a line between charisma and cult leadership. And sometimes the reality distortion field folds back on itself and the charismatic founder can't see that the universe is saying this is too early or this is too big, this is not gonna work. And then it becomes a tricky Problem for the board of directors, sort of. How do you reel the person in and convince them that it's time to pivot, find something that can be done?
Well, thanks for taking us through the six behaviors. And I find this moment truly ironic. Remind me, when did you start teaching at HBS? What year?
1997.
Yes, mine was 1995. Full time. So I realized, and remember that we were the same pedigree, or vintage, maybe somebody ought to put it. But the reason.
I got to get this job, and I know you feel the same way, this is not a job. This is such a joy that what you and I do. And I want to talk a little bit about education later on, but the reason that happened is because I was part of a cascading miracle situation that did not happen. And that was building a lot of software going to be the Microsoft in terms of Microsoft's applications, the broadest set of applications for pen and finger based computing.
So were you at GO Computing?
No, we were on top of go, meaning the applications that ran on there. It's called Slate. And we had one of your grads, the fellow, my co founder, was the person who invented the spreadsheet in your classroom. You know what I'm talking about, Dan Brickley.
Yeah, of course.
And we. So we had amazing 70 of the finest software people at the time, including the person who invented spreadsheets to begin with, long before that. But we were the cascading miracles, meaning you're sitting on top of an ecosystem that had everything had to go right. And it went right. But not in 1993.
It took 20 years.
Yeah. So there you go. Can we shift gears a little bit here these last few minutes before we open up to the questions? Let me just make sure I know what the team wants me to do because I was having such a flashback there. Yeah. Well.
Tell me about the origins in the classroom where you taught a course. Right. You taught a course about failure. And so when did the light bulb go off or the epiphany go off that, wow, I should really dive into this, really do the research, really do the book. So it's. This is not so much about a book. It's about this period of time that.
You went through and said, yeah, exactly.
You know, I knew that the course, when I made the commitment to write the book, I knew a course and sort of testing the ideas with smart students and bringing entrepreneurs into the class, failed founders into the classroom would sharpen the ideas. And, boy, was that the case.
I had tried teaching failure, you know, when the intro entrepreneurship course at Harvard Business School. The students in the end of semester feedback always said, you know, you tell us that two out of three startups fail, but then you show us all these winners and, like, what's going on here? And so we would put in a couple of failures, and then the reaction would be, thank you, rear view mirror. Oh, isn't it kind of obvious why that one failed? Like, well, did you see the smart people that built it and the smart people who invested in it? It wasn't obvious at the time. So I knew to actually, to teach this stuff, I was going to have to sort of reinvent the approach in the classroom.
Harvard Business School did a lot of case methods, so this course and Setting Failure is particularly well suited to the case method. But the way I got around the rear view mirror was to bring the founder in literally from the first minute. Most of my colleagues save. If a founder is visiting, they save them for the last 20 minutes, and the class will run a discussion for an hour. And then you bring the founder in to comment on the discussion, discussion and update things and so forth. I brought them in from minute one, and, boy, the students would look at that person and say, wow, this is a sharp individual. They're inspiring. They clearly thought this through, and that diffused the whole notion that it's obvious why these things fail. And so the second thing I worried about, Tom, when I launched the course was that it'd be depressing, but even more so that it would turn off a whole bunch of Harvard Business School students from ever launching anything. Half of our graduates, over the course of the first 20 years launch a business, so it's a pretty entrepreneurial place. And I worried about the article coming out five years from now. Suddenly, entrepreneurship has rolled off the edge, and who's responsible for that? It's this failure course.
The professor killed entrepreneurship education.
Exactly. And so at the end of the course, each year, I asked the students, has the course changed the way you think about being an entrepreneur in the next five years after graduation? And 40% on average say, yeah, I'm actually more likely.
And it's, you know, yeah, I've seen the pain. I've seen it right up close. You put it in my face. I think I can handle it. But more importantly, I've seen this founder that you brought in and what he or she's doing now, really impressive. So they bounce back. And, you know, every one of them said that even though it failed, it was worth the ride. They're proud of what they did. They Learned a lot. So Those folks, another 20% say, no thanks. Like, you showed me the pain, you showed me the personal, you know, what it does to families, you know, just how hard it hurts. And I don't think I want to go through that. And then 40, the remaining 40% basically say, I was always going to be an entrepreneur, I'm still going to do it. And they self select the aspiring entrepreneurs into courses like mine. But what you've shown me is that raising venture capital isn't the only way to build a tech venture. And that's important, you know, I mean, the business schools in particular, I think it's probably true where you teach, we lionize venture capital and our students tend to think it's the only, you know, if you're going to build a startup, it's the only way to do it. And a lot of these founders in the course come in and they say, look, I was eyes wide open. I knew what I was, what I was signing up for, that a VC is going to pressure you for lots of growth, that, you know, they need everything in the portfolio to have the potential to be a 10 times, 20 times return. And of course only a handful of small fraction are going to be. But I didn't realize what that meant for the way I would run the business and the sort of pressures it would put on me, and I'm not going to do it again. So we started to think, you know, because of the course, about how can we bring better understanding of other financing approaches into our classroom.
Thanks for sharing that experience. So building on that though, I want to go.
All the things. I'm going to go a little negative side here because you got triggered by your comment about how painful it can be. And earlier, you know, I know you share our interest in.
Elevating ethical behavior, especially for our students that are going to be entrepreneurs and innovators. So what, what's the most troubling thing you tend to see startups get do as they start to fail?
Yeah, you know, there's, there's, it's almost choreographed. The, the set of moves a startup goes through when it starts to struggle. You try some pivots and, and that doesn't lead to bad behavior. You try to get a bridge loan from your existing investors. First off, you try to raise money from new investors and they say it ain't going to go. So then after that doesn't work, you go to your existing investors and say, please bridge us, give us money. For anybody who don't know what it is, enough money to get over this bridge to the point where we can sort things out. And boy, do you see some nasty dynamics between investors who are.
Willing to do it and those who don't want to do it, but also don't want to be deluded because basically anybody who steps in when they're in trouble, it'll be what's called a cram down where who's ever going to put the fresh money in is going to take a big, big chunk of equity at the expense, dilution expense of everybody else. And you can get these nasty board fights and the poor CEO, the founders are caught in the middle of this. So there's nastiness there. You then when that either works or doesn't, you start to try to sell the company. And boy, do you see some messy, nasty behavior there. A lot of it on the part of the acquiring entities. They're kicking the tires. Who wouldn't? You know, the entrepreneur gets excited because they get all sorts of expression of interest. You know, every competitor in the space wants to look at our company. Well, guess what, they want to sort of meet your employees. They want to see how much you're paying them, they want to learn more about your products and that. And they're all going to look and they're going to string you along. And so you get people who know that they've got clock is ticking, your cash is running out and they know how much cash you have. So you get some really awful behavior around mergers and acquisitions and the acqui hires, which I think again, it's a thing we lionize on the east coast and Silicon Valley. It's a great exit approach for lots of teams. Well, guess what? Not everybody goes right. That acquiring entity is doing a tryout and they're going to interview all your people. And some of them get to come and many of them don't. And it's painful. A team that's been working together really hard to sort of see that some of them don't make the cut is nasty. Founders themselves can do bad things. Transparency is really tricky at this stage when you're in trouble because if you're very open with your team about it or your investors, you can scare them off. And some employees may leave and that'll just hasten.
The downward spiral. And so.
Ethically you're torn up about how open and honest to be about what's going on and whether to misrepresent or at least be quiet. And so the founder has to make some tough choices. The last tough choice a founder has to make is whether to toss the keys on the table and basically say, hey, board, you know, I am obviously not going to make any money from this thing. I've got a lot of life ahead of me. I have better things to do. You drive and boy, if you want to sort of destroy permanently your relationships with venture capitalists, try that move. So, yeah, it's just pain and nastiness at a lot of the stages there.
Well, I'd like to then flip the coin though, and talk about what I've found that the last part of the book is truly extraordinary and talking about how to fail, but how to fail with integrity.
With your character in place. So let's talk about that because that to me is a key takeaway of what you've. I keep saying the book, but the book is just a manifestation of this.
These lessons or patterns you saw. But also I really like the last part of the book. So can you talk about that? The importance of integrity and character at the.
Yeah, for sure. The goal for a founder, if they're going to fail, I mean, you want to do your best not to, but if you're going to ought to be to fail. Well, and there are really two dimensions to that. Failing gracefully means that everybody who's owed money, and I don't mean your investors, but your vendors, your employees, the tax authorities, everybody gets repaid. Your customers get moved to a good place. If your product isn't going to be available, you move them to some competitor who can do for them what you've been doing and you're open with everybody about what happened. You help your employees find new work.
With your investors. It's so easy for the founder to basically, at this stage, a lot of founders will be embarrassed, they'll feel disgraced and they go silent and they don't reach out for help and they don't update people on what's going on. So your investors are actually. You lost their money. They knew that. Anybody who invests in startups knows that that's part of the game. But you do owe them an explanation and a thank you. So that's all. Failing gracefully. And then post the failure. Take some time to wind the thing down. And basically the experience is an entrepreneur is going to be surging with all sorts of emotion, sadness, anger, grief, rage at the co founder who dropped the ball or lost attention and all this stuff. And it takes time for those emotions to settle down.
And the best way for a founder to do that is to sort of alternate between distractions, you know, find a hobby do some exercise, something different side project and rumination, sort of reflecting on what happened. And eventually the founder will find a space, hopefully where they've learned from the experience. And unfortunately a lot of founders don't. They're at one of two extremes. Many founders will continue to blame everybody else and the universe for what happened in the not their own failings or faults or mistakes, and they haven't learned nothing. They're probably going to go found or try to found again and they'll make exactly the same mistakes over again. At the other extreme, you have people that take too much responsibility and so you want to avoid those extremes. The people who take too much responsibility will never be founders again. And some of them shouldn't be, but most of them would probably be perfectly fine to get back on the horse and do it again. And it's a shame for society if they don't try. So if you fail gracefully with transparency.
And if you can explain to people what happened, what your role was, what you did wrong, what you'll do differently next time, you're actually pretty well positioned to bounce back. And what we see in the research is that more than half of failed founders go back and found again. And the ones who really learned from the experience and failed well, I think are particularly well, well positioned to do it. They preserved relationships and reputations.
Yeah. As we like to say graceful, or I'm now adding the word graceful. I think that's a wonderful way to put it, Tom. Graceful failure is okay.
Unethical behavior is not.
That simple.
So we got a. Do you mind if we do a couple of questions that have been posted? Yeah. So let me read you this one. It came early on, but let me know if we covered it already. We'll discover it together as students and future founders. What is one important component most new founders overlook when starting a venture? What is the key initial step you would recommend to new founders? So maybe that's kind of a challenge in how to summarize that first block of conversation we had.
Yeah. So, you know, a big surprise to me with the work was how important industry domain expertise is for some startups, but not others. You know, the founders that I sort of at the very beginning, the catalyst for the work, they were building an apparel company. And it turns out that designing and manufacturing apparel is incredibly specialized steps and you better understand how they all fit together and how people are going to do that work. And my founders had no such experience and that got them in a lot of trouble. Food and beverage too. I mean, I'm sure you must at Stanford see a lot of folks launching, have a wonderful idea for some new food or beverage product. Takes a ton of experience. You know, how are you going to get a co packer? How are you going to get the packaging to jump off the shelf? When do you pay slotting allowances? When do you expand from local to national? So know whether the business you're in requires that. And there are many to launch Instagram you didn't need to have worked in photo sharing, you know, so, so there are many startups that don't require it, but there's some that do and you need to know that the, the other thing to keep an eye out for, I mean we talked about the false start so that's just be aware that there's going to be a lot of pressure on you to build prematurely. And then we didn't talk a lot about the false positive but basically it's really tricky to spot the false positive and when because you need the early adopters and you will love the early adopters and you want to be loyal to them and serve their needs and, and an entrepreneur should do all those things but you can take it too far.
And so the first time founder needs to be aware that mainstream customers may be different. And if you can build a business happily around early adopters only good for you. But you probably need the mainstream.
Yeah. Thank you. I think this is related to what you said, but you may want to embellish it. Another.
Person posted.
Founders are almost inherently strong headed and obviously believe they are right and have a better idea.
Part of the way why they're starting the company. Knowing this, how can you convince them to follow your advice and avoid these pitfalls either before they start a company or when they're in the thick of or headed toward a catastrophic failure? And this is related to another one. How do you know if an entrepreneur is coachable and will listen when things go bad in early stage? So it looks like that's a theme of a number of these questions.
Boy, the second one's easy. I mean you must, you work with literally thousands of students over the years and it's pretty clear to me at least and I bet to you when somebody's listening and particularly if it's repeated contacts, whether they have and you don't expect of course an entrepreneur to do everything as an advisor that you tell them to do that would be a big mistake because they're going to get whipsawed by lots of different advice. So it is the entrepreneur's job to sort through lots of conflicting views. But I don't find it hard to figure out who's coachable. And I think that would be true for a lot of good investors. They look for that. And everybody listening who aspires to raise money should know that.
Entrepreneur, excuse me, Investors are going to be on the lookout for that.
Yeah.
The overconfidence thing is it comes with the territory. Right. We need entrepreneurs to be confident that they've got a winning formula. If people were too sober minded about the odds of success, no one would do this. Society wouldn't get amazing new products. So it does work. And when it works, we get great stuff. And even when it doesn't work, people learn things and sort of can bounce back and do other great stuff.
Well, I'm going to steal these last couple of minutes to just finish on a question for you. So it's wonderful to hang out with you and think about the last 25 years of entrepreneurship education and just how far it's come. And I'm including teaching design as well as teaching. Taking novel.
Stuff to market or to society has been wonderful. Why are you optimistic about the next 10 years in our field that we, our occupation, this notion that. Yes, okay, we've proven, thanks to Harvard, actually, because you were the pioneers long ago.
We'Ve proven you can teach entrepreneurship and innovation. But what makes you optimistic about this coming decade for those of us who do teach, and that means for everybody in this room who learn, because someday maybe they'll be a teacher.
Yeah. So the optimism comes from two things. And you're at the forefront of certainly one of them and in many ways the other.
We're.
Learning how important it is to pull ethics into the curriculum. And ethics comes in two flavors. It's sort of the moves that an entrepreneur makes. When do you fire your co founder ethically? And then it's the ethics of the emerging technologies, privacy and all that. And they're related in some ways. The entrepreneurship ethics. When do you misrepresent your progress? At what point does it become Theranos?
And so I think when we figure out how to teach this and how to work it into our curriculum, the world will be a better place. No doubt about it. Entrepreneurs will be better equipped to think through these tricky choices they have to make. The second thing that's got me excited, and.
Stanford's sort of again, right in the thick of it. MIT certainly is, and I think Harvard is too, is tough tech. People use different terms. MIT says tough tech and we love that. Hard tech, emerging tech Deep tech, frontier tech. But everybody I think knows what I'm talking about. This is space tech. It's, it's autonomous vehicles. It's a lot of clean tech technologies and they are bloody difficult. We know how to do software basically you usually can make the thing, but there's a lot of market uncertainty. And lean startup turns out to be the perfect way to sort through the market uncertainty and then you make it and you got a winning business. We know how to do biotech too. There's actually often no market uncertainty. If the drug works and sort of solves the problem, solves the medical problem, people are going to adopt it. But there's enormous technical uncertainty. We got a well oiled machine for putting money for the FDA testing and putting money in at the different phases and then selling the thing to big pharma, et cetera, et cetera. What we don't yet have is a machine for turning out tough tech and tough tech's problem. Because if you think about it, there's both market uncertainty, profound market uncertainty, think better place and technical uncertainty. And so the entrepreneurs who launch those businesses have to confront very long development cycles, huge amounts of capital and we don't have an established way of funding these businesses. And so I think as entrepreneur educators, we're going to spend a lot of time at all these places figuring out how to move those businesses forward and how to train entrepreneurs to run those businesses. And that's important because these are the very businesses that are going to make a huge impact on society if they work. Space tech, clean tech, ag tech, we can go right down the list.
Thank you for that, Tom. I'm going to urge my colleagues, my teaching colleagues at Stanford to listen to these last three minutes. You just gave us a call to action and it's been terrific to serve on your advisory board for those 25 years too out here. And I hope you'll keep me around. But most of all, thank you, thank you, thank you for sharing your wisdom and your thoughts about these topics today. They're very, very important and I know that this live audiences and the others will benefit greatly from.
Thank you Tom. And thanks to everybody at STVP for this opportunity.
All right, great. There'll be some upcoming ETLs. Keep your eyes open at ecorner Stanford Edu and ETL Stanford Edu and of course the YouTube channel. We'll see you at the next seminar.
More from Tom

"Why Startups Fail" with Tom Eisenmann, Author & Harvard Business School Faculty Chair

Why Startups Fail with Tom Eisenmann (HBS Professor) || Harvard Alumni Entrepreneurs

12. Tom Eisenmann & The Other F Word (Failure) | FOMO Sapiens with Patrick J. McGinnis







