What Operations Managers Wish the CEO Understood About ERP Implementation

Every operations manager knows the feeling. You’ve spent months building the case for an ERP system. You’ve documented the inefficiencies, calculated the labor hours lost to manual data entry, and watched your team drown in disconnected spreadsheets. Finally, the CEO agrees: it’s time to implement an ERP.

Then the questions start. “Can we do this in 90 days?” “Why does it cost that much?” “Can’t IT just handle it?”

And suddenly you realize the hardest part of ERP implementation isn’t the technology. It’s getting leadership to understand what this project actually requires.

This isn’t about pointing fingers. CEOs have legitimate concerns about cost, timeline, and disruption. But there’s a persistent gap between executive expectations and operational reality when it comes to ERP projects. Bridging that gap is often the difference between a system that transforms your business and an expensive piece of software nobody uses.

Here’s what operations managers wish they could say in the boardroom.

This Is a Business Transformation, Not a Software Installation

The most common misconception at the executive level is treating ERP implementation like buying new equipment. You purchase it, install it, train people for a day or two, and move on.

That’s not how this works.

An ERP system touches every part of your business: how you process orders, track inventory, manage vendors, handle accounting, and communicate across departments. Implementing one means rethinking workflows that have existed for years. It means asking uncomfortable questions about why things are done a certain way and whether those reasons still make sense.

A 2023 study by Panorama Consulting found that 74% of ERP projects experienced schedule overruns. The primary cause wasn’t technical failure. It was underestimating the scope of organizational change required.

When a CEO asks “why is this taking so long,” the honest answer is usually that the company is doing more than installing software. It’s redesigning how work gets done. That takes time, testing, and iteration.

Operations managers see this complexity daily. They know that the warehouse team has workarounds for the inventory system that nobody documented. They know that the sales process involves three spreadsheets and a shared inbox that somehow holds everything together. Replacing those systems isn’t plug-and-play. It requires understanding what exists, deciding what should change, and managing the human side of that transition.

The CEO’s job is strategic vision. The operations manager’s job is making things actually work. ERP implementation lives in the gap between those two perspectives, and closing that gap requires real conversation about what transformation means in practice.

Budget Conversations Miss the Real Costs

When leadership evaluates ERP costs, they typically focus on licensing fees and maybe some implementation consulting. That’s the visible part of the iceberg.

The submerged portion includes data migration, custom integrations, employee training, productivity loss during transition, and the ongoing cost of maintaining the system after go-live. Working with experienced Odoo ERP implementation services can help companies anticipate these hidden costs upfront, but many organizations learn about them the hard way.

According to research from Mint Jutras, the average ERP implementation costs 25% more than initially budgeted. Organizations that planned for comprehensive change management from the start came much closer to their original estimates.

Here’s what operations managers wish CEOs would budget for:

1. Data cleanup before migration. Your existing data is messier than you think. Duplicate customer records, inconsistent product codes, incomplete vendor information. Someone has to fix that before it goes into the new system, and that someone is usually your operations team working overtime.
2. Parallel running periods. Most implementations require running old and new systems simultaneously for weeks or months. That means double the work for staff during a critical transition period.
3. Post-launch support and refinement. Day one isn’t the finish line. The first 90 days after go-live typically require significant adjustments, additional training, and troubleshooting that wasn’t anticipated during planning.
4. Lost productivity during the learning curve. Even well-trained employees are slower on a new system. For the first few months, expect 15-25% productivity reduction in affected departments. That’s a real cost that rarely appears in project budgets.

The total cost of ownership for an ERP extends years beyond the initial implementation. Operations managers live with these ongoing costs; they’re the ones fielding complaints when the system doesn’t work as expected or when a critical report takes three times longer than it used to.

The Timeline Pressure Creates Long-Term Problems

There’s a predictable pattern in ERP projects. Leadership wants the system live by a specific date, usually tied to a fiscal year, a board meeting, or just general impatience. The implementation team knows that timeline is aggressive. They push back. Leadership holds firm. Corners get cut.

Then everyone lives with the consequences for years.

Rushing an ERP implementation creates technical debt that compounds over time. Configurations that were “good enough” for launch become permanent limitations. Training that was condensed into a single day leaves employees confused and resistant. Integrations that weren’t fully tested break in production, causing data discrepancies that take months to untangle.

