Groundhog ERP Day!
ERP Project happening Again, and again, and again....
A Pennsylvania Dutch superstition - if a groundhog emerging from its burrow on this day sees its shadow due to clear weather, it will retreat to its den and winter will persist for six more weeks; but if it does not see its shadow because of cloudiness, spring will arrive early.
“What? Are we going down that path again?” Mr. Badger, the Chief Operations Officer, asked in amusement. “Haven’t we tried this same project every 2 years and always stop right after we do a bunch of ‘waste of time’ demos?” The room was a bit chilly since it was only the beginning of February. The topic was replacing the ERP system. The current system had been implemented about 15 years ago and lacked zillions of features, so it had become customized beyond the ability to upgrade. That is why no new system they had demo’d seemed able to replace the current old bones.
But the last management report said that the old, outdated ERP system was a critical flaw in the company and should be a top priority to address. Data, data, data, the consultants kept repeating. So, there they were, today, exactly the same position as yesterday. The sun was shining, and they’d be looking at their shadows, one more time! Every six weeks, the company held an executive meeting where each of the execs were to give a report on results to date and to bring up big initiatives for the coming year. This time the meeting was being held at a retreat in Punxsutawney, Pennsylvania.
Most of the executive team was gloomy. Rather than an upbeat discussion of great projects to undertake, each of the executives was feeling defeated. Chief Sales Officer Doug Daks was spending his weekends building his sales team reports in Excel, and although excited about the growing sales, he was down in the tooth about the amount of burdensome work-arounds to get reports. The Chief Marketing Officer needed more and faster data on sales for each SKU associated to each marketing campaign by sales channel. And the CEO, Chris Candlemas, was exhausted because she had been up all night worrying about the meeting she was to have with investors next week.
The new CFO, Phil Groundhog, was a bit nervous. Although he’d only been with the company 6 weeks, he had experience from a similarly sized manufacturing company and he wanted to talk about undertaking an important project to change-up the ERP system. He was afraid the CEO would balk at the hefty price tag. To calm himself before his presentation, Phil went out onto the patio outside the conference room for some air. Looking up, he saw the sky starting to cloud over, blocking the sun.
Not seeing his shadow, Phil smiled from ear to ear. This was a sign. Phil turned to scurry back into the room. His presentation was going to touch on the top 3 points the company needed to consider now. His project would get green-lit today, and he would not have to wait another six weeks! Phil started his presentation by outlining what he knew about their systems’ Current State. From there, he pointed out the areas that were holding the company back. Finally, he gave a picture of the Future State. He provided a clear vision of the steps to be taken to modernize the operations of the company.
1. Current State. The outline showed the major departments, the software in place, and the missed connections between departments.
2. Areas that are holding the company back: There were more ‘glitches’ than we have space to present, but a few examples included: