Hi, in case you haven’t been following along at home, I’ll give you the short catch-up info first. Blake Ross wrote a post criticizing some tips that Google recently tried. I agreed that I didn’t like the tips, primarily because the targeting was too poor (even substrings would trigger the tips). Danny Sullivan, who has covered the search industry for a decade, saw the tone of some of the discussion and wrote a good post about keeping perspective. He noted that folks should hold every company to the fire, not just Google. Right when it seemed like things were calming down, Michael Arrington decided to turn up the heat on the discussion up to the proverbial 11. He asked if this issue would be a tipping point where people would be much more negative toward Google. Arrington concluded with
And while Matt Cutts, the unofficial Google blogger, deals with the Ross post in a straightforward and honest way, I think he should be far more critical of his company. Even to the point of risking his job. Because that is exactly what Google needs right now.
I’ve never met Michael, but I respect him a lot. For example, I agree with pretty much everything he’s said about PayPerPost. But I believe his final statement (that I need to be more critical of Google on my blog) is dead wrong. To understand why, you need to know a little more about Googlers and how Google works.
Words can’t express how much I respect my colleagues at Google, but I’ll try. Googlers are smart, rational, and polite. They execute well on projects and listen to objections with an open mind. When they run up against an obstacle, they get creative and look for a new approach to solve the problem. Among the hundreds of Googlers I know, there’s also a strong streak of wanting to change the world for the better.
Google the organization in many ways mirrors the character of its employees. Google is a very polite, consensus-driven company. Usually if you get everyone in the same room and everyone explains their reasoning, the best decision emerges pretty quickly. As a result, I can’t recall ever hearing someone shout at Google. Even when issues are hotly debated, we tend to keep our discussion and our self-criticism within the company. So for me to be “far more critical” on my blog is not what Google needs right now. If anything, that’s more likely to burn bridges than to solve issues. I don’t have the outsider status that Scoble did. If disagree with something Google does, I go directly to the Googlers involved and I discuss it with them. I’m lucky to be enough of an old-timer that I usually can find the right person to ask, bug, or cajole.
Here’s the other thing you need to know about Google. We listen and respond to the feedback we hear. Google makes mistakes, just like anyone or any company does. That’s a given. The important thing is how you react to those mistakes. In an ideal world, you find out quickly when something has gone wrong. You correct it as soon as possible. And then you ask yourself “How can I try to prevent this issue from happening again?”–just like you’d do when you found a bug in a computer program. With any luck, future failures won’t happen unless several circumstances align against you.
Did a backhoe bring down your site by cutting a cable? Next time, you look to have redundant data centers and redundant network connectivity. If someone sends you a legal or DMCA request and you worry that the removal request impacts free speech, then you look for a better approach. You have to comply with the legal request and remove the requested pages, but maybe you revise your DMCA policy to give the other party a chance to counter-notify. Maybe you also add a DMCA notice at the bottom of the page that points to Chilling Effects so that users can get more background on the situation. We may think that a “Blog about this page” button on the toolbar is a good idea, but what do you do when someone cries foul because the button goes to Blogger? Well, one thing you can do is introduce the notion of custom toolbar buttons. Then anyone can add a button to their toolbar that posts to del.icio.us, TypePad, or they can make their own button for their favorite site.
So what does Google need to keep us on the right path?
I think what Google needs is more bloggers. I’m using a liberal definition of bloggers here; I mean people who monitor the blogosphere. In an ideal world, they’d also respond to feedback online. Some of the most dynamic teams at Google are the ones that listen to bloggers and respond. The webmaster console team has Vanessa Fox, Amanda Camp, and several others. Mihai Parparita and the entire Google Reader team listens for requests and responds to feedback in the blogosphere. Sometimes I’ve gone to answer a blogger’s question about Google Calendar only to see that Carl Sjogreen already arrived and answered it better than I could. There’s a VP of Engineering in ads who keeps a close eye on blogs, and I’d trust his intuition on any issue at Google.
My ideal would be if every Google project had someone watching the blogosphere for feedback. It could start as simply as a persistent search in Google News and Google Blogsearch for mentions of that product. That would help us spot if a particular project is causing headaches for someone. We should get the listening locked in first. As people get familiar with listening, they’ll soon be ready to comment, answer questions, and post a lot more.
Finally, Arrington’s mention of “Matt Cutts, the unofficial Google blogger” also set my spidey sense tingling. No single person should be Google’s unofficial blogger–that’s not scalable. I love working at Google, but at some point my wife is going to wake up and smell the coffee. She’ll say “Hey, we agreed we’d try this Google thing for four or five years, and then I’d get to pick what to do next. It’s been like eight years now! When do we move on to our next adventure?” Any Google engineer will tell you that a good way to scale something is to shard it. Rather than relying on one person, Google needs lots of unofficial bloggers.
So how do we keep the tipping point firmly in the “Google is Good” range?
- Each project at Google should monitor the blogosphere for issues. Reduce the disconnect to reduce the danger.
- Get more Googlers talking online. There will be some mistakes, but the conversations will be worth it.
A lot of this is already happening naturally at Google. I just want it to move faster.