Can Google Save Us From Bad Interfaces?

Craig Weber
Insurance Experts' Forum, April 27, 2010

As often happens, a recent conversation with an insurance CIO produced an “ah ha!” moment for me. Why is it that we, as an industry, are so slow to recognize technology user behaviors that have become commonplace? If everybody Googles, why don’t insurance applications?

The topic of discussion was the difficulties that technology execs face in supporting the polarized needs of users. For example, some agents still prefer to take new applications via their trusty yellow legal pads and ballpoint pens, while others take a laptop-centric view of the world and prefer electronic applications. Those two streams may converge at some point (probably on the desk of a field office or underwriting assistant), but there are critical implications for processes and technology.

Even within the subset of agents that is technologically savvy, there are differences. For example, most agents are comfortable generating an illustration using traditional desktop software, which presents a series of data entry fields, and spits out compliant presentation materials in about 10 minutes. But what about the agent who is a Google power user, who thinks in terms of a command-line interface to do things more quickly and more directly? Could a Google-based comparative illustration application work?

On a goof, I tried entering the following in Google: “male 44 year old non-smoker 20 year YRT.” What the heck, I thought, go with the "I’m Feeling Lucky" button. (For the uninitiated, this slightly irreverent option in Google takes you directly to the top search hit based on the other terms entered, rather than presenting you with a list of all hits.)

"I’m Feeling Lucky" produced no result. Shocking! Apparently, there are no carriers leveraging a pure online illustration package with a Google interface. A regular Google search wasn’t much better—it turned up lots of articles on mortality and insurance, but not what my hypothetical agent was looking for.

The lesson for me is that if the insurance industry truly designed technology to meet user needs and expectations, this application or something similar would exist. The technology is proven, and commercially available.

Is insurance more complex than searching for a JPG of a common house wren? No question. Are there difficult issues with designing a business model around this approach? Absolutely! But technology exists to solve problems, and sometimes to enable radical shifts in how businesses and customers interact. We could avoid a lot of pain and effort by leveraging existing user behaviors rather than forcing users down the paths that are most convenient for us.

This blog has been reprinted with permission from Celent. Craig Weber is SVP of Celent's insurance group, and can be reached at cweber@celent.com.

Readers are encouraged to respond to Craig using the “Add Your Comments” box below.

The opinions posted in this blog do not necessarily reflect those of Insurance Networking News or SourceMedia.

Comments (0)

Be the first to comment on this post using the section below.

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

The Other Auto Insurance Telematics Shoe Drops

Progressive's decision to charge Snapshot drivers more if their driving data indicates higher risk has started the industry down a road of data-driven adverse selection.

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.

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.

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.

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.