Comment by debatem1
7 months ago
I was there around this time and remember the first time someone said out loud that they were doing project Z because "that's what will get me promoted". I argued until I was blue in the face that it was a bad idea, but they didn't care: they had their objective and knew how to get it. Unhappily, everyone was right: he got promoted and the project was an expensive failure.
My two cents is that Google has been consumed by its performance review process; the amount of money made by advancing dwarfed the amount of money made by making advancements, and as always the metric was the outcome.
I agree with you somewhat, having spent ~4 years at Google... though I think "perf-driven development" is IMO a symptom and exacerbating factor, but not a root cause.
Advancement and fulfilling of personal ambitions is a common thing in basically every sufficiently large company. Google isn't unique in having that problem - nor is their promotion process markedly different than everyone else's!
What is different is that Google is extremely metrics and OKR driven, combined with a near-total absence of product leadership. There is often no broader product strategy besides "grow X by Y".
This results in a critical weakness where you can get promoted for shipping Obviously Dumb Shit, because it hits some ill-defined OKR. It's practically an annual tradition within Google's management: creatively interpret pointless and vague OKRs so that you can make a (contorted) argument that Projects X and Y contribute to it, so you can ship it and get everyone involved their promos.
People in other companies are ambitious and want to get promoted too! The difference is that in many other companies there are other sanity checks in place that you don't get promo'ed for shipping Obviously Dumb Shit.
Google's root problem IMO is that there is an extreme lack of product leadership and product vision at the very top levels of the company. This results in a near-total inability to mitigate meta-hacks of internal promotion systems.
At companies with more product strategy at some point someone at a high level goes "Projects X makes no damned sense!" and puts the kibosh on it. At Google Project X will ship, and then after its badness becomes inescapable, get shut down.
The dominant culture in the company began to mimic the history of Raghavan: failing upwards, short-term gains with long-term detriment. When you get back far enough you begin to see a recurring pattern of it with these MBA/exec types who basically only have a bean-counter, extractive, understanding of running a business or making things.
Do you have a link to anything about performance review process . I am curious how msft or nintendo which known for innovation handles it .