Article 6MCRR Enshittification of Google and the Men Who Killed Search

Enshittification of Google and the Men Who Killed Search

by
janrinok
from SoylentNews on (#6MCRR)
The specific process by which Google enshittified its search (24 Apr 2024)

owl writes:

https://pluralistic.net/2024/04/24/naming-names/#prabhakar-raghavan

All digital businesses have the technical capacity to enshittify: the ability to change the underlying functions of the business from moment to moment and user to user, allowing for the rapid transfer of value between business customers, end users and shareholders:

Which raises an important question: why do companies enshittify at a specific moment, after refraining from enshittifying before? After all, a company always has the potential to benefit by treating its business customers and end users worse, by giving them a worse deal. If you charge more for your product and pay your suppliers less, that leaves more money on the table for your investors.

Of course, it's not that simple. While cheating, price-gouging, and degrading your product can produce gains, these tactics also threaten losses. You might lose customers to a rival, or get punished by a regulator, or face mass resignations from your employees who really believe in your product.

Companies choose not to enshittify their products...until they choose to do so. One theory to explain this is that companies are engaged in a process of continuous assessment, gathering data about their competitive risks, their regulators' mettle, their employees' boldness. When these assessments indicate that the conditions are favorable to enshittification, the CEO walks over to the big "enshittification" lever on the wall and yanks it all the way to MAX.

The Men Who Killed Google Search

Uncle_Al writes:

https://www.wheresyoured.at/the-men-who-killed-google/

The story begins on February 5th 2019, when Ben Gomes, Google's head of search, had a problem. Jerry Dischler, then the VP and General Manager of Ads at Google, and Shiv Venkataraman, then the VP of Engineering, Search and Ads on Google properties, had called a "code yellow" for search revenue due to, and I quote, "steady weakness in the daily numbers" and a likeliness that it would end the quarter significantly behind.

For those unfamiliar with Google's internal scientology-esque jargon, let me explain. A "code yellow" isn't, as you might think, a crisis of moderate severity. The yellow, according to Steven Levy's tell-all book about Google, refers to - and I promise that I'm not making this up - the color of a tank top that former VP of Engineering Wayne Rosing used to wear during his time at the company. It's essentially the equivalent of DEFCON 1 and activates, as Levy explained, a war room-like situation where workers are pulled from their desks and into a conference room where they tackle the problem as a top priority. Any other projects or concerns are sidelined.

In emails released as part of the Department of Justice's antitrust case against Google, Dischler laid out several contributing factors - search query growth was "significantly behind forecast," the "timing" of revenue launches was significantly behind, and a vague worry that "several advertiser-specific and sector weaknesses" existed in search.

Read more of this story at SoylentNews.

External Content
Source RSS or Atom Feed
Feed Location https://soylentnews.org/index.rss
Feed Title SoylentNews
Feed Link https://soylentnews.org/
Feed Copyright Copyright 2014, SoylentNews
Reply 0 comments