RISK MANAGEMENT SOFTWARE DEPLOYMENT: YOUR GUIDEBOOK TO SUCCESS 20
We often find it works well to understand the organization's current
workflows. We focus on what their pain points are today, and then look
at what's not working.
Once we have a good understanding of the workflows, we discuss where
they see the RMIS in the next two years, three years — even five years.
Are there other modules or capabilities they'll need, or other critical data
they'd like to capture?
We realize that these are longer term, even visionary questions,
particularly for a first-time RMIS client. But even having a basic wish list
of how the RMIS could support them gives us a jump-start on deploying
the new system.
UNDERSTANDING WORKFLOWS
This step can be as simple as a collaborative brainstorming session.
For example, we can pose the scenario: "We're tracking these five
claim types in the system today. But we also have claims for areas X, Y
and Z. How can we make sure the RMIS can accommodate this change?
Can we build a system now that will track those additional claim types
effectively, as well?"
The answer doesn't have to be definite, as in, "These are the exact
reports we'll need," or, "This is the exact data we're going to capture."
It's more a case of, "This is our policy information now, and in the future
it would help to understand how our claims are impacting our policies
and insurers." This kind of information helps ensure that we are aware of
future needs and are making decisions today that will allow the client to
grow into this setup.
THE POWER OF BRAINSTORMING
