The Hamster In the Black Box

Every once in a while, we like to take a look back at the insurance industry’s technical literature. It reminded us that, at a time in the not-too-distant past, it was impossible to pick up anything — trade publications, marketing collateral from vendors, reports from the analyst community, et al. — without reading about Service Oriented Architecture (SOA). It seemed as if every developer and his dog were employing and touting SOA to the nth degree.

Our exploration also led us to some architectural relatives of SOA, which we’ve listed here, in part, with their respective definitions:

  • SOA. Service Oriented Architecture is a style of software design that provides services (discrete units of functionality, accessed remotely, acted on and updated independently) to various other components through a communication protocol over a network.
  • SAP. Service Application Programming. We’re going to leave this one alone.
  • SOAP. Service Oriented Application Programming is a clean approach to software development that combines architecture, application development, and protocol programming.
  • SOUP. Service Oriented Utility Programming describes the attempt to program utility into application development; that is, to create a solution for which there is an existing problem, rather than vice versa. Utility, in this context, is sometimes used synonymously with objective.
  • SOUP TO NUTS. Service Oriented Utility Programming Tapping Objectified Neurons Under Total Secrecy is an approach to enterprise programming that’s so covert not even the people who know about it know about it. SOUP TO NUTS was also known by the abbreviation TCP: The Complete Package.

We certainly found our discoveries amusing, if not terribly enlightening. But it caused us to think a little more deeply, particularly when we found a reference to black box in reference to SOA.

What Difference Does it Make?

The reference we found defined black box as:

a device, system or object which can be viewed in terms of its inputs and outputs (or transfer characteristics), without any knowledge of its internal workings. Its implementation is “opaque” (black).

That prompted us to wonder about what seems to us to be the relative unimportance to the user or the consumer of any specific technology and/or its nature. To be more specific, we wondered what our prospects might say if we asked this in one of our introductory conversations: “If our system comprised a hamster, running on a wheel in a black box — but it was easy to use, processed your business efficiently cost-effectively, and improved your results — would you care?”

We never ask that question, of course. And we’re quite proud of our technology, its facility, and its adaptability. But it did make us think about the possibility that all of us might be better off if we focused on objectives and outcomes, rather than on techniques and technicalities.

If we did that, decision-makers might be able to view all technology as just a hamster in a black box.

Changing the Subject Won’t Help

We firmly believe in the notion that anything is possible. If a person puts his mind to something, or if a group of people commits to working together to accomplish something previously unaccomplished, we’re among the first to believe it can be done. But believing anything is possible isn’t the same as believing everything is possible.

By the same token, common wisdom has it that the shortest route to any destination is a straight line. Along similar lines (no pun intended), the shortest route to the resolution of any question, particularly a business question, is a straight answer.

Presuming we’re all in agreement on those two points (why wouldn’t we be?), where does that leave us? We don’t know that we can answer for everyone. But we certainly can answer for ourselves.

Function Follows Facility

We make software to perform specific functions for a specific industry. Insurance. It does lots of things insurance software needs to do: It administers policies and claims. It manages billing. It provides business intelligence. It permits access through portals and mobile devices. And it features a WYSIWYG Design Studio that lets you design, configure, and manage the entire Finys Suite; to develop and deploy products, states, and lines of business; or to quickly change any of those things with or without our help, or any degree in between, depending on your needs and desires.

As much as it pains us to admit it, the Finys Suite doesn’t make coffee. It doesn’t play the violin. It won’t make us better looking.

The fact of the matter is, we don’t want the Suite do any of those things (with the possible exception of making us better looking). Our customers don’t need it to do those things. And we’ll never tell our customers or prospects the Suite will do everything they might want it to do. With their input and a legitimately demonstrable need, we can likely get the Suite to do anything they might like it to do. But we won’t make impractical promises, avoid their questions, or give circuitous answers to those questions.

Changing the subject, or avoiding it, won’t help anyone.

Let’s Be Careful Out There

At various points in the year, we like to review some of the things that have been forecasted to take place in or be important to the insurance industry. As a result of such a review, we came across a piece from PropertyCasualty360 called, “Four trends shaping insurance in 2019.” In brief, the four predicted trends were:

  1. Virtual claims adjusting
  2. Innovative use of mobile technology
  3. Better, more powerful data
  4. Blockchain will get bigger.

