News & Commentary

12:34 PM
Eugene Lee, Guidewire
Eugene Lee, Guidewire
Commentary
50%
50%

When Designing Insurance Apps, Consider the Intent

Insurance apps, intended to give insurers easier access to data, haven't made enough of an impact to be deemed particularly useful. Why?

Applications, which have saturated the global market in the hundreds of thousands, arguably have a singular focus: to simplify users' lives. So when the "appification" trend made its way to the insurance industry, hopes were high for streamlined processes. Consumer insurance apps for policy management are now fairly common, and First Notice of Loss apps are used regularly to ensure agents receive timely and accurate claim loss data.

But similar to some of the hundreds of thousands of apps created for the global market at large, still other insurance apps, intended for insurers to have easier access to data, haven't made enough of an impact to be deemed particularly useful. Why? Because these applications are designed without intent: Data is dumped on the user, and is out of context and unfocused. As a result, insurers are overwhelmed with information and unable to make informed decisions on policy quotes, support calls, claims adjustments and other such transactions.

Just like in any other industry, big data in the insurance industry has made available tomes of internal and external data. While having more information to work with can be a boon, data delivered without context is counterproductive. Indeed, too often insurance apps were designed with little thought given to what the user actually wants to do with the gathered data other than present more data in a more colorful, graphical mobile way.

But when an app is designed with intent, the data delivered is put into context and becomes meaningful -- it now has a purpose. Designing an app with intent must begin by identifying and understanding a specific need or use-case, and building the application around that. Doing this is actually very difficult: It means the scope of what an app can do must be reined in. A laserlike focus must always be kept; otherwise, the app is at risk of being useless.

As well as creating a purpose for an app, to have context it must also have meaningful content. Therefore, appropriate data must be collected, filtered, merged, prioritized and indexed – in other words the data must be curated; a process to metamorphose data into context rich information.

Information is now in context and consumable, and delivered in a way that maps directly back to a specific task. Insurers are presented with actionable intelligence that translates to more efficient and streamlined processes, and better overall decision-making. For example, a comparative application will provide industry context around an insurer's performance measures, delivering peer insurer benchmarks. A forensics application for hail facilitates communications with policyholders and enables the insurer to efficiently deploy resources to areas that have seen hail. This type of application can also curb fraud by validating the severity of hail for claims and policies. Yet another example is an application that evaluates the present and future impact of external events and internal decisions such as business process changes, product innovations or capital investments.

Indeed, the appification of the insurance industry has far-reaching implications, not only in helping streamline internal processes to better serve clients, but also in helping to limit fraud, assist in risk management and usages we haven't yet imagined. But in order to achieve these benefits, intent in design and a laser focus on serving a singular need with each application must be considered. Only then will insurance applications deliver consumable, usable data, and continue to live up to their potential.

About the author: Eugene Lee is senior director of new initiatives at Guidewire. 

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Janice, I think I've got a message from the code father!
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.