Can Google Buzz Teach Insurers a Few Lessons About Social Networking?

Craig Beattie
Insurance Experts' Forum, February 26, 2010

Google tends to get a lot of press simply because it’s Google, although it’s fair to say it’s got a few things wrong with some of it’s products—anyone remember Orkut, or all the hype around Google Wave? One thing is certain Google have got a lot right about its launch of Google Buzz. This may be particularly interesting as some insurers and financial advice Web sites move to create their own social networks. Let’s examine first what Google got right, and then what we can learn from where they went wrong.

Firstly, and I think this is key, Google leveraged an existing network. Google Buzz is built on Google Mail. This immediately gives a population of customers. In addition, this product already has many of the customer’s frequently contacted friends. This means there’s little set up involved and the network has been swiftly established.

Secondly, Buzz leverages existing assets and relationships. It’s linked to Flickr, YouTube, Google Reader, Google Maps and others. This means that customers can continue using existing and familiar tools and gain extra value from Buzz.

Thirdly, Buzz came out with a programming interface to allow third-parties to start integrating. It also leveraged existing networks, and APIs allow it integrate with the customers other applications very quickly.

Lastly, Google has been very quick to respond not just with words but meaningful change to the product, even though it is only a week old at the time of writing. In an interview, Google have described having a War Room set up with developers and product owners listening to customers in real time, and making key decisions about whether to and how to change the product.

However, Google got two things wrong.

The very public and ill-thought-through impact on privacy has been the key concern. Customers could easily and accidently disclose information about who they frequently e-mailed and contacted—information previously private. This is of concern to cheating partners and political activists alike. Google already has done much to address this concern, and what was an own-goal is now being applauded as a swift response by advocates. We’ve learned today that the privacy issue has sparked some class-action lawsuits in the U.S.

The second thing that could have gone better is the programming interface, which is currently read-only. I would expect a further increase in adoption once tool authors can create updates to Buzz directly, which for me constitutes a huge opportunity missed.

What does this mean in financial services? Some simple guidelines:

1. Leverage existing assets—both information you have and public information. Google asked their customers to volunteer their Twitter ID. This information provides Google with an already public list of their customer’s friends. Unless you have a key unique selling point, consider leveraging existing networks rather than building your own—for example Twitter or Facebook.

2. Link your network to support the free public feeds from Flickr, Twitter, etc.

3. There are successful social networks that operate without a programming interface. Very few companies have offered open programming interfaces with insurance or financial data— is one such example offering read-only transaction data.

In other domains, allowing third-party developers and tools vendors to build applications for a Web site has sped up adoption. Limiting an API to posting updates, managing communication and friends should have the same effect.

4. On launch, set up a war room. Most of the feedback will arrive in the applications infancy, and its survival depends on identifying the issues and opportunities, prioritising these and visibly acting on them.

5. Finally, get the security and privacy right. The two go hand-in-hand. Getting it a bit wrong and fixing it quickly as Google have can earn you forgiveness, but customers will likely expect more from financial services organizations.

Craig Beattie is an analyst in Celent's insurance practice, and can be reached at

The opinions of bloggers on do not necessarily reflect those of Insurance Networking News.

Comments (1)

While it is a well thought analysis, may be some more thoughts on what lessons do Insurers have from this would be more thought provoking. For me, it sounded pretty generic - nothing specific for Insurance companies.


Posted by: nramanathan | February 27, 2010 5:07 AM

Report this Comment

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

Core Transformation – Configuring in the Rain

The whole point of core transformation is that changes at the micro level can be used as a stimulus for changes at the macro level.

6 Ways to Develop a Productive IT-Business Dialog

Relationship management 101 for keeping IT and business on the same page.

Agile and Continuous Delivery in a Regulated Environment

Just because a development team is doing continuous delivery or packaging releases into two-week sprints doesn’t mean that code is being moved to production.

Unified Digital Strategy: Succeeding in the Digital Revolution

A unified digital strategy recognizes that all business strategies and technologies touch the customer in some way and that a one-size-fits-all channel model is obsolete.

Dealing with the COBOL Brain Drain

Documentation on aging systems often is akin to tribal knowledge, and the potential for things to go bump in the night increases as these environments face generational transition.

Enterprise Insight at Insurers’ Fingertips

Insurers are caught in a complexity predicament because of frequent mergers and acquisitions, expanded product and service offerings and more stringent regulations.