The first three are pretty much indisputable. Given the capabilities unleashed by the Internet (hello, IoE), the digitalization of darn-near everything, the ubiquitous advancement of mobile capabilities, the data generated by, accessible to, and running all those things, their inevitability couldn’t have been disputed. We do, however, wonder about #4.

The Jury’s Out

In November of last year, The Register published this — “Blockchain study finds 0.00% success rate and vendors don’t call back when asked for evidence” — which is the kind of thing that grabs our attention, especially when blockchain is being hailed more optimistically in other quarters. This was hard to ignore:

We found a proliferation of press releases, white papers, and persuasively written articles … However, we found no documentation or evidence of the results blockchain was purported to have achieved in these claims. We also did not find lessons learned or practical insights, as are available for other technologies in development.

We weren’t ready to give up on blockchain’s future in the insurance industry. In fact, some people, publications, and companies like SAP still hold out hope for it. But this one hurts a little more — “Blockchain Has Been Unblocked, Unchained And Broken” — especially when you get to this part:

Hackers have stolen nearly $2 billion worth of cryptocurrency since the beginning of 2017, mostly from exchanges, and that’s just what has been revealed publicly … One does wonder why Blockchain is so wonderful, then, if in practical use, its supposed greater security is so easily circumvented … To anyone with a shred of common sense, this is a fatal event.

Don’t Panic

We can’t be any more hasty in dismissing blockchain than some folks were in embracing it. As it is with any new technology, time is our best friend. So, let’s watch and wait. We can’t be certain of the outcome. But we can be certain we’ll learn something.

We’re not saying blockchain is dead or dying. All we’re saying is let’s be careful out there.

Business Objectives

Some businesses have lists of objectives that are better measured in yards, rather than word-counts. If there’s a way to prioritize and manage that many objectives, maybe that’s okay. We, on the other hand, tend to think there are two business objectives that (should) supersede all others:

  1. Acquire customers by developing the right product
  2. Retain those customers by delivering the right service(s).

While it may not seem like it, #1 is the easier of the two objectives. Creating a new product is like spring training: It’s a new season, a fresh start. Everything is fresh, green, hopeful, and eminently possible. With a win in front of us and the wind at our backs, all we imagine is succeeding. But that success precipitates the challenges manifest in #2.

The Day After

After developing the product and earning customers, the product has to be kept functionally relevant. Since we can’t eliminate change or anticipate the needs of every customer, #2 requires the constant accommodation of change and constant communication with customers. It takes a profound working knowledge of the industry (or industries) in which the product is expected to perform. It takes a combination of open-mindedness and decisiveness to know the product may, at some point, do this, but it will never do that (regardless of the precise definitions of this and that), as well as the courage to tell customers what the product will and won’t do — and why or why not.

Most important, perhaps, is the willingness and the determination to look ahead. No one can predict the future. But communicating with customers, listening to their needs, anticipating others, and demonstrating a commitment to remain professionally concerned and functionally relevant goes a long way to achieving two of the so-called soft objectives — the trust and confidence of your customers. Look at it this way: Functionality can always be added after the fact. But trust can never be back-filled.

First steps are crucial. Next steps are make-or-break.

It’s About Philosophy

Business objectives are great. Good intentions are terrific (and the stuff, of course, of which a particular road is paved). But over-promising and under-delivering is not a philosophy by which to earn long-term success.

That’s why we’re thinking about making a poster out of this strip:

 

 

 

The Decreasing Increase

Based on some of our recent reading, there seems to be a disparity of opinions as they pertain to the employment market:

  • Exhibit A: According to an article in PropertyCasualty360, “The number of insurance professionals aged 55 years and older … increased 74 percent [between 2006 and 2016].”
  • Exhibit B: According to a study published by Deloitte, “Few millennials are familiar with the insurance industry and only 10 percent are ‘very interested’ in choosing insurance as a career.”
  • Exhibit C: According to a study published by The Jacobson Group, “The mass talent shortage is here, and insurers must take action.”
  • Exhibit D: According to the LinkedIn Talent Blog, “The U.S. will be hit the hardest by the talent shortage, losing $435.69 billion in unrealized economic output—or 1.5% of the whole U.S. economy.”

But those alarmingly bleak perspectives don’t appear to be commonly held, let alone unanimous.

The Plot Thickens

In fact, according to a piece published by the United States Census Bureau in April of last year — “Older People Working Longer, Earning More” — the aging of the workforce and the rise of the millennials might not be so bad after all, particularly for the increasing numbers of  … uh … seasoned folks in said aging workforce.

Here’s a sampling of comparative statistics in monthly wages alone:

  • 17 percent for workers aged 14-24, a $245 increase from $1,431 to $1,676.
  • 20 percent for workers aged 25-34, a $600 increase from $3,049 to $3,649.
  • 32 percent for workers aged 35-44, a $1,254 increase from $3,939 to $5,193.
  • 32 percent for workers aged 45-54, a $1,390 increase from $4,363 to $5,753.
  • 41 percent for workers aged 55-64, a $1,629 increase from $3,928 to $5,557.
  • 80 percent for workers aged 65-99, a $1,816 increase from $2,276 to $4,092.

So, what is there to learn from this seemingly conflicting information? In fact, much.

Cutting to Reality

This much is indisputable: There are demographic shifts taking place in all industries. In the insurance industry (and others), those shifts mean younger people — who are more familiar and comfortable with technology — will enter, and older people — who have the requisite domain knowledge and experience — will exit. But it won’t happen all at once.

Because it won’t happen all at once, there will be knowledge-transfer between those demographic groups. Technology in general and good systems in particular will abet that knowledge transfer, ensuring that the application of technology serves and is informed by the institutionalization of material domain knowledge.

Despite the best efforts of some to convince us there’s a crisis-level shortage of capable insurance-industry personnel on the short-term horizon, it might be much ado about nothing.

As have generations before us, we’ll just do our best to keep up with time and change. Chances are we’ll be just fine.

Be Careful What We Wish For

We’re tech people. We’ve always thought we’re tech people so insurance people wouldn’t have to be tech people. And we’ve always felt like we were alone in that thinking. But the tide may be starting to turn.

The February edition of Best’s Review ran an article entitled, “Generation Next”, contending that the traditional focus of the insurance industry on technical competence (though not limited to technological competence) may be too narrow to carry it into the future. As Limore Zilberman, a consultant at the executive search firm, Russell Reynolds Associates, put it:

People were hired because of their technical prowess and because of their technical acumen and their technical contribution … [but]  the landscape of leadership is going to change. The expectations of leadership are going to change. Our technical talent is not necessarily well-poised to take on broader leadership capabilities.

That seems about right. To put it another way: With all the bigger fish insurers have to fry, technical talent may be a red herring.

Leaders Lead

In arguing that the insurance industry focus on specialists needs to broaden sufficiently to include generalists in leadership positions, Zilberman elaborates on the characteristics of the people she believes are better suited to fill the leadership roles of the future:

They’re agile, they’re adaptable, they’re quick learners, they’re good problem solvers, they’re forward-looking … Those types of people can be put at the helm to manage the lower ranks of the organization that might carry more of that technical expertise.

At risk of seeming to quibble with terminology, we take issue with Ms. Zilberman’s notion of managing the lower ranks. (We even find lower to be a tad condescending; although, we do take her point.) We take issue because leaders lead. Managers manage. And those two jobs, along with their respective responsibilities, are quite different.

But that difference in perspective on vocabulary notwithstanding, Ms. Zilberman and the article are correct. The insurance industry does need to think more broadly. And it does need to embrace well-rounded, critical-thinking generalists as its leaders.

If continue to favor leaders whose strength are technical (linear) thinking, as opposed to general (conceptual) thinking, we should be careful what we wish for.

Tight Lips Sink Ships

If you’re familiar with the expression, “Loose lips sink ships,” you understand why too much information (TMI) can be a bad thing. By the same token, too little information (TLI) can be equally bad. Case in point: The insurance industry seems conspicuously tight-lipped when it comes to information about implementations. As a result, there’s precious little data on failed or failing implementations, to say nothing of blown budgets, blown dates, and undue expectations as they apply specifically to the insurance industry.

Fortunately, there are two other things from which to derive meaningful and applicable perspectives: (1) A plethora of data on ERP implementations. (2) Extrapolation. Let’s have a look.

The Numbers Are In