A Gartner analysis found that organizations rushing ERP implementations were 50% more likely to require significant remediation within the first two years. That remediation often costs more than taking adequate time in the first place would have.

Operations managers understand this math intuitively. They’re the ones who will manage the workarounds, field the complaints, and eventually make the case for fixing what wasn’t done right the first time.

What they wish CEOs understood is that timeline flexibility isn’t a sign of poor project management. It’s a recognition that complex systems require adequate time for:

• Thorough requirements gathering that captures how work actually happens, not just how it’s supposed to happen
• Testing with real data and real users before go-live
• Training that gives employees time to practice, ask questions, and build confidence
• Contingency for the unexpected problems that always emerge

The question isn’t whether the project will hit obstacles. The question is whether there’s enough buffer to handle them without compromising the result.

Your IT Department Can’t Do This Alone

Many CEOs assume that ERP implementation is fundamentally an IT project. IT selected the vendor, IT understands the technical requirements, so IT should lead the implementation.

This approach fails more often than it succeeds.

ERP systems are business systems that happen to run on technology. The critical decisions aren’t about server configurations or database structures. They’re about how orders flow through the company, when inventory should trigger reorders, which approvals are required for purchases, and how financial data rolls up into reports.

These are operations questions, not IT questions.

Successful implementations require deep involvement from the people who actually do the work. That means operations managers, department heads, and frontline employees who understand the nuances of daily business processes.

The role breakdown that works looks like this:

• Executive sponsorship provides resources, removes obstacles, and signals organizational commitment
• Operations leadership defines requirements, validates configurations, and manages change within their teams
• IT handles technical infrastructure, security, integrations, and ongoing system maintenance
• External implementation partners bring methodology, experience with the specific platform, and an outside perspective on best practices

When any of these groups is absent or marginalized, problems emerge. IT-led implementations often create systems that are technically sound but operationally awkward. Operations-led implementations without IT involvement create security vulnerabilities and integration gaps. And implementations without strong executive sponsorship tend to lose momentum and budget when competing priorities emerge.

Operations managers often find themselves trying to compensate for missing pieces. They become unofficial project managers, translators between business needs and technical capabilities, and change management leaders by default. That’s exhausting and unsustainable.

Change Management Is Not a Soft Skill

When budget pressure hits an ERP project, change management is usually the first casualty. Training gets compressed. Communication plans get simplified. The assumption is that people will figure it out once the system goes live.

This is backwards. People are the entire point.

An ERP system is only valuable if employees use it correctly and consistently. A perfectly configured system that people avoid, work around, or use incorrectly is worthless. According to Prosci research, projects with excellent change management were six times more likely to meet objectives than those with poor change management.

Operations managers see resistance firsthand. They hear the complaints: the old system was faster, I don’t understand why we changed, this doesn’t work the way I need it to. They watch employees create shadow spreadsheets to avoid using the new system. They deal with the fallout when data quality suffers because people are entering information incorrectly or not at all.

What effective change management requires:

• Early and honest communication about why the change is happening, what it means for individual roles, and what support will be available
• Involvement of affected employees in requirements gathering and testing, creating ownership and incorporating practical knowledge
• Training that matches how adults actually learn: hands-on practice with realistic scenarios, not just demonstrations of features
• Visible leadership commitment that signals this isn’t optional and won’t be abandoned when it gets difficult
• Feedback channels that let employees raise concerns and see those concerns addressed

None of this is optional if you want the implementation to succeed. But it all requires time, attention, and budget that often gets squeezed when leadership focuses primarily on technical milestones.

Success Metrics Need to Be Realistic and Long-Term

CEOs want to know when the investment will pay off. That’s reasonable. But the way ROI questions get framed often creates unrealistic expectations.

Asking “when will we see returns” implies that there’s a specific date when benefits suddenly materialize. In reality, ERP value accumulates gradually and depends heavily on how well the system is adopted and optimized over time.

The Hackett Group’s research on ERP implementations found that organizations typically require 23 months to realize full benefits from their ERP investment. Companies that expected faster returns often declared projects failures prematurely, sometimes abandoning optimization efforts just as benefits were beginning to materialize.

Operations managers would prefer honest conversations about what success looks like at different stages:

Months 1-3 post-launch: Stabilization. The goal is getting core processes working reliably. Expect problems, firefighting, and frustrated employees. Success means the business continues operating without major disruption.

Months 4-6: Optimization. Users are more comfortable, and patterns emerge about what’s working and what needs adjustment. Success means making improvements based on real usage data.

Months 7-12: Value capture. Processes are stable enough to measure improvements. Success means documenting efficiency gains, error reductions, and time savings against baseline metrics.

Year 2 and beyond: Strategic leverage. The system becomes a platform for further improvement, automation, and data-driven decision making. Success means using ERP capabilities that weren’t priorities during initial implementation.

Declaring victory or failure at month three misses the point entirely. Operations managers know that real operational excellence takes time to build. They’d rather have leadership patience and sustained support than premature pressure for ROI numbers.

What Operations Managers Actually Need From Leadership

This isn’t a list of complaints. It’s a request for partnership.

Operations managers want ERP implementations to succeed. They’re the ones who will benefit most from streamlined processes, better data, and systems that actually support how work gets done. They’re also the ones who absorb the impact when implementations struggle.

What would help:

Trust operational expertise. When the operations team says a timeline is unrealistic or a feature is essential, that assessment comes from direct knowledge of how the business actually runs. Dismissing those concerns because they’re inconvenient creates problems that surface later at higher cost.

Maintain visible commitment. ERP implementations are marathons. When leadership attention drifts to other priorities, momentum dies. Regular check-ins, continued resource allocation, and public reinforcement that this project matters all signal that the organization is serious.

Expect messiness. No implementation goes according to plan. Budgets shift, timelines slip, and unexpected problems emerge. That’s normal. The question is whether leadership treats these as learning opportunities or as failures to be punished.

Invest in people, not just software. The technology is the easy part. Getting hundreds of employees to change how they work is the hard part. Budget and plan accordingly.

Take the long view. The value of ERP isn’t in the go-live celebration. It’s in the years of improved operations that follow when the system is adopted, optimized, and leveraged for competitive advantage.

The Conversation Worth Having

ERP implementation represents one of the largest operational investments most companies make. Getting it right requires alignment between strategic vision and operational reality.

That alignment doesn’t happen automatically. It requires honest conversation between executives who set direction and operations managers who understand what execution actually demands.

The gap between these perspectives isn’t a problem to eliminate. It’s a tension to manage productively. CEOs should push for efficiency and accountability. Operations managers should advocate for realism and adequate resources. The best outcomes emerge when both perspectives are heard and balanced.

If you’re an operations manager preparing to make the case for ERP investment, or navigating an implementation that’s hitting turbulence, know that your concerns are valid. The challenges you’re experiencing are common across organizations of all sizes and industries.

And if you’re a CEO reading this, consider it an invitation. Ask your operations team what they wish you understood. Listen to the answer. The success of your ERP investment might depend on that conversation more than any technical decision you’ll make.

When a CEO asks “why is this taking so long,” the honest answer is usually that the company is doing more than installing software. It’s redesigning how work gets done. That takes time, testing, and iteration.

Operations managers see this complexity daily. They know that the warehouse team has workarounds for the inventory system that nobody documented. They know that the sales process involves three spreadsheets and a shared inbox that somehow holds everything together. Replacing those systems isn’t plug-and-play. It requires understanding what exists, deciding what should change, and managing the human side of that transition.

The CEO’s job is strategic vision. The operations manager’s job is making things actually work. ERP implementation lives in the gap between those two perspectives, and closing that gap requires real conversation about what transformation means in practice.

Budget Conversations Miss the Real Costs

When leadership evaluates ERP costs, they typically focus on licensing fees and maybe some implementation consulting. That’s the visible part of the iceberg.

The submerged portion includes data migration, custom integrations, employee training, productivity loss during transition, and the ongoing cost of maintaining the system after go-live. Working with experienced Odoo ERP implementation services can help companies anticipate these hidden costs upfront, but many organizations learn about them the hard way.

According to research from Mint Jutras, the average ERP implementation costs 25% more than initially budgeted. Organizations that planned for comprehensive change management from the start came much closer to their original estimates.

Here’s what operations managers wish CEOs would budget for:

