Google Went “Code Red” to Save Google Buzz

Here’s the story of how panicking just enough may have saved Google’s answer to Facebook and Twitter.

Last week, Google launched an add-on to Gmail called Google Buzz. Almost immediately, the world howled with complaints that the product exposed users’ privacy by publishing lists of followers made up of the people a user e-mailed and chatted with most.

This made Google Buzz a danger zone for reporters, cheating spouses, mental health professionals, and anyone else who didn’t want to tell the world who they e-mailed or chatted with most.

But since this early failing, Google employees — specifically VP of product Bradley Horowitz and Buzz product manager Todd Jackson — have done a rousing job answering criticism from users and the media with rapid-fire updates to the product.

It wasn’t easy.

Horowitz and Jackson’s first move was to set up a  “War Room” for Buzz, where engineers and product managers could plot and push immediate changes to the product. Then, on Friday, the team took questions at a company-wide meeting with Google employees. With that feedback, Jackson pushed Buzz into “Code Red” starting on Saturday so that all updates to Buzz code would push as soon as possible.

With the proverbial alarm bells ringing, Buzz team members decided to stay at Google until the product was fixed. A Google spokesperson said, “Some of them [were here] straight through Friday and Saturday nights and through late Sunday, making changes.” A bunch of Googlers actually slept two nights in a row at the Googleplex.

A week after the complaints, Google corrected all the privacy flaws. Back in 2007, it took Facebook a month to figure its way out of the Beacon privacy mess.

Here’s the Google Buzz timeline:

(via Silicon Alley Insider)

Reblog this post [with Zemanta]