Work Rules: What Google Got Right About People Strategy and What Did Not Travel

Laszlo Bock’s ‘Work Rules!’ was published in 2015, the product of over a decade of building people practices at Google during the period of its most extraordinary growth. Bock was Google’s Senior Vice President of People Operations from 2006 to 2016, and the book is his account of what that work taught him about building organisations in which people do their best work. It is candid, specific, sometimes counterintuitive, and, for HR professionals reading it in the mid-2020s, a document that requires reading on two levels simultaneously: as an account of what Google got genuinely right, and as a study in how context shapes what is transferable.

The book’s central argument is straightforward: most organisations manage people too tightly and invest too little in understanding what actually produces high performance. Bock argues for radical transparency, for giving employees significantly more autonomy than most organisations are comfortable with, for using data to understand and improve people practices rather than relying on intuition and convention, and for investing heavily in finding exceptional people, on the grounds that the gap between average and exceptional performance is larger than most organisations account for when making hiring decisions.

These are not novel propositions in the abstract. What makes ‘Work Rules!’ distinctive is the specificity with which Bock grounds them in actual Google practice, the data that Google used to inform its decisions, and the frank account of what worked, what did not, and what Google had to unlearn along the way.

The practices that ‘Work Rules!’ describes most effectively are, in my reading, three: the Project Oxygen findings on management effectiveness, the structured hiring process built around work sample tests and structured interviews, and the practice of sharing information with employees at a level that most organisations would find uncomfortable.

Project Oxygen is the best-known Google HR research output and the most practically significant part of the book. Google’s internal research team identified eight behaviours that distinguished the most effective managers at Google from the least effective ones. The finding that has been most widely discussed is that technical expertise ranked last on the list, below coaching, empowering the team, expressing interest in team members’ success, communicating clearly, and several others. THIS FINDING DID NOT SURPRISE GOOD HR PROFESSIONALS WHO HAD BEEN WORKING IN PEOPLE DEVELOPMENT, but having it come from Google, with Google’s data and Google’s credibility, gave it a weight and a visibility that years of academic research on the same point had not achieved.

The hiring process account is similarly valuable. Bock’s argument that work sample tests predict performance better than interviews, that structured interviews outperform unstructured ones, and that adding more interviewers beyond four provides diminishing returns, is well-grounded in the research and practically actionable. For organisations that are still running informal, unstructured hiring processes, this section of ‘Work Rules!’ provides both the evidence base and the practical guidance for doing it differently.

The transparency practice is the most culturally specific but also, in some ways, the most instructive. Google shared information with employees at a level that would be structurally difficult in most public companies and culturally difficult in most private ones. The practice of sharing almost all company information, including strategy, financial performance, and product roadmaps, with all employees, assumed a level of trust and a corresponding expectation of discretion that took years to build. But Bock’s account of what the transparency produced, in terms of employee engagement, intrinsic motivation, and the quality of ideas that came back to the leadership, is a compelling case for taking transparency further than most organisations currently do.

The significant limitation of ‘Work Rules!’ as a practical guide for HR professionals is the degree to which its most striking practices depended on three conditions that were specific to Google and not replicable in most organisations.

The first condition was talent density. Google, during the period Bock describes, was one of the most attractive employers in the world for a specific profile of highly capable, intrinsically motivated, analytically skilled person. The company could afford to hire slowly and select rigorously because the candidate pool was extraordinary. The practices Bock describes, the autonomy, the peer-driven management, the assumption of high intrinsic motivation, work exceptionally well when the talent density is very high. They work considerably less well when the organisation’s talent profile is more varied.

The second condition was financial performance. Google was, during this period, generating extraordinary returns on a relatively lean organisational structure. The financial capacity to invest in people practices, to run experiments, to sustain practices that had a long payback period, and to absorb the costs of the occasional experiment that did not work out, was not typical. Most HR organisations operate under budget constraints that make the “invest in people first” posture practically difficult, regardless of its strategic merits.

The third condition, and the most culturally significant, was the founding culture. Google was built from the outset by founders who had a strong egalitarian philosophy, a deep scepticism of hierarchy, and a genuine conviction that the best ideas could come from anywhere in the organisation. The practices that Bock describes were not interventions into a hierarchical culture. They were the natural expression of a culture that had never been hierarchical in the conventional sense. Transplanting those practices into organisations that have deep hierarchical roots, and most Indian organisations do, requires a cultural intervention that precedes and substantially exceeds the practice implementation itself.

The practices in ‘Work Rules!’ that are most directly applicable in the Indian organisational context are those that depend least on the Google-specific conditions described above. The structured hiring methodology translates well; the evidence base is universal even if the specific tools require contextualisation. The Project Oxygen findings on management effectiveness translate very well; the behaviours identified are recognisable across cultural contexts, even if the way they are expressed varies.

The practices that require the most significant adaptation are those that depend on high psychological safety and high trust in organisational transparency. IN THE INDIAN ORGANISATIONAL CONTEXT, THE ASSUMPTION THAT INFORMATION SHARED WIDELY WILL BE USED CONSTRUCTIVELY AND DISCRETELY IS HARDER TO BUILD THAN BOCK’S ACCOUNT IMPLIES. It is buildable; the conditions for it can be created. But it requires a deliberate, sustained investment in the trust infrastructure that Bock largely takes as a starting condition rather than as a developmental project.

The differentiated rewards practice, which Bock describes with considerable nuance, requires careful handling in organisations where perceived fairness is a dominant cultural value and where the norms around explicit performance differentiation are still evolving. The principle is sound. The implementation requires sensitivity to the specific equity norms of the organisational culture it is being introduced into.

‘Work Rules!’ is a book that every CHRO and senior HR professional should read, with two caveats clearly in mind. The first is the context caveat: Google’s conditions were unusual and the practices that depended on those conditions require substantial adaptation before they translate to other organisational contexts. The second is the timeline caveat: the book was written about a period, roughly 2006 to 2015, that predates the significant changes in the labour market, the technology landscape, and the competitive environment for talent that have occurred since. Some of the practices Bock describes have already been modified or retired by Google itself.

Read it as a rigorous account of what evidence-based people management can achieve, not as a playbook to be implemented. Use Project Oxygen as the most practically transferable section. Use the transparency and autonomy arguments as a directional challenge to whatever the current level of both is in your organisation. And use the talent density discussion as an honest prompt to examine whether the practices you are currently running are calibrated to the talent reality you actually have, rather than the talent reality you would have if you were Google in 2010.