Tag Archives: Google

Bill Campbell, the Trillion Dollar Coach

Leave a reply

I had so often heard of this hidden secret of Silicon Valley that when I read about a book written about him, I had to buy and read it immediately. Which I did. And what about the authors: first and foremost, Eric Schmidt, the former CEO of Google…

I had mentioned Campbell 3 times here:

– first in 2014, in Horowitz’ The Hard Thing About Hard Things: there is no recipe but courage. This is there I had Campbell picture just between Steve Jobs and Andy grove.
jobs-campbell-grove

– then in 2015, in Google in the (Null)Plex – Part 3: a culture. This piece is also mentioned in the new book: Google decide management was not needed any more and neither Schmidt, nor Campbell liked it. Here is how it was solved: “The newly arrived Schmidt and the company’s unofficial executive coach, Bill Campbell, weren’t happy with the idea, either. Campbell would go back and forth with Page on the issue. “People don’t want to be managed,” Page would insist, and Campbell would say, “Yes, they do want to be managed.” One night Campbell stopped the verbal Ping-Pong and said, “Okay, let’s start calling people in and ask them.” It was about 8 P.M., and there were still plenty of engineers in the offices, pecking away at God knows what. One by one, Campbell and Page summoned them in, and one by one Page asked them, “Do you want to be managed?” As Campbell would later recall, “Everyone said yeah.” Page wanted to know why. They told him they wanted somebody to learn from. When they disagreed with colleagues and discussions reached an impasse, they needed someone who could break the ties.”

– finally last year, in Business Lessons by Kleiner Perkins (Part II): Bill Campbell by John Doerr.

Not bad references! I am not finished with the Coach. I have never been a fan of coaching and I am probably wrong. Let me just begin. “I’ve come to believe that coaching might be even more essential than mentoring to our careers and our teams. Whereas mentors dole out words of wisdom, coaches roll up their sleeves and get their hands dirty. They don’t just believe in our potential; they get in the arena to help us realize our potential. They hold up a mirror so we can see our blind spots and they hold us accountable for working through our sore spots. They take responsibility for making us better without taking credit for our accomplishments. And I can’t think of a better role model for a coach than Bill Campbell”. [Page xiv]

On the next page, Schmidt explains he may have missed on important point in his previous book (How Google Works) where he emphasized the importance of brilliant individuals, the smart creatives. And this may be the higher importance of teams, as described in Google’s Project Aristotle. I just give a link form the New York Times about this: What Google Learned From Its Quest to Build the Perfect Team. New research reveals surprising truths about why some work groups thrive and others falter.

The first two chapters are devoted to the life of this extraordinary character. A tireless worker, who started as an American football college coach to become the CEO of high-tech companies such as Claris or Intuit before becoming the Silicon Valley star coach. All told on the occasion of his funerals in 2016. If you do not want to wait for my next blog and not buy the book you may want to read the slideshare from the authors, but first you should read his manifesto, it’s the people.

People are the foundation of any company’s success. The primary job of each manager is to help people be more effective in their job and to grow and develop. We have great people who want to do well, are capable of doing great things, and come to work fired up to do them. Great people flourish in an environment that liberates and amplifies that energy. Managers create this environment through support, respect, and trust.

Support means giving people the tools, information, training, and coaching they need to succeed. It means continuous effort to develop people’s skills. Great managers help people excel and grow.

Respect means understanding people’s unique career goals and being sensitive to their life choices. It means helping people achieve these career goals in a way that’s consistent with the needs of the company.

Trust means freeing people to do their jobs and to make decisions. It means knowing people want to do well and believing that they will.

Entrepreneurship, startups and luck : Google according to Daniel Kahneman

1 Reply

I offered Thinking Fast and Slow by Daniel Kahneman a few months ago and this morning the reader made me read pages 200-1. It’s a great lesson about how luck plays an important role in startup creation, through the Google story. So I give you below the full extract.

“A compelling narrative fosters an illusion of inevitability. Consider the story of how Google turned into a giant of the technology industry. Two creative graduate students in the computer science department at Stanford University come up with a superior way of searching information on the Internet. They seek and obtain funding to start a company and make a series of decisions that work out well. Within a few years, the company they started is one of the most valuable stocks in America, and the two former graduate students are among the richest people on the planet. On one memorable occasion, they were lucky, which makes the story even more compelling: a year after founding Google, they were willing to sell their company for less than $1 million, but the buyer said the price was too high. Mentioning the single lucky incident actually makes it easier to underestimate the multitude of ways in which luck affected the outcome.

