Almost every organization has one.
The Immortal Spreadsheet.
You know the one. It started as a temporary workaround years ago.
Nobody remembers who created it.
Everyone depends on it.
Somehow, each year, it acquires a few more tabs, a few more formulas, and a few more warnings not to touch anything.
But the spreadsheet itself usually isn’t the problem.
The real issue is that temporary solutions have a funny way of becoming permanent processes.
- A manual approval step gets added for a special circumstance.
- A workaround solves a reporting gap.
- One department develops its own way of handling a task because “that’s how we’ve always done it.”
Over time, those decisions become embedded in the way the business operates.
Then an ERP project begins.
In my previous article on ERP implementation success factors, I discussed why successful ERP projects depend on much more than software selection alone. Organizations evaluating solutions like Microsoft Dynamics 365 Business Central often focus on features and functionality first, but process clarity, organizational alignment, and user adoption all play important roles.
One of the biggest reasons ERP projects struggle deserves a closer look: organizations often try to automate processes before they’ve fully defined, standardized, or improved them.
That’s why ERP process optimization is such a critical part of implementation success. ERP systems can streamline workflows, improve visibility, and support growth, but they don’t automatically fix operational confusion.
More often, they expose it.
In this article, I’ll explore why “lift and shift” ERP implementations often fall short, what operational clarity actually means, how ERP implementation process mapping helps uncover hidden inefficiencies, and why fixing broken processes before automation can have a bigger impact than any feature list or dashboard.
Why Do ERP “Lift and Shift” Implementations Fail?
One of the biggest misconceptions in ERP is the idea that a new system will automatically improve how a business operates.
I’ve seen organizations spend months planning an ERP migration, selecting software, and preparing for implementation, only to discover they’re rebuilding the same inefficient processes inside a newer platform.
That’s the challenge with “lift and shift” ERP projects. Instead of rethinking how work should happen, companies simply move existing workflows into a new system. The technology changes, but the underlying processes remain exactly the same.
The problem is that ERP systems don’t hide operational issues. They expose them. That’s why ERP process optimization should be viewed as a business initiative, not simply a software activity.
- If a purchasing process relies on unnecessary approvals, those approvals still exist after implementation.
- If departments use different methods to perform the same task, that inconsistency doesn’t disappear.
- If reporting depends on manual workarounds and disconnected spreadsheets, the new system will quickly reveal those weaknesses.
This is one reason ERP process optimization is so important before implementation begins. ERP systems are designed to bring structure and visibility to business operations, but they aren’t designed to determine how those operations should work.
I’ve seen the same pattern repeatedly during ERP projects: organizations achieve better outcomes when they improve underlying processes alongside the technology rather than treating software as the solution by itself.
That’s also a major reason why ERP implementations fail. The software often gets blamed for problems that actually originated in workflow design, process ownership, or operational inconsistencies that existed long before the project started.
Successful ERP projects don’t begin with configuration.
They begin with asking whether the current process is worth preserving in the first place.
What Does “Operational Clarity” Mean in an ERP Implementation?
Operational clarity is one of those phrases that sounds straightforward until you ask several departments to describe the same process.
That’s often when the confusion begins.
One team describes a workflow one way. Another team explains it differently. A third group has created its own variation because it was easier than following the original process.
In an ERP implementation, operational clarity means having a shared understanding of how work moves through the organization. It means defining responsibilities, documenting workflows, establishing consistent processes, and ensuring teams agree on how work should be performed before the system is configured.
This is a critical part of ERP process optimization because ERP software can automate a process, but it can’t decide whether that process makes sense.
I’ve seen organizations discover during implementation that different departments use different definitions for the same operational task. I’ve also seen reporting challenges traced back to inconsistent workflows rather than technology limitations.
Those situations aren’t software problems.
They’re process problems.
That’s why understanding the business process before ERP implementation is critical. Without that foundation, ERP process optimization becomes far more difficult because teams are trying to improve workflows they don’t fully understand.
When organizations take the time to create operational clarity first, they typically make better configuration decisions, encounter fewer surprises during implementation, and achieve stronger long-term results.
Why ERP Process Optimization Creates Better Reporting, Efficiency, and Scalability
When most organizations consider ERP benefits, they often think about dashboards, reporting tools, automation, and visibility.
Those outcomes are certainly important, but they don’t appear automatically just because new software is installed.
They emerge when strong processes support the technology.
Effective ERP process optimization creates consistency in how data is captured, how work moves through the business, and how decisions are made. That consistency improves reporting because everyone is working from the same processes and the same operational assumptions.
It also improves efficiency.
Instead of maintaining multiple workarounds, duplicate approvals, or department-specific processes, organizations can simplify how work gets done across the business.
Scalability is another major benefit.
Processes that depend on tribal knowledge, manual intervention, or individual spreadsheets often become difficult to sustain as organizations grow. Standardized workflows create a stronger foundation for expansion because they reduce complexity and improve repeatability.
The goal isn’t simply to automate work. It’s to create processes that are worth automating.
That’s where ERP workflow optimization delivers some of its greatest value.
How Do You Map and Fix Broken Processes Before Implementing ERP?
One of the best ways to improve implementation outcomes is through ERP implementation process mapping.
Before making decisions about configuration, organizations should develop a clear picture of how work currently happens throughout the business.
That includes documenting workflows, identifying bottlenecks, reviewing approval processes, and uncovering manual workarounds that may have accumulated over time.
Process mapping often reveals inefficiencies that teams no longer notice because they’ve become part of daily operations.
According to the Lucidchart process mapping guide, visualizing workflows helps organizations identify gaps, redundancies, and opportunities for improvement that may otherwise remain hidden.
But documenting current processes is only part of the exercise.
One of the most useful exercises during ERP process optimization isn’t documenting how work happens today. It’s comparing those workflows against processes that have already proven effective in similar organizations. The gaps between the two often reveal opportunities for improvement that might otherwise go unnoticed.
This is often where some of the biggest improvements occur:
- Teams discover approval steps that no longer serve a purpose.
- Reporting processes become simpler.
- Data collection becomes more consistent.
- Workflows become easier to understand and maintain.
It’s also where fixing broken processes before automation becomes essential.
If an inefficient process is automated without improvement, the organization may complete the work faster, but the underlying inefficiency still exists. In some cases, it becomes harder to recognize because the technology makes it appear more streamlined.
The strongest implementations don’t focus exclusively on automation.
They focus on improving the process first and then using technology to support it.
When organizations begin an ERP project, it’s tempting to focus on software features, dashboards, integrations, and automation opportunities.
Those things matter.
But the success of the implementation often depends on work that happens long before configuration begins.
ERP process optimization creates the operational clarity needed for better reporting, greater efficiency, and sustainable growth. The strongest results come from treating it as an ongoing effort rather than a one-time implementation activity.
Most importantly, it helps organizations avoid carrying old operational problems into a new system. After all, the goal isn’t to move the Immortal Spreadsheet into a more modern ERP platform. It’s to understand why it exists in the first place and decide whether the process behind it still belongs there.
In the final article in this series, I’ll shift from processes to people and explore why user adoption and employee buy-in often determine whether even the best-designed ERP system delivers long-term value.
If you’re evaluating an ERP project and want a clearer understanding of the processes behind it, let’s have a conversation.
About Mike Stallmann
Meet Mike Stallmann, Director of Product and Business Development, Co-founder at Oztera, and the original “Chief Geek Juggler.” With decades of ERP innovation under his belt and over 200 successful deployments, Mike’s involvement with business technology is extensive.
From wineries to agriculture and beyond, Mike and Oztera specialize in solving complex, industry-specific challenges. If you’re looking to leverage technology for growth and efficiency, our experience is your secret weapon.
For insights and actionable advice, connect with Mike on LinkedIn and discover what tech-driven business transformation looks like.