Akshata Mohanty | Fullstack Engineer

My takeaways from `How Google Works`

I am trying to lose weight. And I figured the laziest way of doing that was to walk 4 kilometers back home from work. However, it gets lonely alone - there's only so much streetscape in Singapore! So I picked up How Google Works by Eric Schmidt and Jon Rosenberg to give me company as an audiobook. I don't really know if I lost a lot of weight in the process, but it definitely added a lot to my brain!

I have a feeling How Google Works by Eric Schmidt and Jon Rosenberg is going to be one of the defining books in my life. Even though the book was probably written with an intention of guiding corporates and entrepreneurs - it did help me consolidate some priciples that I’d like to incorporate into my life. How Google Works talks about Google as a company and provides an inside look into the foundations, principles and culture the company is built on. If books are meant to inspire growth, this one is definitely it. Here is a list of my five key takeaways from this amazing read.

Be a ‘smart creative’

The book centers around smart creatives, better known as Googlers. The description presented by Eric Schmidt about this genre of people is inspiring. These are people who are intelligent, agile, grow fast, and have a figure-it-out mentality. They are broad in their knowledge and skills and follow core principles of movement, elasticity and speed. Heck! I’d love to be one of these people - how can one not want to be - and not just because they get to work at Google!

Eric Schmidt, himself, has a lot to teach, being a smart creative leader. He is generous with his acknowledgement of this group of people being the defining pillars of Google’s success. He discusses ways of attracting, managing and retaining such talent - providing a balance of autonomy and direction. The synergy of the approaches, the real examples of success with them makes for a compelling argument.

My journey into software from Architecture started when I questioned a sub-optimal process in a firm, as an intern. I decided to make it better using code I mashed up together. Figuring out better solutions and caring about it has helped me speed up my own progress and growth. The book is all about the impact of such values working cumulatively (read: Google). It motivated me even more to chase after these principles with more aggression! A simple line in the book sort of stuck with me - it said Googlers often start with let me show you... It is basically about developing a bias towards thought, data and action - and being a do-er.

A psyche worth striving for - especially when Google Maps, Google Sky - all came out of this mindset! There’s an example in the book: a set of people unrelated to Google Ads, came up with solutions to make it better. Just because Larry Page stuck a post-it note somewhere saying These ads suck.

Concentrate on first principles

Foundations are important and everything comes from first principles. I am expecting some heated discussions with my MBA buddies over this. But it was funny and endearing how the book sort of dissed market research. Eric Schmidt minces no words in telling you to bet on technical insight, not market study. Market research can’t tell you what the customer doesn’t yet know he wants; but technical acuity can. He uses Henry Ford’s famous quote - If I had asked people what they wanted, they would have said faster horses. And then the fact that Google started out with no market strategy. And the case is closed.

Personally, now, my next goal is to concentrate on building acute technical insight. Today’s times requires one to grow big fast. And Eric Schmidt predicts that building platforms with a specialization is the key to next generation big products. He advocates the hedgehog concept - to be amazing at one key thing. And also, that technical insight beats all.

A strategy used at Google is to always ask the question to the PM:

what is the most important thing you do?

Already fixed a post-it note on my mirror with this.


Being the data-oriented company Google is, it gives a lot of numbers to quantify priority.

For example:

  • 80% time to 80% of your revenue;
  • 70-20-10 rule for resource allocation with 70% on main business, 20% for adjacent and 10% on completely new
  • 20% time for personal projects

What I found amazing was the fact that even though this is a company with almost infinite resources and talent, they still aggressively prioritize at a fundamental level. And they do so, quantitatively.

And here I am - struggling to keep track of my time - often spending 80% of time on things that make me 0% of my money! :D

This principle had to go on the list.

Keep it open

Where Jon Ronsenberg takes being called a router, as a compliment - it says a lot about how intrinsically the top management believes in the virtues of openness and trust. Apparently, Larry Page remembers everything that everyone does and follows up with them. Eric Schmidt , does the same, just with notes. The products are open, the board letters are open, OKRs are open and anyone can talk to anyone.

For me, the philosophy of being open, is a slightly difficult one to incorporate. Being raised as a middle-class suspicious Indian - I like to hold my cards clos. Yet, the merit for this lies in the fact that more you open yourself up, the faster the refinement.

The quality of being optimistic is important to for any new venture. And openness reinforces that optimism in a way. We tend to hide things, when we are unsure. Metaphorically speaking, by being open, there’s no way to hide the flaws, hence would disappear.

Another imaginative way to keep the communication going is to reinforce the same principle in different ways. For example, the goal at Google has been excellence User Experience. To reinforce this, Eric Schmidt once talked about the increasing sophistication of users. Based on the increasing length of search queries. It was an interesting statistic that people didn’t know about. And I can see why that would immediate pique an interest towards striving for better UX. Hence, reinforcing the idea.

I also liked the idea of keeping your OKRs openly available. It is one way of getting peer pressure to work for you. Helps keeps things ambitious as well as realistic - stops you from putting something on your todo-list just to check it off (I’m guilty!).

Another intriguing point, was the idea of doing a self review - and using that as a basis for a 360. I often fret if I’m completely off in my judgement about myself, my growth and performance. Getting a random review, without any context is like writing an essay without any research. A review in context of a self-review would definitely be a more through, insightful one.

PS: The book talked about an app called Snippets to keep track of work done everyday. Could be compiled for weekly progress reports and milestones? If there are any Googlers reading this, and the code is open-source - would you be so kind to send me a link? Just curious. :)

Be anti-fragile

My favorite takeaway of all - Fail well.

Technically, it tells you to figure out a way to let people experience the product. And to fail fast, fail well. Essentially, that failure should get you new data and new learnings. Ideas should be morphed, not changed and iterations should always be based on learning.

It made failing well sound like a skill. Which it is.

On the personal day to day front, we often hear how failure is a stepping stone for success. But no-one ever emphasizes that just experiencing failure is useless. Unless you take the time to extract meaning and tangible knowledge out of it. The books talks about having a playbook - for everything. About the importance of a coach. Someone who might not be better in the playing field, but is good at observation. Someone to distil the learning from watching you to provide you with the knowledge. Which is your advantage.

Last but not the least, being a great believer in resilience, I loved the comparison between the two.

Resilient remains the same, but anti-fragile changes to evolve.

Was this helpful? Please share.

Hi, I'm Akshata. Fullstack engineer at Rakuten Viki. Architect-turned-software-developer. I like to build apps with AI. I also like teaching, food & MMA.