3 Aon eSolutions
share this guide
Risk Management Software Deployment Your Guidebook to Success
Remember how, in grade school report cards, our teachers evaluated us on how well we worked and played with others?
Well, this chapter may take you back as we address the best ways to ensure collaboration between a RMIS provider and the
client's project team.
All implementations will have a formal statement of work and generate project plans. But in bringing risk management software
uccessfully online, collaboration is certainly a most vital component.
Collaboration is something of an intangible factor, but you'll likely find the following points useful in continuously promoting cooperation:
Address risk and issue management within the project itself:
Just as risk management is a critical function in a business, it's also one of the
most important factors in a successful project implementation. The practice
of risk and issue management starts during project inception. Once you've
recorded the issue/risk, it's important to evaluate the potential impact and
apply mitigation strategies. That means discovering what needs to happen
to gain buy-in from end-users who are happy with the current system. Keep
revisiting the issue until you've eliminated that risk. Many project managers
also have risk logs, which are valuable tools for all team members to
reference frequently as a resource that enhances collaboration.
Plan communications to meet stakeholder needs:
How do we know exactly what should be communicated? A good place to
start is getting knowledge and understanding of exactly who your
stakeholders are and how and when it's most effective to communicate with
them. At project kickoffs, we on the Aon eSolutions Professional Services
team develop a formal communication plan. We base this plan on a detailed
stakeholder analysis that we perform together with the client team during
the planning phase. We make sure the plan reflects the level of detail
required by each shareholder or group.
t
