ERP implementations are the most disruptive technology projects manufacturing companies undertake. They change the system of record for every business process, require significant organizational change, consume enormous management attention during implementation, and have a long history of cost overruns, schedule delays, and operational disruptions. They also have a long history of delivering genuine long-term value when they succeed.
The manufacturing CEO who understands this duality approaches ERP implementation with realistic expectations, disciplined governance, and patient commitment to the long-term benefit rather than the short-term disruption. The CEO who approaches it with naive optimism about the timeline, the cost, or the operational impact creates the conditions for the failure narratives that have made so many manufacturing executives reluctant to undertake ERP projects at all.
Your governance of the ERP implementation is not optional. The decisions that determine whether an ERP project succeeds or fails are executive-level decisions: scope management, resource allocation, organizational change management, and the willingness to make difficult prioritization decisions when the project encounters the inevitable difficulties. Delegating all of these to the implementation team or the system integrator produces the most common ERP failure mode: an implementation that runs out of executive attention precisely when executive attention is most needed.
The Pre-Implementation Phase: Where Implementations Are Won or Lost
Most ERP implementation failures can be traced to decisions made before the implementation begins. The pre-implementation phase is where the conditions for success or failure are established, and it deserves as much executive attention as the implementation itself.
Requirements definition is the most important pre-implementation activity. Your ERP system will enforce the business processes it is configured to support. If your process requirements are defined imprecisely, the configured system will support imprecise processes. Most ERP implementations that fail to deliver their expected benefits failed to define requirements at the level of specificity needed to guide configuration decisions. “We need better production scheduling” is not a requirement. “Production planners need to generate a finite capacity schedule for the next four weeks, with the ability to model alternative scenarios and compare them on the basis of schedule attainment and overtime cost” is a requirement.
Vendor and implementation partner selection requires more diligence than most manufacturers apply. The ERP vendor’s manufacturing functionality, their reference customers in your specific sub-industry, and their implementation track record all matter. The implementation partner’s manufacturing expertise, their ERP implementation methodology, and specifically their track record with companies of your size and complexity matter as much as the software itself. Most failed ERP implementations involved a capable ERP system implemented by an inadequate implementation partner.
Data migration strategy is a pre-implementation decision that will constrain what is possible throughout the project. Your legacy system contains years of operational data: open orders, inventory balances, customer and supplier master data, cost standards, BOM structures, and routing data. How you migrate this data into the new system affects both the migration project complexity and the quality of the data in the new system from day one. Garbage-in, garbage-out applies to ERP migrations with particular force.
Building a Realistic Timeline
ERP implementations in manufacturing consistently take longer than initially planned. Understanding why helps you build a more realistic timeline from the outset rather than starting with an optimistic timeline that will be revised repeatedly.
The most common sources of timeline extension are: discovery of complexity not anticipated during scoping (almost inevitable in manufacturing operations with significant process complexity), data quality remediation that takes longer than estimated (also almost inevitable), configuration iterations that arise when initial configuration does not meet user needs (this is not failure; it is the design process working as it should), and testing that reveals integration issues requiring additional development (particularly common when the ERP must interface with production floor systems).
A realistic ERP implementation timeline for a mid-size manufacturing company typically runs 12 to 18 months for a single-site implementation of a standard manufacturing ERP. Multi-site implementations, custom development, or complex integration requirements extend timelines accordingly. Any vendor or integrator promising significantly shorter timelines for equivalent scope should be questioned closely about what is not included in their scope definition.
Build the implementation timeline around your operational calendar. Do not schedule your ERP go-live during your peak production season. Do not schedule it during your annual audit period. Do not schedule it when multiple key leadership team members are unavailable. The go-live period will require intensive management attention from your operations, finance, and IT leaders simultaneously, and scheduling it when those leaders are already at maximum capacity creates unnecessary risk.
Governance Structure for ERP Projects
ERP implementations need a governance structure that provides clear decision authority, regular oversight, and fast issue resolution. The most effective structure has three levels.
The executive steering committee, which should include the CEO, CFO, and COO or equivalent, meets monthly and is responsible for: approving scope changes, resolving issues that affect budget or timeline significantly, making organizational decisions that the implementation team cannot make independently, and maintaining organizational alignment with the project. The CEO’s active participation in the steering committee is essential; an ERP implementation that has nominal executive sponsorship but no real executive engagement loses the organizational priority that sustains it through difficult periods.
The project management office, typically led by an internal project manager with support from the integrator’s project management, meets weekly and is responsible for tracking progress against the plan, managing the project budget, coordinating across workstreams, and escalating issues that require steering committee decision. The internal project manager role is one of the most important staffing decisions in an ERP implementation; this person needs to have the organizational credibility, the operational knowledge, and the project management discipline to drive progress across multiple functional areas.
The workstream teams, covering specific functional areas such as production planning, purchasing, financials, and inventory, meet as needed and are responsible for requirements validation, configuration review, testing, and training within their area. These teams need to include your best operational people, not just whoever can be spared. ERP implementations that staff functional workstreams with employees who were not critical enough to their day jobs to protect often produce systems configured by people who do not understand the operation deeply enough.
Managing Scope
Scope creep is the most reliable way to extend an ERP implementation timeline and exceed the budget. It is also almost impossible to eliminate entirely because implementation invariably reveals requirements and connections that were not visible during scoping.
Build a formal scope change process that requires explicit approval for any addition to the project scope. Every scope addition should include a revised estimate of the time and cost impact. Many scope additions that seem minor in isolation have significant cascading effects on configuration, testing, and training. The discipline of quantifying these effects before approving additions prevents the gradual accumulation of scope that transforms a 12-month project into an 18-month project without any single decision being obviously wrong.
The counterbalancing discipline is scope reduction. When the project is running behind schedule, resist the temptation to recover by rushing. Instead, identify scope that can be deferred to a post-go-live phase without fundamentally compromising the system’s utility. A go-live with a core system that is solid and well-tested is better than a go-live with a complete system that is fragile and inadequately tested.
The technology implementation governance framework applies directly to ERP projects. The pilot-then-scale principle, applied in ERP contexts, often means implementing core modules first and more complex or specialized functionality later, giving the organization time to stabilize on the foundational capabilities before adding complexity.
Go-Live Planning and Stabilization
The go-live is not the end of the ERP project. It is the beginning of the most operationally challenging phase. In the weeks immediately after go-live, the operation is running on a new system that nobody is fully proficient in, legacy workarounds are no longer available, and every operational problem that the system would normally handle automatically requires manual intervention or assistance from the implementation team.
Plan the go-live period with the same intensity you would plan any major operational disruption. Identify the minimum support staff and system integrator resources that must be available during the first two to four weeks after go-live. Define clear escalation paths for system issues that prevent operational continuity. Have explicit contingency plans for the scenarios most likely to cause significant operational disruption: system unavailability, transaction processing failures, or reporting errors that affect production or financial close.
Communicate honestly with your customers and key suppliers about the ERP go-live timeline. Sophisticated customers understand that ERP implementations create temporary operational challenges. They do not understand being surprised by delivery failures or order management problems caused by an implementation you knew was planned. Proactive communication, reasonable commitments, and active monitoring of customer-critical shipments during the stabilization period protects customer relationships through an inherently challenging period.
Research from Panorama Consulting on ERP implementation outcomes found that manufacturing companies with active executive governance structures, including monthly steering committee involvement and explicit scope change management processes, achieved successful implementations at rates approximately twice those of companies without structured governance. Their annual ERP report with manufacturing implementation data is at Panorama Consulting’s ERP report.
Post-Go-Live Value Realization
ERP implementations that go live without a post-implementation program to realize the projected benefits routinely fail to deliver the business case that justified the investment. The technology is installed, but the operational changes, process improvements, and capability developments that were supposed to produce the financial benefits have not been systematically managed.
Build a benefits realization program that tracks the specific operational metrics that were supposed to improve as a result of the ERP implementation: inventory turns, schedule attainment, purchase order cycle time, period-end close time, and others relevant to your specific business case. Assign ownership for each benefit metric to the operational leader who has the authority to drive improvement in that area. Review progress quarterly in the 18 months following go-live.
When benefits are not materializing, investigate why. It is usually not because the system is incapable of enabling the benefit; it is because the organizational and process changes needed to realize the benefit have not occurred. System capability and operational benefit realization are separate challenges that require separate management attention.
The manufacturing CEO who governs an ERP implementation from pre-implementation through benefits realization, maintains personal engagement with the steering committee, makes the difficult decisions about scope and resources when they are needed, and holds the organization accountable for realizing the operational benefits that justified the investment will achieve what most ERP implementations fail to deliver: a system that genuinely improves operations and a team that is more capable at the end than at the beginning.
The equipment replacement schedule addresses capital planning discipline that supports ERP-driven operational improvements.
Related Reading
For further context, explore Annual Planning Timeline for Manufacturing CEOs: Running the Year-End Process Without Losing Momentum and Budget Review Schedule for Manufacturing CEOs: Running the Annual Process in a Capital-Intensive Business.