Many ERP projects do not struggle because the software is weak. They struggle because the business expects the ERP system to create clarity that leadership has not yet defined.
This is one of the most common patterns I have seen in ERP implementations. A company starts the project with strong expectations:
- "We need better reporting."
- "We need standardized processes."
- "We need more control."
- "We need better visibility."
- "We need the system to force accountability."
All of these expectations are valid.
But when leadership relies on a software purchase to create this clarity, the organization can fall into a dangerous and costly cycle.
Throughout my 35 years in ERP development and implementation, I have seen this pattern repeat many times: companies invest millions of dollars in a new ERP system, only to replace it again within 7 to 10 years.
In many cases, they move from one major tier-one ERP platform to another, expecting the new system to solve problems that were never caused by the software alone.
The deeper issue is often the same: the ERP was implemented without a clear business foundation - Vision, operating model, process ownership, decision authority, KPI definitions, reporting needs, and accountability.
When this foundation is unclear, changing the software does not solve the problem. It simply gives the business a new system where the same confusion appears again.
The Problem ERP Often Exposes
In one implementation, a company expected the new ERP system to automatically standardize operations and improve reporting across departments. At the beginning, everyone agreed with the goal. But once the project moved into requirements and process workshops, the real structural friction appeared. Different departments were using the identical business terms, but they meant entirely different things.
For example, everyone talked about "order processing," but each department viewed it through a completely disconnected lens:
- Sales saw order processing as a customer commitment and delivery promise.
- Finance saw it as credit approval, invoicing, and revenue control.
- Operations saw it as fulfillment planning.
- Warehouse saw it as picking, packing, and shipping.
- Customer Service saw it as communication and issue resolution.
So, when the ERP implementation team started asking practical configuration questions, the discussion hit an immediate wall:
- Who owns the end-to-end order process?
- When is an order officially approved?
- Who can change the delivery date?
- Who can override a credit hold?
- Which department owns the customer promise?
- Which report should leadership trust?
- Which KPI matters most: order entry speed, fulfillment accuracy, invoice timing, delivery performance, or customer satisfaction?
The problem was not the ERP software. The problem was that the business had not yet agreed on its core operating model.
The ERP project did not create the confusion. It exposed the confusion.
Why This Matters to ERP Sponsors
This is where ERP sponsors - CFOs, CIOs, COOs, and business leaders - need to be exceptionally careful. If business clarity is missing before the implementation begins, the project will inevitably suffer severe downstream symptoms:
- Requirements balloon into a long, unmanageable wish list.
- Workshops devolve into department-by-department turf negotiations.
- Customization requests skyrocket to patch standard procedural gaps.
- Reports become mathematically impossible to define.
- Testing processes stall out due to conflicting user expectations.
- Decision-making slows to an expensive crawl.
- Users violently resist the system because they do not understand the process behind it.
The implementation team may appear to be struggling with "system design," but the deeper issue is almost always a lack of fundamental business alignment.
An ERP implementation is never just a technology exercise; it is a business design exercise. The system will inevitably force the business to make hard operational decisions that may have been actively avoided for years.
Requirements Are Only as Good as the Clarity Behind Them
Many organizations rush into requirements workshops far too quickly. They gather requests from departments, document current pain points, map out existing workflows, and immediately start designing the solution.
But if the business has not clarified its ultimate direction, ownership model, approval structure, and performance expectations, those requirements will not represent the future business. They will only represent today’s habits. And not every current habit deserves to be automated.
- Some processes need to be completely re-engineered.
- Some historical approval layers need to be permanently removed.
- Some strict internal controls need to be introduced.
- Some legacy reports need to be thrown out and redesigned.
- Some structural responsibilities need to shift from one role to another.
- Some operational decisions need to be permanently elevated to leadership.
This is why ERP requirements should never be treated as a simple checklist of user requests. They must be treated as architectural business design decisions.
Vision Is Not Just a Statement
In our framework for Entrepreneurial Transformation, Vision is not a slogan, a mission statement, or an inspirational sentence on the corporate website. It is a highly detailed, mathematically measurable blueprint of the company that the executive team intends to construct over a 12-Year Rolling Horizon.
It describes the future scale of the business in highly practical parameters:
- Expected revenue targets and annualized transaction volumes.
- Operational scale, headcount density, and organizational maturity.
- Geographic presence, regional facilities, and cross-border entities.
- Future product lines, service solutions, and market-ready infrastructure.
This matters because an ERP should never be designed around where the business sits today; it must be architected to sustain where the business is going.
To make this long-term horizon actionable, the enterprise manages this vision through Continuous 3-Year Transformation Loops. Each loop translates the long-term vision into a concrete, immediate 3-Year Picture. From there, the 1-Year Plan turns that 3-year slice into immediate execution priorities: revenue targets, budgets, operational objectives, and milestones.
In simple terms: the 1-Year Plan executes the 3-Year Picture. The 3-Year Picture realizes the 12-Year Rolling Horizon. And your ERP must serve as the unbroken digital thread supporting this entire path from strategic direction to daily execution.
The Questions Leaders Must Answer First
Before allowing an implementation team to start ERP requirements workshops, leadership must align on several non-negotiable questions:
- What scale of enterprise are we trying to build over our 12-Year Rolling Horizon?
- What must the business realistically look like at the conclusion of our first 3-Year Transformation Loop?
- What must we execute flawlessly in the next 12 months to drive toward that 3-Year Picture?
- Which core operating processes must be completely standardized across the corporate group?
- Where do we intentionally allow operational flexibility by department, branch, or business unit?
- Who owns each end-to-end business process from data entry to financial reconciliation?
- Who possesses the explicit authority to approve, reject, override, or escalate key transactions?
- Which macro KPIs matter most to the executive steering committee?
- What precise scorecards must executives rely on immediately following go-live?
- What decisions should the ERP system strictly enforce, what should it escalate, and what should remain entirely with human judgment?
Answering these questions upfront is often the absolute boundary line between a clean, cost-effective ERP implementation and a painful, runaway failure.
ERP Should Connect Vision to Operations
A successful ERP system stops functioning as an isolated IT asset and transforms into the company's central business execution system. To achieve this, the project must form an unbroken, structural chain from high-level strategy to daily workflow execution:
- 12-Year Rolling Horizon informs the concrete 3-Year Picture.
- 3-Year Picture dictates the immediate 1-Year Plan.
- 1-Year Plan locks down current business priorities.
- Priorities drive optimized, standardized processes.
- Processes define clear software requirements.
- Requirements map directly to corporate roles and accountabilities.
- Roles establish workflow authority and system approvals.
- Authority embeds ironclad internal controls.
- Controls generate clean, real-time KPIs.
- KPIs feed executive scorecards.
- Scorecards back to highly informed, fast executive decision-making.
Why Clarity Reduces Cost and Risk
When business clarity is missing, implementation teams demand expensive software customization because they cannot agree on a standardized process. When clarity exists, technical design choices become instantly obvious.
By establishing absolute business clarity upfront, a project sponsor can:
- Eliminate unnecessary, high-risk customizations by forcing the business to align with standard software best practices.
- Avoid devastating configuration rework and architecture changes late in the project lifecycle.
- Focus user acceptance testing (UAT) on the workflows that actually drive enterprise value.
- Make user training practical and meaningful because workflows are tied to business roles rather than system clicks.
System adoption becomes natural because people understand not only how the software works, but why the process was engineered that way. Business clarity is not a pre-project "nice-to-have"—it is the single most powerful risk-reduction tool available to an enterprise.
The Joraid Perspective
At Joraid Consulting, we treat ERP implementation as a core mechanism of a broader business transformation. The software cannot, under any circumstances, be decoupled from corporate vision, organizational accountability, role definitions, process optimization, or performance management.
Our methodology ensures your technology stops operating as a static transaction database and starts acting as the operational engine driving your strategic roadmap. By executing through continuous 3-year loops against a 12-year rolling horizon, your teams understand true ownership, your business accurately measures performance, and your leaders gain total visibility into whether the company is moving in the right direction—all while maximizing the lifespan of your existing system architecture.
Final Thought
ERP does not create clarity. ERP requires clarity.
Before asking whether your technology stack is ready for a transformation, ask whether your leadership team is clear enough to guide it. The clearer the operational foundation, the stronger, faster, and more profitable the digital transformation.
ERP from Vision to Execution
Weekly Monday Series | Article 1 of 52
This article is part of a 52-week series exploring how Entrepreneurial Transformation, Business Transformation, and Digital Transformation work together to create successful ERP outcomes.
- Next Monday’s article: Why ERP Projects Fail Before Configuration Starts