Whenever a company dominates an industry for many years and continues attract top talent, it pays to examine how they operate. Google is one such company. Eric Schmidt and Jonathan Rosenberg wrote it all down in a book called “How Google Works.”
The book has a lot of tactical advice about things like fostering innovation, designing products, hiring and retaining talent, and decision-making, but I think there is an underlying philosophy common to all the advice: Invest time and money in Going Deep to find the best solution to the problem.
That might seem simple, obvious, and probably something all companies claim to do. But you probably know that’s more talk than action. Think of losing weight, it’s simple: eat less and exercise more. Very hard to execute. Very few people do it.
The concept is best articulated in their discussion on product development: “Bet on Technical Insights, not market research.” A technical insight is a solution that emerges only after a very deep understanding of a topic; something that addresses the absolute core of a problem or a need (as opposed to tackling symptoms). Schmidt and Rosenberg define a Technical Insight as “a new way of applying technology or design that either drives down the cost or increases the functions and usability of the product by a significant factor. A “significant factor” means that the results of using a Technical Insight should be “obvious” and clear to any user, requiring very little marketing.
For example, when Google was developing the original search algorithm, the Insight was that the best results would be dependent not just identifying the content of the website, but having a understanding of the context of the website. The standard Search approach at the time was to find the optimal match between the search terms and the content of website. They added on a layer of context to evaluate the quality of the website (i.e. :how many pages link to it, and what type of web pages). The insight was coming up with a way to judge the quality of page that took into account more than just surface level matching.
To me, this approach is similar to a “First principles” thinking concept: You get to the very core or essence of the use case or problem you are looking at, and then build out from there.
To be clear: you can still have a great success and progress by taking an incremental approach: this means using your competitive advantages to move into adjacent markets or make improvement in pricing, marketing or distribution. Such strategies CAN be well-served by market research and are useful for established businesses, looking for steady growth in healthy markets. But, when you need 10x growth, or when you’re fundamentally trying to disrupt an industry with a new product, you need to get to that technical insight that is true shift in how to solve the use case.
“Going Deep” applies to more than just product development, but people development (hiring and promoting), goal setting, and decision-making. When you’re really looking to achieve superior performance in any of these areas, there are no lightweight solutions. It’s time and money and effort. Of course, not everything can take this approach, and you can certainly achieve great performance allowing incremental progress to compound over time. But the Google approach is to strives for 10x changes, that’s how the company is designed, it is the underlying architecture of the “Operating System” as it were, behind How Google Works.