Here are just three citations from the volumes of information about EPR implementations available on the Web: First, here just five of the failures listed by ERP Focus in “Ten ERP failure statistics that highlight the importance of getting it right first time round“:

  1. 60% of ERP projects fail.
  2. 57% of ERP systems take longer than expected.
  3. 54% of ERP systems exceed projected budget targets.
  4. 40% of ERP systems experience at-large operational disruption.
  5. 41% of enterprises fail to achieve more than half of the expected benefits.

Second, according to this infographic from Technology Evaluation Centers:

  • Nearly 50% of ERP implementations fail the first time around.
  • On average, 30% of ERP implementations take longer than estimated.
  • Most implementations cost three to four times what was budgeted.
  • About 65% of the time, budgets go over because the system needs modifications to improve usability. But companies realize this only after the implementation has started.

Finally (for now), Management Consulting Now reports ERP implementations:

  • Take longer than expected (61%)
  • Cost more than expected (74%)
  • Fail to deliver more than 50% of the expected benefits (52%)
  • Leave their respective organizations unhappy with the results (59%).

While all of those sources and studies might not agree, we can agree all of their statistics are dismal … and unnecessary.

Why Settle?

These numbers may be dire, but they need not be leading indicators, as we say in the biz. With some initiative, some diligence, some foresight, and a clearly articulated set of shared expectations, these statistics can be greatly improved. Oh, and let’s not forget clear and open communication between the parties involved.

Remember: Tight lips sink ships.

How About Insurance Insurance?

We saw this question the other day: How much chain could a blockchain block if a blockchain could block chain? It accompanied this cartoon:

We’re not trying to play similar word games with insurance. But we can’t help wondering: How much insurance could an insurance company write if an insurance company had insurance for its insurance company? We don’t mean liability insurance or BOP. We wonder if a sound, solid, fully functional insurance-processing suite constitutes something like insurance for your insurance company.

Think About It

When’s the last time you read an article about the number of insurance companies still working on green screens? Many insurers still do. When’s the last time you heard anyone admit to still using a dial-up modem? Some people still do. When’s the last time you heard anyone in any industry say anything other than their technologies were emerging, disruptive, or innovative? And why do you think that is?

It’s because talk is cheap. It’s also less expensive and more practical than chasing the rainbow and betting the ranch on emerging technologies.

And speaking of practical, is any industry more practical than insurance? Insurance has to be practical by definition. If you’re in the business of reserving the premiums of your policyholders against potential losses, what else could you be?

Yes. Like every other industry, insurance needs to keep its eye on emerging technologies. But its first look has to be at reliable ways in which to process its business, to serve its constituents, to ensure minimally risky ways in which to deliver its products and services. If insurers spent their time and attention pursuing emerging technologies, how much would be left with which to satisfy and retain their policyholders?

Everything you hear about leading insurance companies notwithstanding, for the really smart ones technology will emerge as it can.

Here’s a Real Bottom Line

We’d like to think we’re as idealistic as the next guys. But we might be just a bit more pragmatic. So, whether you’re betting the farm on insurtech, blockchain, or any other dream of the future — whether you’re chasing rhetorical rainbows like digital transformation or you need a fully functional insurance-processing suite right now — we’re here. We’re here now. And we’re ready, right now.

Feel free to think of us as your insurance insurance.

What a Difference a Year Makes

According to FinTech Global, this may not be the best time to be getting involved in insurtech. As of May, 2017, interest in insurtech was on the wane. Investments in insurtech were down more than 70 percent in the first quarter of 2017 vs. the first quarter of 2016. And here in North America, plumbing was looking like a better bet than insurtech:

The share of InsurTech deals in North America has been progressively decreasing since 2014, falling to only 37.7% in Q1 2017. The first quarter of the year also saw the overall amount invested in North American companies fall below the amount invested in their European peers for the first time, with $72.2m and $89.9m invested, respectively.

Yeah. It’s a terrible time to be in insurtech … unless it’s not.

Oops …

According to FinSMEs (“a fast-growing blog and represents a realiable [sic] and trusted source of information for would-be, young and established entrepreneurs, angel investors, venture capitalists, technologists, analysts, journalists and bloggers”), insurtech is going gangbusters. As of July, 2018, spending is up. Skepticism is down. And technology is about to … well … you might have to read this yourself:

Tech innovation never ceases to impress society and changes are happening at a very fast pace … Insurtech is still new to people, even though the insurance industry is one of the most common and popular financial businesses out there. Technology and insurance merged into one, creating this new concept … the disruptive innovation of Insurtech has numerous benefits that will positively influence the way people are dealing with their insurances … Technology will take over the insurance world by using complex systems for tracking cars, monitoring devices, helping customers to manage their insurance preferences and so on … Insurtech helps with leading businesses.