A detailed history would specify the Google’s founders, but for our purposes it suffices to say that almost every choice they made had a good outcome. A more complete narrative would describe the actions of the firms that google defeated. The hapless competitors would appear to be blind, slow, and altogether inadequate in dealing with the threat that eventually overwhelmed them.

I intentionally told this tale blandly, but you get the idea: there is a very good story here. Fleshed out in more detail, the story could give you the sense that you understand what made Google succeed; it would also make you feel that you have learned a valuable general lesson about what makes businesses succeed. Unfortunately, there is good reason to believe that your sense of understanding and learning from the Google story is largely illusory. The ultimate test of an explanation is whether it would have made the event predictable in advance. No story of Google’s unlikely success will meet that test, because no story can include the myriad of events that would have caused a different outcome. The human mind does not deal well with nonevents. The fact that many of the important events that did occur involved choices further tempts you to exaggerate the role of skill and underestimate the part that luck played in the outcome. Because every critical decision turned out well, the record suggests almost flawless prescience – but bad luck could have disrupted any one of the successful steps. The halo effect adds the final touches, lending an aura of invincibility to the heroes of the story.

Like watching a skilled rafter avoiding one potential calamity after another as he goes down the rapids, the unfolding of the Google story is thrilling because of the constant risk of disaster. However, there is an instructive difference between the two cases. The skilled rafter has gone through the rapids hundreds of times. He has learned to read the roiling water in front of him and to anticipate obstacles. He has learned to make the tiny adjustments of posture that keep him upright. There are fewer opportunities for young men to learn how to create a giant company, and fewer chances to avoid hidden rocks – such as a brilliant innovation by a competing firm. Of course there was a great deal of skill in the google story, but luck played a more important role in the actual event than it does in the telling of it. And the more luck was involved, the less there is to be learned.”

Goomics (Part III) – About Patents

Leave a reply

My final post about Goomics deals with Manu Cornet’s views on Patents. They are not that different from mine: I copied his view below (I hope he does not mind this limited copyright infringement) whereas you can read my slideshare contribution. You may also try to guess what invention Cornet’s is referring to and what is the Australian patent I use in my class. It was granted and then revoked, shoudl you be interested to know about it…

Goomics by Manu Cornet (Part II)

Leave a reply

I’ve reached letter O of Goomics by Manu Cornet. (you can see my previous post about the book here). My favorite piece is at letter N for Nerds. I hope this author will not complain about my copying it here…

I agree with the author. That much for lousy jokes, but I love it. And a more serious one, the amazing growth of Google with its 4 CEOs.

Thanks a lot for the author for new contribution about Google.

A New Yorker article about 2 Google developers : The Friendship That Made Google Huge

Leave a reply

The New Yorker just published a beautiful article abotu two google developers. The Friendship That Made Google Huge is subtitled Coding together at the same computer, Jeff Dean and Sanjay Ghemawat changed the course of the company—and the Internet.


The company’s top coders seem like two halves of a single mind.
Illustration by David Plunkert

Here are some extracts:

Sanjay Ghemawat, [is] a quiet thirty-three-year-old M.I.T. graduate with thick eyebrows and black hair graying at the temples. Sanjay had joined the company only a few months earlier, in December. He’d followed a colleague of his—a rangy, energetic thirty-one-year-old named Jeff Dean—from Digital Equipment Corporation. Jeff had left D.E.C. ten months before Sanjay. They were unusually close, and preferred to write code jointly. In the war room, Jeff rolled his chair over to Sanjay’s desk, leaving his own empty. Sanjay worked the keyboard while Jeff reclined beside him, correcting and cajoling like a producer in a news anchor’s ear.

[…]

Today, Google’s engineers exist in a Great Chain of Being that begins at Level 1. At the bottom are the I.T. support staff. Level 2s are fresh out of college; Level 3s often have master’s degrees. Getting to Level 4 takes several years, or a Ph.D. Most progression stops at Level 5. Level 6 engineers—the top ten per cent—are so capable that they could be said to be the reason a project succeeds; Level 7s are Level 6s with a long track record. Principal Engineers, the Level 8s, are associated with a major product or piece of infrastructure. Distinguished Engineers, the Level 9s, are spoken of with reverence. To become a Google Fellow, a Level 10, is to win an honor that will follow you for life. Google Fellows are usually the world’s leading experts in their fields. Jeff and Sanjay are Google Senior Fellows—the company’s first and only Level 11s.

And more about dual creativity. Quite fascinating!

