The system went live. The project was closed. And six months later, half the organisation was back on Excel.
This is not an unusual story. After more than 20 years of implementing ERP solutions in the maritime sector, we have seen this pattern more times than we can count. And in almost every case, the cause wasn't the software.
The implementation succeeded. The change didn't.
A successful go-live is not the same as a successful implementation. The moment a system goes live, the real work begins. People who have worked a certain way for ten years don't change overnight. Workarounds appear, small at first, then structural. The old spreadsheet stays 'just temporarily.' Two years later it's still there, running parallel to the system that was supposed to replace it.
This is the most common reason ERP implementations underdeliver. Not missing functionality. Not technical failure. But the gap between a system that is live and a system that is actually used.
Three patterns we see consistently
The first is the parallel system. The new ERP goes live, but the old way of working doesn't disappear. Teams use the new system for what they're required to, and the familiar tools for everything else. The result is two versions of reality and nobody is quite sure which one to trust.
The second is incomplete process design. Many implementations focus on replicating existing processes in a new system rather than redesigning them. The inefficiencies move over intact. The system is new, but the underlying problems remain. Three months after go-live, the same questions surface: why is the data still incomplete, why does reconciliation still take this long, why are there still errors in the invoices.
The third is adoption without ownership. When a new system is introduced without clear internal ownership, someone who is responsible for how it is used, not just that it is used, it slowly drifts. Teams develop their own interpretations. Configurations that were carefully designed get quietly bypassed. Over time the system stops reflecting how the organisation actually works.
What the organisations that get it right do differently
They treat go-live as the beginning, not the end. They remove the alternative, no parallel spreadsheets, no workarounds that are allowed to persist. They design processes before they configure systems. And they appoint someone internally who owns the outcome, not just the project.
None of this is complicated in theory. In practice, it requires discipline, clear agreements and a partner who understands that the real work happens after the go-live, not before.
At Ultimate Maritime Logistics, we have spent over 20 years learning what makes implementations in the maritime sector actually stick. Not just technically, but operationally. The difference between a system that is used and a system that transforms how an organisation works is rarely about the technology.
Curious what this looks for your organization? Get in touch for a no-obligation introdcution.
