« Is Al Gore All Wet on Global Warming? | Main | Non-proprietary Systems: What a Concept! »

Insurers and Technology: Once Burned, Twice Shy

burn.jpg
When I look back on the long and, really, rather mundane history of technology in the insurance industry, one glaring fact leaps out at me—when it comes to upgrading technology or trying something new in the tech realm, we are far from enterprising or adventurous.

Industry consultants and observers (including me) have been critical of insurance companies in particular for being too conservative and all-too-willing to stick with what is admittedly a comfortably profitable status quo. We have watched impatiently while other industries successfully adopted new technologies, and we rolled our eyes and shook our heads when the insurance industry finally adopted those same technologies as much as five years later. Why can’t this industry be part of the leading edge, or even the bleeding edge of technology, we asked? We are just so un-cool.

It is important to realize, however, that insurers actually have some good reasons to be gun-shy about technology advances. First, there’s the old saw about not fixing what “ain’t broke.” In fact, as early adopters of mainframe technology, insurance companies saw a huge increase in productivity that they frankly expected to last them for years to come—and that promise has been realized, with so-called “legacy systems” still in place today (much to the dismay of pundits such as myself).

Meanwhile, while our business may fluctuate between robust and lean times, business overall is pretty darn good in the insurance industry. So, if the dollars are rolling in using what insurers have now, those insurers might understandably ask, “Why should I spend the time, money and manpower to upgrade what I have?” Sure, everyone wants to inflate the bottom line, but in many cases insurers have not seen the gains to be made as compelling.

Secondly, when carriers have judged that gains from technology would be compelling, they have jumped into the fray, only to emerge a bloody mess. Take the example of customer relationship management (CRM), which was touted by many (again, including yours truly) several years ago as a technology that would help insurers focus their sales and marketing efforts while at the same time maintaining positive relationships with their most profitable customers. CRM made a world of sense for business, and certainly for insurance, but it proved to be a miserable failure in our industry.

Of course, critics (NOT including yours truly), were quick to say that CRM was an impractical and useless bit of nonsense that had cost insurance companies millions of dollars and yielded virtually no benefit. Yet nothing could have been further from the truth. Sometimes it’s not the technology that is bad, but rather its implementation and use, or lack of use. Post-mortem studies on CRM projects pointed to a lack of backing from top management and a failure to change corporate cultures to adapt to the paradigm on which CRM depends.

Yes, CRM was a failure in insurance, but it was the humans who failed, not the technology. The unfortunate fallout from this episode, however, was that CRM was virtually pronounced dead in our industry, even though the industry actually needs a technology that can help it focus on the best customers and pay less attention to the tire-kickers. The more unfortunate fallout was that technology took the blame, and insurers were all the more reluctant to sink dollars into new tech initiatives.

It seems the latest potential victim of this fallout may be yet another highly useful technology, business process management (BPM). BPM is a platform that provides a systematic approach to improving business processes in order to make an organization more efficient and improve the bottom line. The potential benefits include cost reductions, flexibility for processes and rules modification, help with compliance and support of legacy systems.

Seems like a slam dunk for insurance, right? Yet research has shown that most insurers will pass on implementing BPM. While there are some industry-specific issues, and while there is certainly a considerable cost, one wonders if the main reasons insurers are saying no is that they just don’t want to get burned by technology again. Maybe they even have confidence in the technology, but lack faith in their human resources to interact profitably with that technology. Either way, it’s a sad state of affairs.

All of this mean that vendors of BPM and other technologies that could benefit the insurance industry need to step it up a notch in educating, selling and, yes, soothing the fears of a sensitive buying public. It also means being realistic about what products can and can’t do, about implementation times, cost of ownership, and many other factors. Mostly, however, it means that not only will vendors have to sell their products, they will also have to show potential customers how to change their organizations in order to effectively use those products.

It’s a daunting challenge, but one that must be met in order to ensure the success of technology initiatives in our industry.

So what's your take? How can vendors break through to reach insurance customers without scaring the life out of them?

This article appeared in the Spring 2007 issue of IASA's "Interpreter."

TrackBack

TrackBack URL for this entry:
http://www.insurancetechguru.com/cgi-bin/mt/mt-tb.cgi/32

Comments (1)

What did we learn?
•Much of industry has poor results from past investments in automated information systems because organizations fail to review and improve their solution acquisition process. The success or failure of their solution selection will eventually become clear. But it is very rare for an organization to study how an acquisition was conducted to look for lessons that can be applied to future procurements. Past mistakes get repeated.

How hard is solution?
•Lack of major project experience causes organizations to greatly overemphasize the ease with which future results can be accomplished
•They fail to consider all of the factors involved in a successful system roll-out. Network, hardware and software infrastructure issues as well as training and end-user support are often underestimated.

What is the real problem?
•Organizations implementing major new automated systems are not thorough enough in defining what is needed for these new systems
•Information technologist don’t understand the business drivers for the system and can’t distinguish between technical requirements and business issues.

What did we buy?
•Overselling of software readiness and capabilities by software suppliers is fueling incorrect expectations and timetables
•You’ve heard the story: Management loves the new departmental application, which was written using a desktop tool. Now they want to roll it out nationally and link it to an IBM DB2 mainframe database, but it can’t be done. Scalability has become one of the most critical issues for success.

What information do we need?
•Poorly constructed and antiquated software acquisition processes are being used to acquire the new software
•The IT department’s part-time buyers...untrained in software acquisition---are over matched by the full-time, trained sellers. Despite the cost , time and impact of software development and purchases on an organization, procurement skills haven’t gotten the attention they deserve.

What about the future?
•Insurance companies that are implementing new automated systems have not developed their change management skills to accomplish the vision and objectives they seek.
•They fail to plan for the continuous, accelerating change in technology. Five-year plans don’t work anymore. IS needs to plan at the outset for the possibility of changing standards, architectures and interfaces in addition to unforeseen breakthrough technologies.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About

This page contains a single entry from the blog posted on May 29, 2007 3:27 PM.

The previous post in this blog was Is Al Gore All Wet on Global Warming?.

The next post in this blog is Non-proprietary Systems: What a Concept!.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type 3.34