It took Monet and Renoir, working side by side in the summer of 1869, to develop the style that became Impressionism; during the six-year collaboration that gave rise to Cubism, Pablo Picasso and Georges Braque would often sign only the backs of their canvases, to obscure which of them had completed each painting.
[…]
In “Powers of Two: Finding the Essence of Innovation in Creative Pairs,” the writer Joshua Wolf Shenk quotes from a 1971 interview in which John Lennon explained that either he or Paul McCartney would “write the good bit, the part that was easy, like ‘I read the news today’ or whatever it was.” One of them would get stuck until the other arrived—then, Lennon said, “I would sing half, and he would be inspired to write the next bit and vice versa.”
[…]
François Jacob, who, with Jacques Monod, pioneered the study of gene regulation, noted that by the mid-twentieth century most research in the growing field of molecular biology was the result of twosomes.

You should read the article…

Goomics by Manu Cornet

Leave a reply

I must thank sincerely Nicolas for offering me today Goomics by Manu Cornet, subtitled Google’s corporate culture revealed through internal comics.

It looks great though I have read only the 1st two chapters (A is for Android and B is for Bonus). It is funny for sure if you know a little about Google.

It begins with a Foreword this way: “Forewords are boring. I never read them myself. Please go ahead and turn the page now.” I did not and was right not to! I think this may become another bestseller about Google… I might tell you more as I read it…

Google is 20 years old

Leave a reply

Google was incorporated in California on September 4, 1998 so the company is just 20 years old today. The technology is older, it was called BackRub initially (in 1996) and was an internal web site at Stanford University, google.stanford.edu and in September 1997, google.com was registered as an independant web site. You can see below some historic images

and the various logos.

There’ve been many books about Google, some of them are great. I blogged about most of them, Work Rules! a few weeks ago, In The Plex in mid 2015, How Google Works in late 2014, Dogfight in early 2014, I’m Feeling Lucky in 2012. Indeed I blogged a lot about the company as you may see from the Google tag.

If Fairchild was the emblematic Silicon Valley company, founded in the 50s, it was followed by Intel in the 60s, Apple, in the 70s, the 80s have seen Cisco and Sun Microsystems, and Google symbolizes the 90s (Yahoo might be forgotten soon). Facebook belongs to the 2000s, the 2010 decade is still open I think. But the lessons learnt from the years of Google are just unique. The technology, the product, the startup growth, the teams have just changed the way we look at business for good and sometimes bad….

Work Rules! by Laszlo Bock – Conclusion: the obligation to dissent

Leave a reply

It took me a while to read Bock’s book. It is dense, ambitious, convincing, despite the fact that “Google sounds too good to be true” [Page 318]. There would be so much to say and the diversity of topics addressed by Bock is so broad. If you deal with people, if you manage teams, I think you should read it (I do not manage people and still I think it will be immensely useful to me!).

Another example after my four posts: Bock mentions of of McKinsey values: “uphold the obligation to dissent” [Page 319]. And an example follows on the same page: I was serving a client whose merger was yet to prove disastrous. The client asked for a recommendation on how best to set up a venture capital business. The data were pretty clear. Aside from a few notable examples, like Intel Capital,most corporate venture-capital efforts were failures. they lacked the expertise, clarity of purpose, and physical proximity to where the most lucrative deals were being hatched. I told the senior partner it was a bad idea. I showed him the data. I explained that there were almost no examples of these kinds of efforts being successful, and none that I could find that were thousands of miles outside of Silicon Valley and run by people who lacked any engineering background.
He told me that the client was asking how to set it up, not whether to to set it up, and that I should focus on answering the client’s question.
Perhaps he was right. Or perhaps he had some superior insight into the issue that trumped my data, Maybe he’d already made that argument to the client, and they’d rejected it.
But to me it felt like I’d failed.I thought the obligation to dissent required me to speak up, so it was all the more gut-wrenching to see my concern brushed aside.

Again Google might sound too good to be true, but this is the 5th or 6th book I read about Google from insiders and from outsiders, and the messages are quite consistent. A final quote from page 339: In the introduction I posited that there are two extreme models of how organizations should be run. The heart of this book is my belief that you can choose what type of organizations you want to create, and I’d be shown you some of the tools to do so. The “low-freedom” extreme is the command-and-control organization, where employees are managed tightly, worked intensely, and discarded.The “high-freedom” extreme is based on liberty, where employees are treated with dignity and given a voice in how the company evolves.
Both models can be very profitable, but this book presumes that the most talented people on the planet will want to be part of a freedom-driven company. And freedom-driven companies, because they benefit form the best insight and passion of all their employees are more resilient and better sustain success.

Work Rules! by Laszlo Bock (part IV) – Managers

Leave a reply

Google has been famous for defiance of authority. Bock develops this further.

