Organizations often enter an ERP program with the belief that the new system will finally bring order to the chaos – standardize processes, eliminate inefficiencies, and create a single source of truth. It’s an understandable expectation. ERP platforms are marketed as engines of discipline and structure. But the reality is far less forgiving:
“ERP systems do not fix broken processes. They simply make those problems more visible, more rigid, and far more expensive to correct.“
Most ERP failures can be traced back to a single root cause: the organization never took the time to stabilize and standardize its workflows before the implementation began.
Instead of building a strong operational foundation, teams rush into system design with inconsistent processes, unclear roles, and data that has been shaped by years of workarounds. The result? Delays, rework, customization, and a system that reflects the very inefficiencies it was meant to eliminate.
ERP Exposes What the Organization Has Avoided Addressing
ERP platforms are built on the assumption that the business already operates with a certain level of clarity. They expect well‑defined workflows, clear ownership, consistent data, and a shared understanding of how work should move across the enterprise. However, the reality is far from it!
When those elements are missing, the system forces decisions that the organization has postponed for years. Teams suddenly realize that different regions, or LOBs follow different processes, that controls are applied inconsistently, or that data definitions vary from one department to another.
These issues don’t disappear inside an ERP, they become embedded in it. And once they are embedded, they are no longer just operational problems; they become system problems that require technical fixes, change orders, 3rd party integrations, and costly redesigns. What could have been addressed through thoughtful process work becomes a multi‑million‑dollar remediation effort.
The Hidden Cost of Automating What Isn’t Working
When organizations move forward without addressing process gaps, the impact shows up in every phase of the ERP lifecycle.
Design workshops become debates about how work should happen rather than confirmations of how it does.
Requirements become contradictory because different teams have been operating in silos.
Customization grows because the system is being asked to replicate outdated or inefficient workflows.
Testing cycles reveal defects that trace back not to the system, but to unclear or unstable processes.
And when go‑live arrives, the business experiences disruption that could have been avoided. I’ve heard this many times: “Billing delays, inventory mismatches, compliance issues, and frustrated users who feel the system is working against them.”
These are not technology failures. They are symptoms of a process foundation that was never ready for ERP.
Why Process Redesign MUST Precede System Design
A successful ERP implementation is not a technology exercise (sorry IT folks out there!) it is the operational expression of a well‑designed future state. Before any system integrator begins configuration, the organization must have a clear understanding of how work should flow, who owns each step, what controls are required, what data is needed, and how decisions should be made. This clarity allows the ERP to be configured with intention rather than compromise.
When processes are defined upfront, the ERP becomes a natural extension of the operating model. Period. Design accelerates because decisions have already been made. Customization decreases because the business aligns more easily with ERP best practices (saving you $$$s). Data migration becomes smoother because the underlying structures are stable. And users adopt the system more readily because it reflects a workflow that makes sense. Happy processors = Satisfied end-users.
A Practical Blueprint for Process Readiness
Organizations that excel at ERP begin with a disciplined approach to process readiness. They start by assessing the current state, not just documenting workflows, but understanding the variations, pain points, and control gaps that have accumulated over time.
They then work toward standardization, aligning teams around a single enterprise way of operating unless regulatory or market differences require variation. From there, they design a future state that reflects best practices and supports the organization’s strategic goals. They embed controls and compliance into the workflow itself, ensuring that governance is built into the process rather than layered on top of it. They establish clear data ownership and quality standards so that the information feeding the ERP is reliable. And they prepare the organization for the change ahead, long before the system arrives.
This work is not glamorous, but it is essential. It is the difference between an ERP that becomes a catalyst for transformation and one that becomes a source of frustration.
The Strategic Benefits of Fixing Processes First
Organizations that invest in process readiness experience benefits that extend far beyond the ERP program. They see faster implementations, fewer change orders, and lower total cost of ownership. They gain cleaner data, stronger controls, and more consistent operations. Their teams adopt the system more easily because the workflows are intuitive and aligned with how the business should operate. And perhaps most importantly, they build an operating model that is scalable—ready for automation, AI, and future growth.
Process readiness is not a delay. It is the foundation that makes transformation possible.
Modern ERP platforms like SAP S/4HANA, Oracle Cloud, Workday, Microsoft Dynamics – they all are built around standardized, best‑practice processes. They assume the organization is ready to adopt them. But most organizations are not. And as AI and automation reshape how work gets done, process clarity becomes even more critical. Without it, organizations cannot take advantage of the technologies they are investing in.
ERP is the backbone of the enterprise. But a backbone is only as strong as the structure supporting it.
How I Can Help
This is the work I’ve spent my career leading across EY, RSM, and global organizations navigating complex transformation. I help companies close the process gap long before it becomes an ERP problem.
I begin by identifying the inconsistencies, bottlenecks, and control gaps that will derail an ERP program. I work with leaders to design future‑state workflows that align with best practices and the realities of the business. I help build governance structures that support decision‑making, clarify ownership, and reduce ambiguity. I strengthen data foundations so that the ERP is built on reliable information. And I prepare teams for the change ahead, ensuring that the organization is aligned, informed, and ready to adopt new ways of working.
The result is an ERP program that is faster, cleaner, and far more cost‑effective—and an operating model that is stronger, more scalable, and better positioned for growth.
If your organization is preparing for ERP or struggling with one already underway, I can help you build the foundation that ensures the system delivers the transformation you expect.