Making “Remote” Risk and Insurance Technology Implementations Work

Over recent months, as a result of the COVID-19 pandemic, an estimated 50% of U.S.-based workers have been participants in a grand remote-work experiment. As Katherine Guyot and Isabel V. Sawhill point out in an article published by Brookings, Telecommuting will likely continue long after the pandemic, while the rapid switch to remote work has been driven by necessity, “COVID-19 may permanently change the way many of us work.”

Understandably, one of the most common questions we at Origami Risk have been answering during this period is related to what this change has meant—and what it might mean—for a complex, weeks-long project such as the implementation of a Risk Management Information System (RMIS), GRC technology, or insurance core system.

While it’s true that, in some instances, gathering around a conference table or sitting side-by-side at a desk to iron out specific details may be preferable, our approach to the design, delivery, and support of risk and insurance technology makes Origami Risk ideal for remote implementation and support. Platform adaptability and usability, a proven approach to implementation, and the experience of the Origami service team means that you will not be part of an experiment. In fact, a majority of our implementation work is, as it has always been, performed remotely.

Technology That Makes Remote Implementation and Support Possible

Origami Risk implementations move quickly and can be performed remotely because our technology doesn’t require a large-scale project or the updating of roadmaps when you see different and better ways of doing things. This is possible because, as a cloud-based, SaaS solution, Origami Risk has been built to meet the following criteria:

  • A scalable platform that is easy to maintain and to which functionality can be added within the base code
  • A platform that interfaces well with the third-party systems on which clients depend
  • A platform that empowers clients to take control if they feel comfortable doing so

In the Origami Risk system, making changes to fields, labels, forms, data mappings, batch import or export processes, point-in-time reports, loss triangles, notifications, alerts and security permissions can all be done through the front end without the need for custom coding. During implementation—and as part of ongoing support—this means that changes are often accommodated during the call in which they are outlined. Additionally, the delivery of system updates every 6-8 weeks mean you don’t wait months to use new functionality.

A Proven Process for Engaging Users and Delivering the Right Solutions

We understand that implementing risk and insurance technology is a complex undertaking, that one size does not fit all, and that constant communication is instrumental in getting it right the first time. For this reason, we use a process that involves not only weekly meetings, but continual communication in the form of emails, phone calls, video conferencing, and—when possible—face-to-face conversations.

Starting week one, there are deliverables for you to review and follow-up for the week ahead. Results and feedback are gathered and distributed in advance of regular meetings that continue throughout the entire implementation. As illustrated in a case study that highlights details of the New Mexico Counties (NMC) RMIS implementation, this allows for pivoting to a more optimal solution, should one arise. It also acts as an additional form of training that prepares users for go-live well before the arrival of the go-live date.

A Collaborative Approach to Implementation and Support, Guided By Experts

The Origami Risk service team is made up of the most experienced professionals in the industry. Although their resumes and backgrounds are unique, members of our team have the following trait in common: each is a problem solver looking for the “why,” not just the “what.” Instead of recreating the old, Origami views implementations as opportunities to collaborate with our clients to make improvements where possible. Part of this approach is taking an in-depth look at data, reports, and workflows in an effort to ensure each supports your business objectives. This can only be accomplished with a team that combines an understanding of insurance and technology experience.

Like system implementations, the Origami Risk approach to ongoing service is different by design. Rather than handing you and your system off to a random member of another support team—one not involved in the implementation—or pushing you toward a call center, your implementation team continues to work with you. There is no handoff; the team that implements your RMIS or insurance core system is the team that supports you on a go-forward basis. Even when face-to-face interaction isn’t a possibility, you’ll still be working with people who understand your needs.

Learn More About Origami Risk

A flexible platform, an approach to implementation that’s different by design, and software expertise combined with risk and insurance knowledge all combine to make Origami Risk insurance and risk technology that can be implemented and supported remotely. Rather than an experiment, it’s an approach that’s been proven to work. If you would like to learn more about our approach to system implementation and discuss how Origami Risk might help you drive meaningful results, contact us.