At google, we have always had a deep skepticism about management. This is just how engineers think: managers are a Dilbertian layer that at best protects the people doing the actual work from the even more poorly informed people higher up the org chart. But our Project Oxygen research, which we’ll cover in depth in chapter 8, showed the managers in fact do many good things. It turns out that we are not skeptical about managers per se. Rather, we are profoundly suspicious of power, and the way managers historically have abused it. [Page 118]

Acton who said “Power corrupts; absolute power corrupts absolutely” also wrote: Great mean are almost always bad men, even when they exercise influence and not authority: still more when you superadd the tendency or the certainty of corruption by authority, there is no worse heresy than that the office sanctifies the holder of it. That is the point at which … the end learns or justifies the means. [Pages 119-20]

It was such a deeply held belief that in 2002 Larry and Sergey eliminated all manager roles in the company. We had over three hundred engineers at the time, and anyone who was a manager was relieved of management responsibilities. Instead every engineer in the company reported to Wayne Rosing. It was a short-lived experiment. Wayne was besieged with requests for expense report approvals and for help in resolving interpersonal conflicts, and within six weeks the managers were reinstated. [Page 190]

Still Project Oxygen initially set out to prove that managers don’t matter ended up demonstrating that good managers were crucial. [Page 188]. I will let you read Chapter 8 and here are the 8 rules from the study [Page 195]:
1- Be a good coach.
2- Empower the team and do not micromanage.
3- Express interest/concern for team members’ success and personal well-being.
4- Be very productive/results-oriented.
5- Be a good communicator – listen and share information.
6- Help the team with career development.
7- Have a clear vision/strategy for the team.
8- Have important technical skills that help advise the team.

I cannot finish this new post without mentioning a link given by Laszlo Bock about the history of Silicon Valley: “Silicon Valley’s Favorite Stories”, Bits (blog), New York Times, February 5, 2013.


Robert Noyce, right, set up an atmosphere of openness and risk at Fairchild Semiconductor.Credit Courtesy of Wayne Miller/Magnum Photos

Work Rules! by Laszlo Bock (part III) – (the invisible) women in the workplace

Leave a reply

The gender gap has become a much more visible issue in 2018 and Bock is no exception (even if his book is older). But before I mention what he says about it, here are two recent and very interesting references:
– The New Yorker just published an article about the gender gap at work and particular at BBC: How the BBC Women Are Working Toward Equal Pay.
– France Culture tells the story of Margaret Hamilton, a software programmer on the Appolo project: (in French) Margaret Hamilton, la femme qui a fait atterrir l’Homme sur la Lune.


Margaret Hamilton during the Apollo program.• Credits : NASA

Now Bock: In one study conducted by Maura Belliveau of long Island University [1], 184 managers were asked to allocate salary increases across a group of employees. The increases aligned nicely with performance ratings. Then they were told that the company’s financial situation meant that funds were limited, but were given the same amount amount of funds to allocate. This time, men received 71 percent of the increase funds, compared to 29 percent for the women even though the men and women had the same distribution of ratings. The managers – of both genders – had given more to the men because they assumed women would be mollified by the explanation of the company’s performance, but that the men would not. they put more money toward the men to avoid what they feared would be a tough conversation. [Page 170]

[1] “Engendering Inequity? How Social Accounts Create vs. Merely Explain Unfavorable Pay Outcomes for Women” Organization Science 23 no 4 (2012) 1154-1174 published online September 28, 2011, https://pubsonline.informs.org/doi/abs/10.1287/orsc.1110.0691

Bock mentions another study on page 137 about graduates from Carnegie Mellon that is also mentioned in the New Yorker article as “As the economist Linda Babcock and the writer Sara Laschever explain, in their book “Women Don’t Ask,” women are less likely than men to negotiate for higher salaries and other benefits. At Carnegie Mellon University, for example, ninety-three per cent of female M.B.A. students accepted an initial salary offer, while only forty-three per cent of men did. Women incur heavy losses for their tendency to avoid negotiation. It is estimated that, over the course of her career, an average woman loses a total of somewhere between half a million and a million and a half dollars.” Additionally “Even when women do make it to the bargaining table, they often fare poorly. In “What Works: Gender Equality by Design,” the behavioral economist Iris Bohnet examines data from a group of Swedish job seekers, among whom women ended up with lower salaries than their equally qualified male peers. “Not only did employers counter women’s already lower demands with stingier counter-offers, they responded less positively when women tried to self-promote,” she writes. “Women, it turns out, cannot even exercise the same strategies for advancement that men benefit from.” When women act more like men, she suggests, they are often punished for it. Lean in, and you might get pushed even further back.