Lessons from Metcash's Massive Microsoft D365 ERP Implementation Failure

What happens when an organization spends 2 extra years and $200M more than expected on their ERP implementation?
That’s what I will be discussing today.
#erpimplementation #dynamics365 #d365 #digitaltransformation
ORDER MY NEW BOOK: The Final Countdown: a.co/d/50cqrCB
CONTACT MY TEAM & I: www.thirdstage-consulting.com...
FOR SPONSORSHIP OPPORTUNITIES: [e-mail]
🔗 Explore Our Latest Resources:
2024 Digital Enterprise Operations Report: resource.thirdstage-consultin...
TSC Resource Center: www.thirdstage-consulting.com...
Software Buyer's Guide: resource.thirdstage-consultin...
Supply Chain Management Playbook: thirdstage-consulting.com/rep...
Digital Strategy Framework: resource.thirdstage-consultin...
Guide to Organizational Change Management: resource.thirdstage-consultin...
20 Lessons from 1,000 Digital Transformations: www.thirdstage-consulting.com...
📱 Connect With Me:
LinkedIn: / erickimberling
Instagram: / erickimberling
TikTok: / erickimberling0
X: / erickimberling
📩 Got Questions?
Contact me to brainstorm ideas for your digital transformation: [e-mail]

[@atimnyanzi6859]

This is another great lecture from you Eric. Thanks for sharing.

[@grahamr56]

So Metcash wanted to "paper over the cracks" with a new ERP system, in effect? I've seen this happen in large organisations where the unspoken objective for new ERP systems was about connecting disparate business operations with broken processes or legacy systems. And these ERP "do-overs" can get incredibly political too - you're either a strong supporter of the initiative (and, by extension, the proponents of that initiative) or you're heading for the door. As the vendor of such a "legacy" system we were once put on the spot by demands from the CIO of a large bank to publicly state our support for their intended SAP project. Naturally we were reluctant to do so at the cost of the reputation of our system, which led to a certain tension. Ironically, many years later our G/L system was still firmly in place, as the CFO wouldn't allow it to be messed with while the SAP project stumbled on.
As for being "sold a dream", I guess Metcash was hearing what Metcash wanted to hear. If it had worked out well, those people would have been saying they "saw a vision of success".

[@jann2759]

This happens a lot with the reporting structures not in place and the senior management team sitting far away from the consultants perhaps penny wise and pound foolish particularly when this happens in large-scale ERP implementation programs.

[@rajivsharaf99]

One of the key factor for project success is who drives project ? If SI drives project, its bound to have many unpleasant surprises. If process is standardized one BU, extension to another BU is not simple if another BU operates under different region, different vendors/ stakeholders.

[@franconasello6160]

My idol does it again

[@patrickrodies6111]

How many organisations are going through the same failure with ERP implementations? Maersk did it with the first implementation of SAP, 1 Billion in the drain. The second is a not a success but they managed to limit the impact of the failure by limiting the scope of the implementation.