How Google Prepared to Compete
When Eric Schmidt arrived at Google, he stepped into a company that did not behave like a normal corporation. Offices were crowded, engineers sat everywhere, and status mattered far less than technical ability. Schmidt even shared a small workspace with an engineer because the company cared more about making room for builders than creating executive comfort. That detail captured the larger reality: Google was organized around product and engineering, not hierarchy.
As the company grew, outside pressure increased. In 2003, investor Mike Moritz warned that Google needed to prepare for a major fight with Microsoft, which was so dominant that it was discussed internally under a code name. The warning sounded reasonable. A company facing a giant competitor should make plans, set dates, and lock down a roadmap.
But that kind of planning did not fit how Google actually worked. Jonathan Rosenberg tried to produce a detailed multi-year product plan, the kind many large companies expect. Larry Page rejected it because he believed rigid plans trap talented teams inside yesterday’s assumptions. If a team discovers a better way, a fixed roadmap can become a barrier instead of a guide.
That early tension shaped a different view of management. Google still needed direction, but not the kind that turns creative people into followers of a script. The job of leaders was to point the company toward important problems, gather strong people, and let them improve the original idea. That approach became the base for how Google thought about competition, growth, and leadership.
Full summary available in the Readsome app
