A Change Management Culture – It’s a Corporate Thing
September 13, 2018The Benefits of Collaborating as a Team
November 15, 2018A Change Management Culture – It’s a Corporate Thing
September 13, 2018The Benefits of Collaborating as a Team
November 15, 2018Emerging technologies represent an opportunity when designing accident and health insurance products, processes, and platforms. Newer technologies like blockchain, heightened consumer expectations for anytime anywhere services, and the impact of social media translate to a growing challenge (and opportunity) for insurers. This especially holds true for complex products like accident and health (A&H) lines of business.
Approaching product design for A&H with a risk management perspective as the cornerstone enables insurers to define a product process as a series of discrete tasks. Rather than developing a software platform as a single application, tackling development as a series of small processes (i.e. microservices) allows insurers to address each process component with the most appropriate technologies.
This segmented approach enables the optimum process with capabilities such as process automation, rules-based functions, or advanced analytics – just to name a few. When the right technologies are applied to each discrete task, benefits can range from underwriting best practices, to risk avoidance from tariffs, regulatory and cyber, all while enabling a streamlined and personalized customer experience. But achieving these benefits requires a well thought out plan and quality execution.
Adopting a product framework
A cross-discipline team that includes subject matter experts representing marketing, underwriting, compliance, claims, operations, IT, etc. can collaborate to develop a product framework, an asset that will continue to facilitate new product innovation in the future. Key benefits for insurers adopting a framework approach is the resulting understanding of the commonality between products and geographies within a corporate structure, and the establishment of a common set of business processes, reporting and other functions. When commonality is identified and built into the framework infrastructure, rapid implementation of future products is enabled.
Product definition in a framework includes product settings, lifecycle schema, fields, coverages, benefits, validations, tax and tariff tables, premium calculations etc. Product and coverage templates can be created to define generic building blocks for quick products launches. Comprehensive product template(s) can be configured and used as building blocks to enable re-use and control consistency across products and regions. Here are some common framework elements (i.e. finite tasks) that can be addressed with microservices:
Compliance requirements
Underwriting controls
Monitoring processes (aggregates / Premium etc)
Common attributes for common entities (customers/insured’s, Brokers, Agents, users etc)
Common elements of a Product definition
Common elements of a Rating architecture
Referral processes
Document storage
Fees and taxes
Exchange rate processing
Billing requirements
Installment processing
Reporting
Given that Insurer systems are a common target for cyber-attacks, cybersecurity and consumer data privacy concerns represent a critical exposure that must be addressed in any product framework design.
Conclusion
As insurers look to emerging technologies, considering a microservices architecture versus the traditional monolithic architecture can enable the best use of new technologies, while extending the capabilities and lifespan of current technology investments. A microservices architecture coupled with a well-defined product framework in place will give insurers a strong arsenal to enable innovation, automation, and a competitive edge.