6 ms·
On paper, Google's throw-everything-at-the-wall-and-see-what-sticks strategy (that has lead to a substantial Google Graveyard) seems like it was intended to all
by e_y_ 3y ago
On paper, Google's throw-everything-at-the-wall-and-see-what-sticks strategy (that has lead to a substantial Google Graveyard) seems like it was intended to allow for some parts of the company to innovate while keeping the core products stable and boring. In practice, many of those innovations (Google Inbox, anyone?) were not deemed profitable enough to keep around. Others were never given the resources to grow beyond an experiment. And even with a long leash, a big company project is never going to innovate as quickly as a startup.
This year, however, with the extremely deep cuts to Google's internal incubator (Area 120), it seems pretty clear that they've given up on this strategy, at least for anything that isn't somehow AI-related.
- teen 3y agoI mean that incubator was a total waste of money. No one did anything, everyone was a bser from the top, and 95% of the projects were total failures. I think there were maybe 3 "successful" projects.
- compiler-guy 3y agoPretty standard rate of failure for early stage startups.
- 121789 3y agoI think this is why these teams are really hard to have in a mature org. In reality maybe 5% of projects in one of these innovation orgs is actually great! But it’s impossible to evaluate and everyone else is thinking some variant of “this team is able to bs and show no value, while I have to hit real goals or risk being fired?” I think the incentives would have to be much different for it to work (e.g. much lower base pay + higher rewards for success)…..but at that point just join a startup
- seraphsf 3y agoWhich 5% of projects are really great? In my experience, presuming you have tight filters such that all of your projects are plausibly potentially great, you really don’t know until you try. That’s the point of an incubator. It’s not that hard to evaluate when something is working (ie the hard part in evaluation is false negatives, not false positives). In Area 120’s case there was no coasting - if anything there was a hair-trigger standard to shut down underperforming projects.
- mk89 3y ago3 successful projects can totally justify what you call waste of money. I sometimes wonder what people expect innovation is. You try and try and try. One thing is good and you must know how to use it - it can make history. If I understood right, chatgpt comes from one of such ideas.... so the question is also: who evaluates the ideas? How come that Google was not able to capitalize on that idea? So yeah, instead of treating the cause they treat the symptoms, like usual.
- deleted 3y ago[deleted]
- lapphi 3y agoAgreed, we are on ycombinator.com, after all. The patron saint of failed ideas.
- gedy 3y agoI think these type of teams are a good way to give talented devs a break from the grind at bigger companies, even if the chances of a new product is low. Not every company can afford these "paid vacations", but they do have some use at times.
- seraphsf 3y agoI ran one of the successful projects in Area 120. I joined Area 120 with huge skepticism. It was hamstrung and inefficient in its own ways. And I agree it didn’t reach its potential - largely because it was encased in Google 2020 instead of Google 2007. But to my surprise almost all of the projects were impressive, well-conceived, promising bets. And the people in Area 120 were among the top 10% of Googlers I worked with in my decade at the company. Google killed Area 120 because of bureaucracy and politics, full stop. Google is worse off because of it.
- jklm 3y agoSomewhat spicy take - if the people in Area 120 were among the top 10% of Googlers you worked with, they probably weren't the right builders to start a new vertical. Most of what makes people effective at large companies is neutral or negative value when applied to very early-stage companies.
- tomrod 3y agoThat assertion applies to the middle 80%, IME. The top 10% are the people you can drop on to any project of any size and any org structure and they adapt quickly and deliver. They adapt themselves accordingly.
- aleph_minus_one 3y ago> That assertion applies to the middle 80%, IME. The top 10% are the people you can drop on to any project of any size and any org structure and they adapt quickly and deliver. They adapt themselves accordingly. These are rather the top 10 % sycophants, not the top 10 % researchers or top 10 % programmers.
- tomrod 3y agoI didn't see that mentioned, perhaps I missed it. I read it as top 10% of performers.
- 3y ago
- jjulius 3y ago>Google Inbox Still so damn bitter about that death.
- Aeolun 3y agoIt’s weird that Gmail never reached that point. Even years later it’s still the same it was 10 years ago. I think after inbox died I just gave up on it and moved to fastmail.
- wyclif 3y agoI understand what you're saying (I miss Inbox, too). But end users like sameness and "it just works." Normies prefer stability over innovation when they are trying to get stuff done.
- abirch 3y agoNormies like sameness, this is why God gave us configs. You can default to normal but let the crazies customize.
- Cthulhu_ 3y agoThing is, they quit on it too quickly; sure, a lot of people would stick with gmail, but others - and following generations - would adopt and grow up with inbox. I think / suspect that many people develop habits of this type in their 20's and never move away from it for the next 60 years because it works. Example, people who still use vi(m) / emacs. Nothing personal, but as an example, they use it because they're used to it and have been for decades. And no editor that claims to be better will ever replace it for them.
- bayindirh 3y agoInbox was not deterministic. It's like a social media feed for your e-mail. I'd rather have my mails left as-is, and allow me to work with them the way I want. You don't have to be a "normie" to appreciate simple or old fashioned things. Most of the e-mails I receive is not for quick-consumption, and I prefer the standard way over Inbox's way. Maybe it was a solution trying to find a problem, IDK. I used it for 30 minutes tops.
- htrp 3y ago> at least for anything that isn't somehow AI-related. If you can't innovate at the base level of app design .... how do you have any hope of innovating for AI apps that require research/engineering/product/marketing collaboration?
- nextos 3y agoThat's true. What they need is what they had started doing, i.e. breaking down Google into Alphabet and letting some companies within the conglomerate act like startups. Why was this effort unsuccessful? Perhaps they were unable to get rid of middle management? I have had lengthy discussions with employees from several of their companies, e.g. Calico, and that seemed to be the case. This article only reinforces my view.
- chii 3y ago> Why was this effort unsuccessful? i suspect that they are unsuccessful for two reasons: failure is not death, and success is not riches (for those who did the work).
- bicepjai 3y agoI think you are talking about “innovators dilemma” great book by the way
- eslaught 3y agoIt's worth noting that was a turning point: the "more wood behind fewer arrows" policy adopted by Larry [1] initiated the die-off cycle of Google products. Prior to that, as far as I am aware, they were much more tolerant of products staying around in a mature-but-not-wildly-successful state. Afterwards, it seemed as if they would only keep things that maintained a trajectory to become as successful as their core products. Again, this was not entirely unpredictable. While I don't remember the details of that lecture, I remember the professor calling out these sorts of big shifts in cultural values as being typical of startups transforming into large companies. And Larry himself was part of the transformation, turning into (presumably, what he believed to be) what was needed to lead Google into its next stage as a large company. [1]: https://googleblog.blogspot.com/2011/07/more-wood-behind-fewer-arrows.html https://googleblog.blogspot.com/2011/07/more-wood-behind-few...
- leoc 3y agoWhat’s remarkable is that that phrase was already, at that time, notorious for having been a portent of doom at Sun Microsystems.
- jmcguckin 3y agoAll the wood behind one arrow…
- ChrisArchitect 3y ago..and now all that's left of Sun is the wood on the back of the Meta sign.
- Annatar 3y agoEvery time a socket is instantiated, Sun Microsystems comes alive; so too it is with NFS, and many other core technologies; there is lots that's left of Sun which still makes it live, even though it doesn't officially exist any more. And any time 0xide Computer ships a cloud in a rack with the Helios operating system powering it, Sun Microsystems shines bright as a beacon of indestructibility due to quality.
- nstart 3y agoIf I recall past discussions on this topic correctly, it wasn’t just about profits. I believe the incentive structures are setup around launches and not maintenance. If that’s correct, then that would lead to people launching, collecting rewards (bonuses, promotions, etc) and then abandoning.
- rizky05 3y agoMicrosoft today is more innovative than google IMO. They keep executing bold and controversial strategies, even though being older than google.
- pjmlp 3y agoIf we ignore the GUI civil wars for a bit, though.
- PessimalDecimal 3y agoAt roughly similar points in their lives, Microsoft and Google initiated video gaming platforms. Microsoft stuck with Xbox through seven years (iirc) of still-unprofitable growth to what it is today. Google abandoned Stadia after three years. Yeah, I think Google is looking more like an IBM in the long run, while Microsoft manages to innovate despite its age and size.
- jacquesm 3y agoThey made - and still make - one crucial error: you need to spin those projects that are simply viable out immediately after they take root. Otherwise you will end up with the brand advantage but there will always be the pressure to use the resources (people, mostly) more efficiently in terms of ROI. And so nothing ever lasts and slowly but surely your reputation as a reliable partner for new products is eroded. You can use your main brand for the launch, but then you have to be willing to support the child.
- Cthulhu_ 3y agoIn addition, I don't understand why they stopped them entirely, instead of spin them off as subsidiaries under e.g. Alphabet; make them financially self-reliant, have Google/Alphabet as the main shareholder, and give the people that worked on it (and whoever else wants to) the opportunity to continue working on the product. Some wouldn't have been viable, sure. Others were probably too ingrained in Google's hardware/software ecosystem to be separated out (although I wonder if nowadays everything Google runs on its cloud offering, which would make it simpler, just change the billing).
- beambot 3y agoMost of them were probably built on Google's core infrastructure in ways that make them difficult to externalize at sub scale. There's also compensation disparity - it's virtually impossible for a new startup / spinout to pay FAANG comp and remain profitable & nimble. This results in braindrain.
- martius 3y agoThe reason is quite simple: why spend engineering headcount on a less successful product? > Some wouldn't have been viable, sure. Others were probably too ingrained in Google's hardware/software ecosystem to be separated out (although I wonder if nowadays everything Google runs on its cloud offering, which would make it simpler, just change the billing). Google Cloud is built on top of Google's tech ecosystem, not the other way around.
- 3y ago