English version published 2026-11-08 with AI assistance. Attribution, source notes, and verification limits are retained in the text. 中文原文
Reading guide
A digest of The Venture Mindset. Gmail, which now has more than two billion users, was not an acquisition. It was an internal Google startup, built by employee number 23, Paul Buchheit, on a server next to his desk. The first users were other Google engineers, and the charter from his bosses was extremely vague: “We think this is an interesting area.” Inside a large company, a startup project will always compete for resources and attention. Whether it lives or dies depends, to a large extent, on the internal innovation process the company has designed: leaders who listen carefully, give people a vague brief and full support, watch the milestones, and decide when to kill what is not working. One reason Gmail worked is that management bet on giving every user 1GB of free storage—an expensive decision in 2004, and the one that ended the era of tiny email inboxes. Google’s approach was a venture mindset: put several horses on the track at once, let jockeys change horses along the way, and have the company design the track. That is an internal startup workshop. The word “intrapreneur” took off after Jobs, in a 1985 Newsweek interview, described the Macintosh team as “a group of people going in essence back to the garage, but in a large company.” The idea is not only for tech firms. Robin’s take: Google could keep funding internal experiments because it had found a business model that printed money. If it ever starts optimizing for operating efficiency instead of innovation, that may be the moment a great company peaks and begins to decline. Balancing the courage to innovate and fail with the need to be efficient and make money is the challenge every large company faces.
Full text — English translation
Design and build a track of your own.
For a lot of people today, Gmail simply is email.
Unlike YouTube or Nest, Gmail was conceived and built inside Google. The product that now has more than two billion users began with one engineer, Paul Buchheit, who joined Google in 1999 as employee number 23.
Gmail was an internal startup. Buchheit was talented, driven, inventive, committed, and stubborn. The product ran on a server next to his own desk. He gathered his first users—other Google engineers—and collected their feedback and requests. Together with a few engineers who helped him, they made up a startup team in miniature.
Gmail’s success is so striking that it is natural to put its story next to those of startups like Slack. If you do that, you miss the point, because Gmail was developed inside a large company.
Startup founders and their teams lack resources and experience. They need venture investors, and they need a track they can actually run on. People with a founder’s instincts inside a company need a similar track. Relative to the core search business, Gmail was really just an experimental side product. Its success is a clear demonstration of how well Google’s leaders could design that track.
A startup can put all of its energy, effort, and resources on a single idea. A large company cannot.
Any internal venture will compete for resources and attention, and it will not sit on the leadership team’s daily list. Whether a project like Gmail is viable, or doomed, is therefore decided to a large extent by the internal innovation process the company has designed for work of that kind.
In a 2007 interview, Buchheit said his bosses “asked me if I wanted to build some kind of email or personalization product. It was a pretty vague charter. They just said, ‘We think this is an interesting area.’ … They were very general—as if they were only saying, ‘Yes, we think there’s something interesting to do here’—but they didn’t tell me what features the product should have. Nobody really knew what this product was supposed to be.”
In the internal startup stories that work, leaders listen carefully to ideas from the team, encourage people to try more things, and pick the most promising ones to develop. The instructions are usually quite vague. Even without a clear direction from above, the team can explore freely in the early days, with few constraints—and the leaders still give them full support.
They also watch whether the project is hitting its goals or milestones, and they decide when to stop the ones that are not working. Buchheit has said that many of the ideas he raised at Google never went anywhere. That should not be a surprise. A lot of internal ventures are very high-risk.
Leaders also have to decide which projects to support all the way through.
One reason Gmail became such a success is that Google was generous with storage. Every address got 1GB for free, far more than anyone expected at the time. People no longer had to delete old mail, or worry about oversized attachments.
With that free gigabyte, the era of cramped email inboxes came to an end. In 2004, of course, that was an extremely expensive decision, and it was not Buchheit’s. It was made by the Google managers who had placed their bet on Gmail as a horse in the race.
Gmail was not Google’s only internal startup. The company started many small, independent projects inside the walls, and some of them later became scaled businesses. They were not designed and launched by a central office in the management chain, and they were not the product of detailed planning by senior leaders or the board. What made that possible was the venture mindset that ran through Google, and the way that mindset let several key ingredients come together.
Google had talented, highly motivated people, and it also had a process that encouraged internal ventures and was willing to absorb failure. Like other large companies, it could put several horses on the track at the same time. Its executives understood that in a corporate setting, good jockeys and good horses are not enough. You also have to build a track that supports them.
What Google did was design a track so that the jockeys and the horses could race efficiently—even if the first version of that track was a bit informal. Jockeys could change horses along the way. Many horses never finished. Some, with a bit of help, ran very fast. In effect, Google had built an internal startup workshop.
“Intrapreneurship” takes the prefix intra-, meaning “inside,” and adds it to entrepreneurship. The word appeared in 1978. A few years later The Economist used the new coinage in a feature. It only really entered the popular press after Steve Jobs used it in a 1985 interview with Newsweek.
Jobs said then that the Macintosh had been built by a group of intrapreneurs. In his words, the Macintosh team was “what is commonly known now as intrapreneurship—only a few years before the term was coined—a group of people going in essence back to the garage, but in a large company.”
Intrapreneurship is not only for tech companies. It ought to be a practice in every kind of firm.
It also requires a venture mindset. Tech founders spend so much time around VCs that they pick it up more easily than executives elsewhere. But any company can design a track for internal startups. Some designs can even turn the horses into cars, and turn a dirt racetrack into a Formula 1 circuit.
#TheVentureMindset
-----
Robin: “Google used to have a university atmosphere that encouraged professors and graduate students to explore as far as they wanted. The most important reason it could support that kind of innovation is that it found a business model that made a great deal of money—and then printed money like a press running at full speed. That is what allowed it to keep funding all kinds of internal experiments. If Google ever starts optimizing for operating efficiency instead of innovation, that may be the moment a great company reaches its peak and begins to decline. How you balance encouraging innovation and being willing to fail against the need to be efficient and make money is the challenge every large company faces.
The next note will look at another innovation giant: 3M.”
These articles are personal notes, book excerpts, and collected reprints. Figures and events reflect the time of the original publication, are not current information, and do not constitute investment advice.
Comments
What do you think? Share your experience or questions.
Sign in to comment, reply or like. Sign in / Sign up
Loading comments…