A Button Without The Treat

A few months ago I wrote a post entitled +1 is Explicit, but is not Relevance Feedback.  I am often personally concerned that, with many of the posts I write, I am being pedantic.  However, last week TechCrunch came to the same conclusion: +1 Is Like A Button You Push For A Treat — Without The Treat.  Some highlights:

I understand the concept behind the +1 Button — it’s a smart one. You get people to click it and it improves the page’s search ranking for logged-in Google users with social connections (and eventually maybe all results). At least I think that’s how it works. But I have a hard time believing that all of you actually clicking on the button really get why you’re doing it.  Don’t get me wrong, it’s great that you’re clicking on it! I am too on some of our stories. But I can’t help but get the feeling that it’s a bit like a cruel experiment we’re running. We put up a button, you click on it because it’s there, expecting you’ll get a treat. But there is no treat.

As I was saying a few months ago, +1 allows for explicit signaling.  But that signaling just isn’t a relevance feedback-type of signaling.  The person doing the clicking doesn’t actually get anything “fed back” from that action to their ongoing information seeking task.  TechCrunch continues: Continue reading…

They Won People Over By A Logical Argument

Via @glinden, I enjoyed this article on why GDrive (an early cloud document/file store) was never launched by Google:

At the time [2008], Google was about to launch a project it had been developing for more than a year, a free cloud-based storage service called GDrive. But Sundar [Pichai] had concluded that it was an artifact of the style of computing that Google was about to usher out the door. He went to Bradley Horowitz, the executive in charge of the project, and said, “I don’t think we need GDrive anymore.” Horowitz asked why not. “Files are so 1990,” said Pichai. “I don’t think we need files anymore.”

Pichai apparently went on to explain in more detail why files are no longer needed.  It has to do with the notion that, in the cloud you just have data and information.  Organizing that information into files is not necessary, especially when you can just start editing that information directly in Google Docs.  I’m going to ignore for a moment the “don’t be evil” ramifications of data portability and lock-in that comes through the dissolution of explicit files — how am I supposed to export my data into the Microsoft Cloud Word or into Open Office or into VisiWord whatever else I’d like to use, if files do not exist?  Instead, I’m going to focus on how this decision was arrived at:

When Pichai first proposed this concept to Google’s top executives at a GPS—no files!—the reaction was, he says, “skeptical.” [Linus] Upson had another characterization: “It was a withering assault.” But eventually they won people over by a logical argument—that it could be done, that it was the cloudlike thing to do, that it was the Google thing to do. That was the end of GDrive: shuttered as a relic of antiquated thinking even before Google released it. The engineers working on it went to the Chrome team.

This is what I find absolutely fascinating.  Here is a company that A/B tests everything in a heavily data driven manner, down which of 41 shades of blue the link anchortext should be.  So you would think that such a momentous decision about killing the whole GDrive project would be data driven.  It was not.  I quote again:

But eventually they won people over by a logical argument—that it could be done, that it was the cloudlike thing to do, that it was the Google thing to do.

Here is an instance where an important decision potentially very large service was made not by the data, but by a HiPPO, the highest-paid person in the room.   Continue reading…