If you feel a little a little breathless after reading that, don’t worry. It’s not diminished lung capacity. After plowing through that, even a free diver would be looking for a little extra oxygen.

Just When You Thought It Was Safe …

If those conflicting points of view haven’t made the insurtech issue as clear as mud, there’s this, which says, in part:

Is there a bubble forming with all the billions being poured into InsurTech investments, and if so, is it likely to burst anytime soon? That was the question I found myself addressing repeatedly during the recent InsureTech Connect conference in Las Vegas. My response is a qualified “no.”

And this — “Can an InsurTech Startup Compete With Progressive and GEICO?” — which says, in part:

Unwary and inexperienced competitors may grow by unknowingly writing the risks that their competitors didn’t want … It defies all logic to suggest that there is a large segment of customers in a fragmented and highly competitive market that are being greatly overcharged simply because these companies refuse to offer them good rates to avoid cannibalization … In an industry where 96 is considered a best-in-class combined ratio, even a little bit of claims leakage can be quite hurtful.

Following the bouncing ball of insurtech opinions can be tiring, to say nothing of a source of eyestrain. Call us old fashioned, but we think if we keep one eye on keeping our customers happy and the other on the technology that keeps them happy, we’re good. So are our customers.

The Present is a Gift to the Future

Especially since technology is no stranger to the insurance industry, we’re not precisely sure what all the fuss is about. If an insurer calls and asks us if we’ll have insurtech next year, we’ll say we’ve had it since our founding in 2001. We may or may not say we’re more interested in the insurance lifecycle than we are in the insurtech hype-cycle. But if the insurer says it’s ready to write insurance, we’ll definitely say we’re ready to get that done right now.

In the meantime, if you need us, we’ll be over here, singing along with a very catchy tune from Dinah Washington.

What’s Required?

We once heard it said that most companies replace systems before they’ve used 80 percent of those systems’ capabilities or capacities. We were skeptical at first. But the more we thought about it, and the more we looked at systems, the more true it became. Here’s why:

Most companies decide to replace systems because of recurring functional frustrations: “Our system doesn’t do this.” “If only our system could do that.” And our favorite: “We need a new system to [fill in whatever you want that new system to do here].” In response to any of those statements, the logical questions are: Did you want your system to do this, that, or the other thing (whatever that thing is) when you bought it? Did you tell anybody?

Look Ahead

When Sylvester Stallone was shooting Rambo III in Thailand, cast and crew members were dropping like flies from the heat and dehydration. Stallone said, “By the time you realized you were thirsty, it was too late.” So it is with systems: By the time you realize you need something, it’s likely too late. That’s why foresight is so important in defining and articulating system requirements. Adding a little more nitromethane to the fuel mixture propelling a top-fuel dragster is much easier to do in the staging area than it is on the straightaway at 300-plus miles an hour.

To define and articulate requirements effectively, you have to:

  • Ensure transparency. If you try to define requirements in secret, away from the prying eyes of users, you’re building the system for yourself. Don’t be that limited or limiting.
  • Specify functional needs. The less you describe specifically what you need the system to do, the more you’re likely to fall for technical smoke and mirrors.
  • Avoid popularity contests. If you ask peripheral stakeholders — rather than users — what they want, they’ll tell you. If you don’t deliver those things, they’ll talk badly of you. If you do deliver those things, you’ll blow the timeline and the budget, the system won’t perform the way users needed it to, and they’ll talk badly of you.
  • Avoid pilots or prototypes. Either the vendor’s done it before or not. As the saying goes, almost only counts in horseshoes and hand grenades. If the vendor hasn’t done it before, you probably can’t afford to be a guinea pig.
  • Agree to a list of prioritized deliverables. Those deliverables should be a clear reflection of your requirements.

Act Like the Future is Now

We know it’s not possible to anticipate everything. But the more you anticipate, the more accurately you can define and articulate your requirements. And the more accurately you define and articulate your requirements, the more you’ll get out of your system and the longer it’ll continue to meet your functional expectations.

Rambo wouldn’t be able to beat the bad guys and dragsters wouldn’t win any races if they ran at 20 percent.