ERP Implementation Isn’t the Goal: Process Improvement Is (Part 2)
By Craig Crossley
Introduction
Last month, we discussed why ERP implementation isn’t the goal—process improvement is. ERP systems bring structure and visibility, but they also expose gaps in how work actually happens across the business.
The next question is: what does it take to turn that visibility into meaningful improvement?
Cross-Functional Alignment Is Where It Breaks Down
Cross-functional alignment matters more than many organizations expect. ERP touches engineering, procurement, operations, and finance simultaneously, and the handoffs between those groups are where real value or real pain shows up.
A system can be configured correctly for each function, yet still fall short if the workflow between functions is unclear or inconsistent. Similarly, training often misses the mark when it focuses only on which buttons to click, rather than what the process is designed to accomplish and how each person’s actions impact downstream teams.
This is where many ERP implementations begin to struggle - not because of the technology, but because alignment, process clarity, and real-world execution weren’t fully addressed upfront.
A Different Approach to Implementation
At Visibility, this is exactly where we focus. ERP success depends as much on people and process as it does on technology. Implementation is not treated as simply deploying software, it’s treated as an opportunity to improve how the business operates while building the ERP foundation to support that improvement.
A key difference is who is guiding the work.
Engineering and manufacturing environments are not generic. They come with real-world complexity that can’t be fully understood through manuals or templates. Priorities shift. Capacity is finite. Supplier lead times change. Engineering changes ripple into purchasing and production. Job cost, WIP, and margin behave differently in practice than they do in spreadsheets.
Without a deep understanding of these realities, it’s easy to design a solution that looks good in a conference room but doesn’t hold up on the shop floor or in a planning meeting. Visibility brings experienced consultants with firsthand backgrounds in process engineering, applications engineering, procurement, operations, and finance—within engineering and manufacturing environments.
That experience changes the nature of implementation conversations. It shifts the focus from:
“How do we set up the system?”
to
“How do we improve the process the system is meant to support?”
It also helps bridge the gap between what leadership wants, what users need, and what the system requires to deliver reliable, repeatable outcomes.
Teaching Over Training
That’s why Visibility emphasizes teaching, not just training.
Training tells people what to click. Teaching helps people understand why the process matters, how their role impacts other teams, and how consistent execution strengthens overall business performance.
When users understand the “why,” the system becomes less of a burden and more of a tool. The ERP becomes part of how work gets done, rather than something people try to work around.
Conclusion
A successful ERP implementation should do more than document transactions. It should help teams become more aligned, more predictable, more efficient, and more scalable. That is the difference between simply going live and truly improving.
Go-live is an important milestone, but it is not the end goal. The real goal is what happens after go-live: smoother execution, clearer visibility, stronger coordination across departments, and a business that operates with greater discipline and confidence.
At Visibility, we believe the best ERP implementations are led by people who understand the realities of engineering and manufacturing - because those realities are where true process improvement begins.
To get a free demo today, click here to connect with our team and schedule a time that works best for you.