Data cleanup before migration. Your existing data is messier than you think. Duplicate customer records, inconsistent product codes, incomplete vendor information. Someone has to fix that before it goes into the new system, and that someone is usually your operations team working overtime.

Parallel running periods. Most implementations require running old and new systems simultaneously for weeks or months. That means double the work for staff during a critical transition period.

Post-launch support and refinement. Day one isn’t the finish line. The first 90 days after go-live typically require significant adjustments, additional training, and troubleshooting that wasn’t anticipated during planning.

Lost productivity during the learning curve. Even well-trained employees are slower on a new system. For the first few months, expect 15-25% productivity reduction in affected departments. That’s a real cost that rarely appears in project budgets.

The total cost of ownership for an ERP extends years beyond the initial implementation. Operations managers live with these ongoing costs; they’re the ones fielding complaints when the system doesn’t work as expected or when a critical report takes three times longer than it used to.

The Timeline Pressure Creates Long-Term Problems

There’s a predictable pattern in ERP projects. Leadership wants the system live by a specific date, usually tied to a fiscal year, a board meeting, or just general impatience. The implementation team knows that timeline is aggressive. They push back. Leadership holds firm. Corners get cut.

Then everyone lives with the consequences for years.

Rushing an ERP implementation creates technical debt that compounds over time. Configurations that were “good enough” for launch become permanent limitations. Training that was condensed into a single day leaves employees confused and resistant. Integrations that weren’t fully tested break in production, causing data discrepancies that take months to untangle.

A Gartner analysis found that organizations rushing ERP implementations were 50% more likely to require significant remediation within the first two years. That remediation often costs more than taking adequate time in the first place would have.

Operations managers understand this math intuitively. They’re the ones who will manage the workarounds, field the complaints, and eventually make the case for fixing what wasn’t done right the first time.

What they wish CEOs understood is that timeline flexibility isn’t a sign of poor project management. It’s a recognition that complex systems require adequate time for:

Thorough requirements gathering that captures how work actually happens, not just how it’s supposed to happen
Testing with real data and real users before go-live
Training that gives employees time to practice, ask questions, and build confidence
Contingency for the unexpected problems that always emerge

The question isn’t whether the project will hit obstacles. The question is whether there’s enough buffer to handle them without compromising the result.

Your IT Department Can’t Do This Alone

Many CEOs assume that ERP implementation is fundamentally an IT project. IT selected the vendor, IT understands the technical requirements, so IT should lead the implementation.

This approach fails more often than it succeeds.

ERP systems are business systems that happen to run on technology. The critical decisions aren’t about server configurations or database structures. They’re about how orders flow through the company, when inventory should trigger reorders, which approvals are required for purchases, and how financial data rolls up into reports.

These are operations questions, not IT questions.

Successful implementations require deep involvement from the people who actually do the work. That means operations managers, department heads, and frontline employees who understand the nuances of daily business processes.

The role breakdown that works looks like this:

Executive sponsorship provides resources, removes obstacles, and signals organizational commitment
Operations leadership defines requirements, validates configurations, and manages change within their teams
IT handles technical infrastructure, security, integrations, and ongoing system maintenance
External implementation partners bring methodology, experience with the specific platform, and an outside perspective on best practices

When any of these groups is absent or marginalized, problems emerge. IT-led implementations often create systems that are technically sound but operationally awkward. Operations-led implementations without IT involvement create security vulnerabilities and integration gaps. And implementations without strong executive sponsorship tend to lose momentum and budget when competing priorities emerge.

Operations managers often find themselves trying to compensate for missing pieces. They become unofficial project managers, translators between business needs and technical capabilities, and change management leaders by default. That’s exhausting and unsustainable.

Change Management Is Not a Soft Skill

When budget pressure hits an ERP project, change management is usually the first casualty. Training gets compressed. Communication plans get simplified. The assumption is that people will figure it out once the system goes live.

This is backwards. People are the entire point.

An ERP system is only valuable if employees use it correctly and consistently. A perfectly configured system that people avoid, work around, or use incorrectly is worthless. According to Prosci research, projects with excellent change management were six times more likely to meet objectives than those with poor change management.

Operations managers see resistance firsthand. They hear the complaints: the old system was faster, I don’t understand why we changed, this doesn’t work the way I need it to. They watch employees create shadow spreadsheets to avoid using the new system. They deal with the fallout when data quality suffers because people are entering information incorrectly or not at all.

