Still, overcoming the cold start problem is deceptively difficult. Chen offers the example of Tiny Speck, the gaming company that would go on to become Slack. Tiny Speck had everything going for it: a star team, an exciting launch, and $17 million from respected investors (including Andreessen Horowitz, where Chen works). It also got plenty of people to try out the game, called Glitch. The problem was it couldn’t get people to stay.
What was the difference between Glitch and Slack? For one thing, Slack’s timing worked: It had anticipated distributed workforces and a need for text logs. But it also benefited from tiny, atomic networks. People joined in teams, and as those teams familiarized themselves with the product, they were likely to continue using it. (The magic number, according to Slack, is when a team has exchanged about 2,000 messages.) Later, the company grew by encouraging companies to adopt Slack across the entire workforce, knitting together many teams on one unified workplace tool.
Of course, network effects alone cannot explain a startup’s success or failure. Slack was just one of many workplace communication apps with a similar idea; not all of them had the same success. “For every successful launch like Slack, there are many more that are failures,” Chen acknowledges, “and they usually stumble right at the start.”
Both The Cold Start Problem and Anticipate Failure offer autopsies of several failed companies, but that can still leave a reader scratching their head. Chen points out that some startups achieve network effects because they provide services that are free, convenient, and easy to use. Other startups succeed for exactly the opposite reason: Their products are exclusive, invite-only, and hard to get. Ananth, in his case studies, locates the problems in various startups without offering a useful prediction to avoid those pitfalls in the future.
Another book from 2021 tries to provide a more comprehensive account of startup failure. Tom Eisenmann, who has taught entrepreneurship at Harvard Business School for the past 20 years, surveyed 470 failed startup founders about why their ventures went south. Their responses make up his book, Why Startups Fail.
Eisenmann rejects the idea that most failures come down to the founders, and even criticizes venture capitalists for focusing too much on finding the “right people” who have grit, determination, and industry acumen. Instead, he suggests that failures more often come down to a misjudgment of market need, growing too fast, and overly idealistic visions (all things, notably, that VCs encourage). Like any good business school professor, Eisenmann comes prepared with an armload of case studies. He pays particular attention to startups founded by his students—cases where the postmortem seems almost personal.
Why Startups Fail provides six reasons things go wrong, including neglecting customer research, finding the wrong stakeholders, and falling into a “speed trap” of growth at all costs. Eisenmann emphasizes that these mistakes are avoidable. But more important, like Ananth he advises founders to understand that failure is often part of the package. Toward the end of his book, he offers advice on how to handle failure when it inevitably happens.
In today’s startup environment, raising money might be easy—it’s what comes after that’s hard. Will these books help startup founders or investors avoid disappointments? Perhaps, but in the same way that millions of health books have helped humans avoid disease. Diagnosing the common reasons for death is one thing. Learning to live more healthfully is another.
If you buy something using links in our stories, we may earn a commission. This helps support our journalism. Learn more.
More Great WIRED Stories
For all the latest Technology News Click Here
For the latest news and updates, follow us on Google News.
