Source
How Google Works (book_cube)
Short review of Eric Schmidt and Jonathan Rosenberg's book on Google management practices.
Source
How Google Works (book_cube)
Short review of Eric Schmidt and Jonathan Rosenberg's book on Google management practices.
How Google Works
Authors: Eric Schmidt, Jonathan Rosenberg, Alan Eagle
Publisher: Grand Central Publishing; Манн, Иванов и Фербер
Length: —
A practical leadership lens on how Google combines culture, engineering autonomy, and speed of execution.
Original
TranslationManagement / Leadership / Processes / Strategy / BigTech
How Google Works is best treated as an operating model for engineering-led organizations where people, information flow, and product speed matter more than heavyweight process.
1. Book map
1. Introduction
A shift from industrial management to smart creatives: less bureaucracy, faster learning loops, and stronger engineering ownership.
2. Corporate culture
Culture is behavior, not slogans: belief in mission, user focus, flatter structures, and decisions not dictated by HIPPO logic.
3. Strategy
In fast-moving markets, technical insight beats heavyweight strategy decks and long planning cycles.
4. Talent
Hiring quality is the strongest long-term lever. Interviewing is presented as a core leadership capability.
5. Decisions
Use data, minimize unnecessary decision volume, and define a clear owner for each critical call.
6. Communication
Managers act as information routers with open-by-default communication and psychologically safe problem framing.
7. Innovation
Create a "primordial soup" for innovation: user-first framing, OKR alignment, and iterative shipping.
8. Conclusion
Platforms and information advantage win over time; leadership quality depends on how well knowledge flows through the org.
2. Smart creative profile
- Combines technical depth with product understanding instead of staying in a narrow functional lane.
- Needs autonomy and context, but not micromanagement.
- Performs best under meaningful complexity, fast feedback, and real ownership.
- Thrives in environments where ideas are tested by evidence and prototypes.
3. Culture and org design
Translate values into everyday operating behavior, not just internal branding.
Keep product and architecture decisions close to engineers and user signals.
Prefer flatter spans where managers can coach without creating hierarchy drag.
Protect speed of prototyping, otherwise strategy remains presentation-level.
AdWords story (from the book)
The authors describe how an engineering group outside AdWords built a weekend prototype to improve ad relevance. The point is less about heroics and more about a culture where initiative can cross formal team boundaries.
4. Decisions and communication
Data-first discussions
Start from evidence and user outcomes instead of role authority.
Fewer decisions
Strong systems remove recurring manual choices by design.
Explicit owner
Every high-impact decision needs a named owner accountable for follow-through.
Short loops
Decisions must be revisited through fast feedback and measurable outcomes.
- Default to transparency and lower the cost of finding context.
- Use psychological safety to improve problem quality and decision quality.
- Act as an information router between teams, goals, and trade-offs.
5. Innovation loop with OKR
- Define the user problem and value hypothesis.
- Set objective and measurable key results.
- Ship an early version quickly.
- Collect live usage feedback.
- Iterate while keeping product and engineering discipline.
6. Typical anti-patterns
Treating culture as messaging while preserving old behavior.
Letting HIPPO-style authority override evidence from users and systems.
Building strategy from market narratives without technical differentiators.
Running critical decisions without clear ownership.
Delaying launches until perfect and losing learning velocity.
7. Recommended patterns
Define what smart creative capability means for your hiring bar.
Audit decision quality quarterly: data-driven vs authority-driven.
Introduce a lightweight decision log with owner and revisit date.
Run leadership communication in open-by-default mode.
Use iterative shipping + OKR to operationalize innovation.
Limit of the narrative
The success stories are intentionally polished. Treat the book as a source of leadership heuristics, then adapt them to your own organizational constraints.