(Warning: I'm going to talk about enterprise stuff. AKA, internal IT efforts. This topic can be really honk-honk-snore for some folks. I wouldn't blame you if clicked Back now. Can I interest you in an iPad article?)
Google announced Google Buzz on Tuesday. As with many Google social tools, many folks I've spoken to are impressed with Buzz's tech, but not its experience. ( Google just isn't the greatest at managing social relationships and contacts in any of its apps. Even adding somebody as a friend in Google chat is strangely awkward and unnecessarily obtuse...)
That said... I think Google Buzz has potential to make an impact in a less web-centric place: the enterprise... as an internal organizational tool. The playing field there is slightly easier to pick off. Expectations and habits are less well-worn, and Google would have some big advantages. Requirements in the enterprise are different. A primary one is the ability to integrate with corporate directory services, something Google Apps already does relatively well. If Google Buzz gets integrated into Google Apps, as Google has announced it will, the directory hurdle is easily cleared. Good for Google, and good for organizations using Google Apps who are otherwise evaluating, negotiating, and integrating another 3rd party microblogging tools like Yammer into their environment.
But in order to really clinch the enterprise deal, Buzz needs to be more decoupled from Gmail. At least at the presentation layer. For one thing... lots of organizations do NOT integrate the entire Google Apps stack. Many use Google Docs without using Gmail. By keeping unrelated tools tied to Gmail, Google accidentally locks out a lot of functionality. (They've done this with the Groups feature of Apps, for example. It's really hobbled if you don't use Gmail, despite its application to non-mail behaviors.) Many organizations looking for an activity stream-like tool like Buzz, are evaluating it as its own service, independent of email. Even when an organization does use Gmail, Buzz really needs to feel a la carte. The Buzz API will ideally create a rich ecosystem of a la carte Buzz tools, but it'd be cool if Google got this at a fundamental level.
Google long ago announced Google Wave's eventual availability for Google Apps customers, something that has yet to happen. Given the giant lateral leap Google Wave represents, I can't blame the slow roll out. But much of the experience Google Buzz represents, is stuff we've already internalized and do in our daily life. We just don't necessarily have it in large organizations yet. Google can be involved in this internal-org shift in a big way if it doesn't insist on indulging in its wacky idiosyncrasies.