4 Highlights from the EHS Software Implementation Success Webinar
1) Always Budget for More Time
Regarding the implementation project timeline of the EHS system, always budget for more time. For example, if you think that your project will take six months, then it’s better to budget for nine months. You want to give yourself the possibility to have extra time to meet the requirements, satisfy stakeholders, and make sure that all issues are resolved. It’s better to underpromise and overdeliver. Giving yourself “a little bit of an extra runway” is helpful regarding the timeline.
2) Roll Out Modules Based on Functional Links
If you’re deploying an enterprise software composed of multiple modules addressing diverse business needs, roll out modules based on their relationships and how they work together. For example, deploying a module on incident management with a module on action plan management, rather than a module on GHG emissions management, makes more sense. Your software vendor and implementation partner can help establish the order of the roll-out of modules, based on functional links between them and the value that these links would bring, as well as your business needs. Doing this saves time by avoiding any re-work in latter phases, which might be necessary if this was not done at the beginning.
3) Select the Right Deployment Strategy for You
There are many ways to roll out software: 1) deploy everywhere at once, 2) have pilot sites first, 3) deploy division by division, 4) deploy first to areas with the greatest need, 5) deploy region by region, or 6) deploy in phases. After your implementation scope and timeline have been determined, you need to think about your deployment strategy and where to deploy the software solution first. The software provider and implementation partner may have suggestions, but ultimately you know your organizations, employees and company culture best, therefore you will know what will work for you.
4) Have an Effective Plan for Escalation
Bumps in the road and issues will always arise during a software implementation project, regardless of the software vendor or implementation partner that you selected. There must be an effective plan for escalation within your own organization, but also within the software vendor and implementation partner. Make sure that the vendor and partner have mechanisms in place to escalate issues in their respective organization, and that they communicate to you these mechanisms, in order to have your issues handled and resolved as quickly as possible.
We hope that you found this post about the webinar interesting. Click on the link below to view the recording of the full webinar and learn much more.