RISK MANAGEMENT SOFTWARE DEPLOYMENT: YOUR GUIDEBOOK TO SUCCESS 33
We urge clients to keep to their project path but stay open to
suggestions. You never know what issues may arise that seemed
minor in early planning but slowly emerge as important to the
client's satisfaction.
An example: We have had clients who were moving to an RMIS from an
environment of categorizing everything in spreadsheets. Their entire
user base had been using spreadsheets and sending them in to the
client's risk management team. It was a huge change for them to go
from spreadsheet data entry to system data entry.
One of the reasons the client purchased the RMIS was to streamline
the collection aspect and make it easy for reporting. Their team came into
the project with a preconception that they wanted it to work like X, Y and Z.
We came back to them and said:
"We can do that; however, here is why you might want to look at
a slightly different approach."
This is where it pays to be flexible. If the client is open to suggestions
of improving their process rather than just recreating it, they'll get
a much better system.
Neither the RMIS provider nor the client goes into an implementation
thinking that change is a given. But experience shows us that it's best to
remain open. The best implementation — no, let's say the "highest value"
implementation — is one where people keep their minds open.
REMAIN OPEN TO SUGGESTIONS
