By Vito Evko
Over the years, I’ve been in hundreds of ERP conversations.
Some start with excitement.
Some start with frustration.
Most start with software.
But here’s something I’ve learned after 25+ years in this business:
ERP implementations don’t fail because of software.
They fail because of people.
And not in the way you might think.
It’s Not About Resistance, It’s About Uncertainty
When companies decide to implement a new ERP system the focus naturally goes to features:
- Does it handle multi-entity?
- Can it manage inventory more efficiently?
- What does the dashboard look like?
- How does it integrate with payroll or CRM?
Those are important questions.
But inside the organization, something else is happening.
People are asking:
- Will my job change?
- Will I still be relevant?
- Am I going to look incompetent while learning this?
- Is this going to make my life easier or harder?
Most implementation plans never address those questions directly.
Process Is Technical. Change Is Human.
From a project management standpoint, ERP implementations are structured and logical:
- Discovery
- Design
- Configuration
- Testing
- Training
- Go-Live
On paper, it’s clean.
In reality, it’s emotional.
I’ve seen projects where:
- The accounting team quietly reverts to spreadsheets.
- Operations avoids entering data because it feels slower.
- Managers hesitate to enforce new workflows.
- Leadership assumes adoption will “just happen.”
It doesn’t.
Change has to be led.
The Real Risk in ERP Projects
The biggest risk isn’t technical failure.
It’s partial adoption.
That’s when:
- The system technically works…
- Reports technically run…
- But the organization never fully commits.
And when that happens, ROI quietly disappears.
You don’t get transformation.
You get an expensive accounting system.
What Successful Companies Do Differently
The companies that truly succeed with ERP implementations do three things well:
- They Assign Ownership
Not just an “IT person.”
A true internal champion who:
- Understands the business
- Has authority
- Believes in the change
- They Invest in Training (More Than Once)
Training isn’t a one-day event.
It’s:
- Pre-go-live exposure
- Hands-on testing
- Reinforcement after go-live
- Follow-up sessions once real data is flowing
- Leadership Stays Engaged
When leadership treats ERP as “an accounting project,” adoption stalls.
When leadership treats ERP as a business transformation initiative, everything changes.
Tone flows from the top.
Why This Matters More Today
Modern ERP systems are incredibly powerful.
Cloud platforms like Acumatica and Sage Intacct can:
- Automate approvals
- Eliminate redundant entry
- Deliver real-time dashboards
- Improve cash visibility
- Tighten inventory controls
But none of that happens without people changing behavior.
Software doesn’t transform companies.
People do.
A Fireside Reality Check
When we start an ERP engagement at SOS Consulting, we spend as much time talking about roles, expectations, and communication as we do about configuration.
Because experience has taught us:
If you get the people part right,
the technology part becomes manageable.
If you ignore the people part,
no amount of customization will save the project.
Final Thought
The most overlooked part of ERP implementation isn’t a feature, a module, or an integration.
It’s the human element.
If you’re considering an ERP project, or you’re in the middle of one, ask yourself:
- Have we clearly communicated the “why”?
- Do our team members understand what’s changing?
- Have we invested enough in training and reinforcement?
- Is leadership visibly committed?
Because in the end, ERP success isn’t a technical achievement.
It’s a leadership one.
in your business right now?
