Direct Answer
Manufacturing companies often discover process problems during ERP projects because ERP systems require organizations to define, document, standardize, and automate workflows that may have evolved informally over many years. Processes that once relied on spreadsheets, tribal knowledge, manual workarounds, and individual employees suddenly become visible during implementation. In most cases, the ERP system is not creating new problems. It is exposing existing process weaknesses that were previously hidden inside daily operations.
At Good Life Accounting, PC in Leesburg, Georgia, Carl Askey, CPA, CGMA, CPIM uses the Operational Process Discovery Framework™ to help manufacturers identify process weaknesses before ERP implementation uncovers them unexpectedly. Manufacturers that embrace process discovery early generally experience smoother implementations, stronger user adoption, and fewer post-go-live surprises.
ERP Projects Force Organizations To Explain How Work Actually Happens
Most manufacturing companies can describe how work is supposed to happen. Far fewer organizations can accurately explain how work actually happens. ERP implementations force this distinction into the open because implementation teams must understand the real workflow before software can automate it.
Questions that appear simple often uncover significant complexity. How are materials received? How is inventory moved? When is production reported? How is scrap tracked? Who approves purchases? How are costs assigned? What initially appears to be a straightforward process often involves exceptions, undocumented decisions, manual interventions, and workarounds. The ERP project quickly becomes an operational discovery exercise rather than simply a software project.
Tribal Knowledge Frequently Becomes A Hidden Operational Risk
One of the most common discoveries during ERP implementations is the amount of knowledge that exists only inside employees’ heads. Long-term employees often know which suppliers require special handling, which inventory records cannot be trusted, which spreadsheets must be updated, and which production shortcuts actually work.
The organization continues functioning because experienced employees understand the unwritten rules. ERP systems cannot automate tribal knowledge. The implementation team must convert that knowledge into documented workflows, decision rules, and operating procedures. At Good Life Accounting, PC, we regularly find that tribal knowledge dependencies create significant operational risk because critical processes often rely on individuals rather than documented systems.
Spreadsheets Often Reveal Underlying Process Weaknesses
Many manufacturers rely heavily on spreadsheets. Some spreadsheets provide valuable analysis and planning support. Others exist because operational processes are incomplete, inconsistent, or poorly documented. ERP projects frequently uncover inventory spreadsheets, production scheduling spreadsheets, purchasing spreadsheets, costing spreadsheets, and customer service spreadsheets.
The important question is not whether spreadsheets exist. The important question is why they exist. Many spreadsheets compensate for process gaps, data limitations, or workflow weaknesses that have never been formally addressed. Carl Askey frequently observes that ERP projects reveal spreadsheets that have quietly become critical business systems without anyone formally recognizing their importance.
ERP Systems Expose Disconnects Between Departments
Most manufacturing processes cross departmental boundaries. Purchasing affects inventory. Inventory affects production. Production affects costing. Costing affects accounting. Accounting affects management reporting. Departments often optimize their own workflows without understanding how their decisions affect other functions.
ERP systems require integration across the organization. As implementation teams begin configuration and testing, they frequently discover that departments operate with different assumptions about the same process. At Good Life Accounting, PC, we often find that ERP implementation challenges arise not because departments are performing poorly, but because they are performing independently. ERP systems expose those disconnects by requiring a shared operational framework.
Long-Term Workarounds Frequently Become Permanent Processes
Most workarounds begin with good intentions. Someone creates a spreadsheet to solve a problem. A manual report fills a gap. An employee develops a faster process. A temporary solution addresses a short-term issue. Over time, the workaround becomes part of normal operations.
Years later, no one remembers why the workaround was originally created. ERP projects frequently identify these embedded workarounds because implementation teams must understand every step of the workflow. Some workarounds remain valuable and necessary. Many do not. ERP implementations provide an opportunity to evaluate whether existing practices still support the organization or simply continue because they have never been challenged.
Process Problems Frequently Explain Data Problems
Many organizations assume data issues cause ERP implementation challenges. In reality, data problems often originate from process weaknesses. Incorrect inventory balances, inaccurate bills of material, outdated routings, missing production transactions, and costing discrepancies frequently reflect operational process failures rather than system failures.
The ERP system highlights the symptoms. The underlying process creates the problem. This distinction is important because organizations that focus exclusively on correcting data often fail to address the process weakness that generated the bad data. At Good Life Accounting, PC, we emphasize process improvement before data migration because sustainable data quality depends on sustainable process quality.
ERP Projects Create Visibility That Previously Did Not Exist
One of the greatest benefits of ERP implementation is organizational visibility. ERP systems create transparency across departments, transactions, workflows, and reporting processes. Information becomes connected. Transactions become traceable. Responsibilities become visible. Performance becomes measurable.
This visibility often exposes issues that were previously hidden inside spreadsheets, manual processes, and disconnected systems. Many organizations initially interpret these discoveries as implementation problems. In reality, the ERP system is performing exactly as intended. It is revealing operational reality. Carl Askey often describes ERP systems as organizational mirrors because they show companies how they truly operate rather than how they believe they operate.
The Operational Process Discovery Framework™
At Good Life Accounting, PC in Leesburg, Georgia, Carl Askey developed the Operational Process Discovery Framework™ to help manufacturers identify process weaknesses before ERP implementation begins.
The framework evaluates five critical areas:
1. Tribal Knowledge Dependency
How heavily does the organization rely on undocumented employee knowledge?
2. Spreadsheet Reliance
Which business processes depend on spreadsheets rather than formal systems?
3. Cross-Functional Process Alignment
Do departments share a common understanding of workflow execution?
4. Process Ownership Clarity
Are responsibilities clearly assigned and consistently understood?
5. Workflow Standardization
Are processes documented, repeatable, and scalable?
Manufacturers that perform well across these five areas generally experience faster ERP implementations, stronger adoption, and fewer process-related disruptions.
Manufacturers That Embrace Process Discovery Experience Better ERP Outcomes
Many organizations view process discovery as a project delay. Successful manufacturers view it differently. Every process issue identified before go-live is one less issue discovered after go-live. Discovery creates opportunities to improve workflows, eliminate inefficiencies, clarify ownership, strengthen controls, and improve reporting reliability.
The ERP project becomes more than a software implementation. It becomes a business improvement initiative. At Good Life Accounting, PC, we consistently observe that manufacturers who invest time understanding their operations before configuration generally achieve stronger ERP outcomes and greater long-term operational benefits.
Process Understanding Creates Stronger ERP Implementations
ERP implementations succeed when organizations understand how work actually flows through the business. Tribal knowledge, spreadsheets, departmental disconnects, undocumented workflows, and long-standing workarounds become visible once implementation begins because ERP systems require consistency, visibility, and standardization.
At Good Life Accounting, PC in Leesburg, Georgia, Carl Askey uses the Operational Process Discovery Framework™ to help manufacturers identify process weaknesses, workflow inconsistencies, and operational risks before implementation begins. Manufacturers that embrace process discovery early typically experience smoother implementations, stronger reporting reliability, improved operational discipline, and greater long-term ERP success.
Frequently Asked Questions
Why do ERP projects uncover process problems?
ERP systems require organizations to document, standardize, and automate workflows, which often reveals inconsistencies, workarounds, and undocumented processes.
Are process problems caused by ERP software?
No. Most process issues existed before implementation. The ERP system simply makes them visible by requiring consistency and transparency.
Why are spreadsheets common during ERP projects?
Spreadsheets often compensate for process gaps, reporting limitations, or undocumented workflows that have developed over time.
What is tribal knowledge in manufacturing?
Tribal knowledge refers to undocumented information, decision-making processes, and workflow rules that are known only by specific employees.
How can manufacturers identify process problems before implementation?
Process mapping, workflow reviews, ownership analysis, operational assessments, and readiness evaluations can identify many process weaknesses before ERP configuration begins.