Blog

Form Following Function: The Hurricane Watcher Model of Insurance Core Applications

Ellen Carney
Insurance Experts' Forum, November 12, 2009

I grew up in a small town in New Hampshire. We were Massachusetts transplants, and my father viewed the family’s move north as his opportunity to transform from city guy to gentleman farmer. So, we went native. We got animals—horses, cattle and turkeys—along with the requisite farm equipment. And having all these farm resources meant that we, or actually my mother, had to go to the local seed and feed store to buy the stuff that kept the Carney farm operating—grain, tractor parts and pitchforks—all of which was no doubt pretty foreign to a woman who grew up in Cambridge, Massachusetts. Even though it was nearly 40 years ago, I won’t forget the first visit to the feed store.

“Hap,” the feed storeowner, was one of those craggy New Hampshire characters who, while spare in the number of words spoken, never failed to get the point across. Somewhat ironically, he had a son who was an aspiring artist, and in the middle of a field out back of the feed business, there was a wooden structure. It wasn’t a building or a sign; in fact, it seemed to have no purpose at all. 

When my mother asked just what that thing in the field was, Hap was quick to tell her that it was a “hurricane watcher” ... and went on to explain that if she saw it fall over, she’d probably be in the middle of a hurricane. Hap knew that this indulgence to his artist son not only served no purpose, but was actually a nuisance when it was time mow around it. With a little sardonic wit, he was able to position at least a little value for it as a disaster indicator.

So what does this hurricane watcher have to do with insurance? Recently, I’ve been talking to variety of roles both inside and outside carrier walls to learn about how carrier application architectures impact how people get their job done. What’s become clear in these conversations is that while the legacy architecture can make things easier for IT to control and manage, that same architecture certainly might not do much to make it easy for people who had to use the systems under it. Some of these architectures were dictating how people worked in the business, meaning it was the employees who had to adapt to accommodate the carrier architecture, rather than the other way around.

Like Hap’s artsy offspring, a lot of insurance applications were built 10, 20 or 30 years ago by the craftspeople in insurance IT shops. The applications, like the wooden ornament in the field, produced a lot of pride in these software artisans, and they probably marveled over the beauty of the code. But the application utility—the ability to satisfy the wants and needs of the business, employees, agents and policyholders—clearly diminished over time or existed as something that primarily served the needs of ITs. 

As a result, contact center staffs spend a lot of time answering questions from policyholders and agents about bills because the systems couldn’t adapt to the needs of the business. Finance couldn’t accurately measure the cost to issue a new policy or produce a bill, and marketing was limited not by regulators, but by their own internal systems even for enhancements to existing products, never mind new kinds of products or ways to help agents sell more policies. 

It’s enticing to think about the creation process because we want to protect the application developers who we depend on to maintain our systems; or, as Ara Trembly recently posted, because internally developed software creates a competitive advantage.  But as I’ve heard from the field, it’s also easy to create systems that are  “hurricane watchers.” 

Ellen Carney is a senior analyst with Forrester Research. She focuses on how the financial services industry researches, procures and deploys business technology, and is responsible for developing the global forecasts for IT budget and spending forecasts for insurance and banking. Follow her on Twitter at: http://twitter.com/ellenmcarney

Readers are encouraged to respond to Ellen using the “Add Your Comments” box below. She also can be reached at ecarney@forrester.com.

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

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

Global Supply Chain, Local Problem

As a technology provider, your clientís ability to deliver products and services to their customers, when and where they need them, is at the heart of their business success.

Legacy Systems Are Increasingly a Competitive Handicap

Legacy systems, while reliable, increasingly hold insurers back, a new study finds

From Her to Watson, and What’s Next?

Imagine a learning system that can replace the performance of your best employee to provide the same level of support across the organization.

Five Reasons to Software-Define Your Operations

It may be possible to provision key services with the click of a mouse, but benefits go well beyond that.

3 Policy Admin Conversion Considerations

Insurers would be wise to learn these lessons before formulating a strategy to convert policies to a new policy administration system.

Boyle’s 4th Law - Response Time Matters!

Why many companies donít do a good job of measuring the thing that clients value the most.