What effective change management requires:

Early and honest communication about why the change is happening, what it means for individual roles, and what support will be available
Involvement of affected employees in requirements gathering and testing, creating ownership and incorporating practical knowledge
Training that matches how adults actually learn: hands-on practice with realistic scenarios, not just demonstrations of features
Visible leadership commitment that signals this isn’t optional and won’t be abandoned when it gets difficult
Feedback channels that let employees raise concerns and see those concerns addressed

None of this is optional if you want the implementation to succeed. But it all requires time, attention, and budget that often gets squeezed when leadership focuses primarily on technical milestones.

Success Metrics Need to Be Realistic and Long-Term

CEOs want to know when the investment will pay off. That’s reasonable. But the way ROI questions get framed often creates unrealistic expectations.

Asking “when will we see returns” implies that there’s a specific date when benefits suddenly materialize. In reality, ERP value accumulates gradually and depends heavily on how well the system is adopted and optimized over time.

The Hackett Group’s research on ERP implementations found that organizations typically require 23 months to realize full benefits from their ERP investment. Companies that expected faster returns often declared projects failures prematurely, sometimes abandoning optimization efforts just as benefits were beginning to materialize.

Operations managers would prefer honest conversations about what success looks like at different stages:

Months 1-3 post-launch: Stabilization. The goal is getting core processes working reliably. Expect problems, firefighting, and frustrated employees. Success means the business continues operating without major disruption.

Months 4-6: Optimization. Users are more comfortable, and patterns emerge about what’s working and what needs adjustment. Success means making improvements based on real usage data.

Months 7-12: Value capture. Processes are stable enough to measure improvements. Success means documenting efficiency gains, error reductions, and time savings against baseline metrics.

Year 2 and beyond: Strategic leverage. The system becomes a platform for further improvement, automation, and data-driven decision making. Success means using ERP capabilities that weren’t priorities during initial implementation.

Declaring victory or failure at month three misses the point entirely. Operations managers know that real operational excellence takes time to build. They’d rather have leadership patience and sustained support than premature pressure for ROI numbers.

What Operations Managers Actually Need From Leadership

This isn’t a list of complaints. It’s a request for partnership.

Operations managers want ERP implementations to succeed. They’re the ones who will benefit most from streamlined processes, better data, and systems that actually support how work gets done. They’re also the ones who absorb the impact when implementations struggle.

What would help:

Trust operational expertise. When the operations team says a timeline is unrealistic or a feature is essential, that assessment comes from direct knowledge of how the business actually runs. Dismissing those concerns because they’re inconvenient creates problems that surface later at higher cost.

Maintain visible commitment. ERP implementations are marathons. When leadership attention drifts to other priorities, momentum dies. Regular check-ins, continued resource allocation, and public reinforcement that this project matters all signal that the organization is serious.

Expect messiness. No implementation goes according to plan. Budgets shift, timelines slip, and unexpected problems emerge. That’s normal. The question is whether leadership treats these as learning opportunities or as failures to be punished.

Invest in people, not just software. The technology is the easy part. Getting hundreds of employees to change how they work is the hard part. Budget and plan accordingly.

Take the long view. The value of ERP isn’t in the go-live celebration. It’s in the years of improved operations that follow when the system is adopted, optimized, and leveraged for competitive advantage.

The Conversation Worth Having

ERP implementation represents one of the largest operational investments most companies make. Getting it right requires alignment between strategic vision and operational reality.

That alignment doesn’t happen automatically. It requires honest conversation between executives who set direction and operations managers who understand what execution actually demands.

The gap between these perspectives isn’t a problem to eliminate. It’s a tension to manage productively. CEOs should push for efficiency and accountability. Operations managers should advocate for realism and adequate resources. The best outcomes emerge when both perspectives are heard and balanced.

If you’re an operations manager preparing to make the case for ERP investment, or navigating an implementation that’s hitting turbulence, know that your concerns are valid. The challenges you’re experiencing are common across organizations of all sizes and industries.

And if you’re a CEO reading this, consider it an invitation. Ask your operations team what they wish you understood. Listen to the answer. The success of your ERP investment might depend on that conversation more than any technical decision you’ll make.