5 Reasons Your New EHS Software Sucks.

2:42 PM 0 Comments

You convinced the executives that this was important. A key step in this day and age. You spent all that time, creative energy and money....and everyone hates the new EHS software…What happened?

1. You Fell For The Slick Salesman

He came into your office in his slick suit, promised you the sun, the moon and stars...and you believed him. The RFP was your gospel and that blinded you from seeing who you were truly dealing with. When you are in the RFP process, you want to hear no to some of your questions. That means you are dealing with an honest provider.

There are also certain intangibles that cannot be scored on a RFP, how you get on with the provider is a huge point that will impact every future step of the EHS software roll-out. No matter what the problem is, if you have a good relationship with your provider, you will be able to work through problems.

When we respond to a RFP, we often are missing a module or can score low in some sections, does this mean we are not the best provider for you? Definitely not. It means we are being honest and transparent with you. But if we don't have the module you are looking for and see commercial value in developing it or have gotten the request multiple times, then we'll work with you to build the best possible version of it!

2. Prior Planning & Preparation Prevents Piss Poor Performance

Were you clear in your own mind what you wanted from the new system? Did you know what was were the must-haves and what were the want-to-haves?

Did you truly map out the process and have realistic expectations at each step?

Or did you just become reactive in the process? Never stepping back to make sure you were on track with your plan and needs and eventually losing sight of what was actually important to you and the company and what was not?

3. Refused to Change

Change is good. But it doesn't always feel that way...Your old system was that comfortable pair of jeans you just couldn’t let go of. So when designing and creating the new one, you resisted anything that was even remotely different to the old system. The result? An EHS software system that doesn't do what it needs to do. You let your own bias and emotions derail the process.

4. Communication Breakdown

The weak system didn't come out of the blue, you could see you were on a path to it weeks or months ago, but what stopped you from being able to communicate this with your team and the provider?

Were you open enough to your team’s feedback? Were the comments from the relevant people? Or did the review sessions result in yet another feature brainstorming sessions and not feedback on what was being presented to you? Were you comfortable enough with the provider to have a real conversation about your concerns?

Wherever it happened, communication broke down at some point in the process.

5. Front line users weren’t part of your project team

You built the system with the wrong people in mind. Sure the dashboard looks great, but you didn't have the end user in mind or on the testing panel so it is a nightmare for them.

So, if the data gets input, it looks great, but you have created a nightmare for the people that will be interacting with the software the most so it might not ever get there...