A 12-Year Rolling Horizon defines the long-term business destination.
A 3-Year Picture translates that destination into the next major operational plateau.
But an ERP project cannot be executed from strategic ambition alone.
It needs immediate business priorities.
It needs this year’s targets.
It needs this year’s constraints.
It needs this year’s projects, resources, budgets, process improvements, and leadership decisions.
This is where the 1-Year Plan becomes essential.
The 1-Year Plan converts the strategic ambition of the 3-Year Picture into the concrete execution priorities the business must deliver over the next 12 months.
For an ERP implementation, this connection is critical.
ERP scope should never be built from a random compilation of departmental requests.
It must be shaped, filtered, and constrained by the business priorities that matter most this year.
The Problem ERP Projects Often Face
In many ERP implementations, the project team starts collecting technical requirements before the business has clearly defined its annual execution priorities.
Without an anchor, departments arrive at scoping workshops with long, unfiltered wish lists.
- Finance wants stronger internal controls and a faster month-end close.
- Sales wants rapid quotation engines and mobile order processing.
- Procurement wants automated vendor evaluations and approval visibility.
- Warehouse wants real-time inventory accuracy and optimized picking paths.
- Production wants advanced scheduling tools and granular cost visibility.
- Leadership wants executive dashboards, real-time KPIs, and predictive reporting.
All of these needs may be completely valid on their own.
But without a clear 1-Year Plan, the project team has no structural mechanism to decide which requirements are truly urgent, which should be phased for later, and which are simply legacy operational preferences.
The result is entirely predictable:
- ERP scope continually expands.
- Departmental priorities conflict.
- Design decisions slow down to a crawl.
- Customization requests skyrocket.
The implementation team remains incredibly busy, but actual business value becomes harder to measure. The core issue is not that the company lacks needs; the issue is that those needs are completely disconnected from a unified annual execution plan.
The 18-Month Implementation Paradox
A common objection raised by leadership teams is a timeline mismatch:
"If our ERP implementation is slated to take 18 months, why should this year's 1-Year Plan dictate the software's scope?"
This is the Implementation Paradox. Leaders mistakenly believe that because a system won't go live until next year, this year's operational pressures are irrelevant to the IT project.
The reality is that an 18-month implementation is not a monolithic block of waiting; it is 18 months of thousands of rapid design decisions, configuration choices, data-cleansing sprints, and process blueprints. What you design this year dictates what you can execute next year.
If your current 1-Year Plan emphasizes stabilizing a fractured supply chain to protect eroding margins, then the first 6 months of your 18-month blueprint must aggressively focus on standardizing procurement workflows, fixing the item master, and securing supplier data.
The 1-Year Plan does not look at what the ERP will output tomorrow morning; it dictates how the implementation team sequences and prioritizes the build today. It ensures that the heavy lifting of the project matches the immediate survival and growth needs of the business.
Why the 1-Year Plan Matters
The 1-Year Plan matters because it defines what the company must execute right now.
While the 12-Year Rolling Horizon provides long-term direction and the 3-Year Picture defines the mid-term stage, the 1-Year Plan answers the highly practical execution question:
What must we accomplish this fiscal year to stay on track toward our 3-Year Picture?
An effective annual plan explicitly outlines:
- Revenue, profit, and cash flow targets.
- Budget and expense management priorities.
- Hiring, talent acquisition, and restructuring plans.
- Core operational improvement initiatives and capacity targets.
- Procurement savings and strategic vendor performance goals.
- Data cleanup, migration readiness, and governance activities.
These immediate operational milestones must directly dictate ERP scope.
If the company’s 1-Year Plan emphasizes reducing month-end close time from fifteen days to four, the initial ERP scope must heavily prioritize financial process discipline, clean data structures, and automated reporting.
If the 1-Year Plan demands an immediate increase in inventory turns, the ERP scope must prioritize the item master cleanup, warehouse layout design, cycle counting functionality, and receiving discipline.
If the 1-Year Plan targets aggressive sales scaling, the ERP scope must prioritize customer masters, pricing engines, credit check automation, and order-to-cash visibility.
ERP scope becomes stronger, leaner, and more effective when it is inextricably tied to what the business must execute this year.
The Critical Distinction: Scope Filter vs. System Data
To deploy this framework successfully, leadership must understand a crucial difference. There is a vast distinction between entering annual targets into a system, and using annual targets to design the system.
- What this is NOT: This is not about the data entry task of typing this year's $10M revenue budget or cash flow targets into the ERP general ledger. That is standard financial administrative input.
- What this IS: This is about using those macro targets as an executive filter to determine which software capabilities get built.
|
The 1-Year Financial Target |
The Resulting ERP Scope Priority (The Filter) |
|
Achieve a $10M Revenue Target |
The sales team cannot afford a clumsy, 12-step order entry process that causes customer churn. ERP scope must prioritize a streamlined, 3-click order checkout design. |
|
Protect Cash Flow & Reduce DSO |
The collections team needs immediate visibility. ERP scope must prioritize automated credit-limit holds and rigid, system-enforced aging alerts over nice-to-have features. |
|
Reduce Operational Overhead by 15% |
Procurement cannot waste hours chasing physical signatures. ERP scope must prioritize automated, tiered electronic approval workflows. |
The 1-Year Plan tells you exactly where the business is bleeding or growing right now, so you can decide which parts of the software must be built to perfection first.
Annual Priorities Should Filter ERP Requirements
A weak ERP requirement says:
“We need this software feature because our department has always done it this way.”
A strong ERP requirement says:
“We need this systemic capability because it directly supports our annual business priority of reducing order lead times.”
That distinction changes everything.
The 1-Year Plan gives the ERP executive sponsor a practical filter to evaluate every single request. Every proposed requirement should be rigorously tested against targeted questions:
- Does this capability directly support this year’s revenue or cost targets?
- Does this eliminate a priority operational bottleneck identified in our annual plan?
- Does this improve a core process that leadership committed to fixing this year?
- Does this generate a metric for a critical KPI or company scorecard?
- Does this requirement belong in the current go-live phase, or can it wait?
Without this filter, ERP scope degenerates into an unmanageable collection of departmental preferences. With this filter, ERP scope becomes a highly focused business execution tool.
The Risk of ERP Scope Without a 1-Year Plan
When ERP scope is detached from a 1-Year Plan, the project quickly becomes overloaded under its own weight.
Every department pushes its own agenda, every process issue feels incredibly urgent, every report seems vital, and every exception becomes a mandatory software requirement.
This creates compounding risks for the organization:
- Timeline Inflation: The project becomes too massive to deliver within the target timeframe.
- Budget Creep: Implementation costs soar as consultants build complex workarounds for low-value requests.
- Diluted Focus: The project team burns valuable energy on minor features while critical business priorities are neglected.
- Complicated Adoption: Users are overwhelmed by a bloated system filled with unnecessary steps at go-live.
Ultimately, leadership struggles to articulate or prove exactly what measurable value the ERP investment actually delivered to the bottom line. ERP scope must never be defined by the volume of requests; it must be defined by strategic business priority.
The 1-Year Plan Makes ERP Phasing Practical
Not everything needs to be delivered on Day One. A successful ERP implementation separates what is required immediately to run the business from what can be enhanced during post-stabilization.
The 1-Year Plan provides the objective criteria to make these phasing distinctions clear:
[Phase 1: Current 1-Year Plan] ➔ [Phase 2: Post-Stabilization] ➔ [Future 3-Year Loop]
(Immediate Core Scope) (Continuous Improvement) (Advanced Innovation)
This structural division prevents the project from becoming unnecessarily heavy, while protecting the business from delaying non-negotiable capabilities. The 1-Year Plan does not shrink the ultimate value of the ERP—it focuses it where it can generate immediate returns.
Connecting Budget to Business Value
ERP implementations represent a substantial corporate investment across multiple categories:
- Software licenses and cloud subscriptions.
- External implementation partner and advisory services.
- Internal resource backfills and dedicated project teams.
- Data cleansing, migration, and integration work.
- Change management, organizational training, and user adoption.
The 1-Year Plan justifies this heavy capital and operational expenditure by directly linking the project scope to immediate business results.
When leadership can clearly state, "We are investing in these specific ERP capabilities because they unlock the cost-reductions outlined in our annual targets," the business case becomes ironclad. ERP is no longer viewed as an expensive IT tax. It becomes part of the company's execution budget—a direct tool to deliver revenue, operational discipline, and performance visibility.
Improving Governance and Accountability
The 1-Year Plan injects much-needed clarity into project ownership. ERP implementations frequently stall when business responsibilities are vague or poorly defined.
By aligning scope with annual business priorities, ownership naturally falls into place:
- Each annual operational priority already has a designated business owner.
- Each critical process improvement has a leader responsible for its execution.
- Each data cleanup effort maps directly to a department head’s annual goals.
When the ERP scope mirrors the 1-Year Plan, the project team knows exactly who must participate in workshops, who has the authority to make design decisions, who must validate the data, and who must sign off on the final configuration. It minimizes delays, drives active business participation, and strengthens governance because people understand exactly how the new system helps them achieve their real-world annual bonuses and targets.
What Leaders Must Define Before Finalizing Scope
Before an organization signs off on its final ERP blueprint, leadership must explicitly align on their immediate annual operational priorities. They must clearly answer:
- What specific revenue and profitability targets must we achieve this year?
- Which operational bottlenecks are entirely non-negotiable to fix over the next 12 months?
- Which core data sets must be completely cleansed and standardized before we migrate?
- Which key performance indicators (KPIs) must leadership be able to trust implicitly?
- Which internal controls, approval matrices, and compliance factors must be strengthened?
- Which specific ERP capabilities are absolutely required right now to support this year’s execution?
Answering these questions translates an abstract corporate strategy into a practical, highly disciplined ERP scope.
The Joraid Perspective
At Joraid Consulting, we believe that ERP scope should always be driven by business execution priorities, never by departmental wish lists.
The 12-Year Rolling Horizon defines your ultimate long-term destination. The 3-Year Picture establishes your next major operational plateau. But the 1-Year Plan defines exactly what your team must execute today.
An ERP project must align with all three, but the 1-Year Plan is where the system becomes immediately practical. It anchors the implementation in current business realities, helps sponsors confidently manage scope, enables consultants to design around actual value, and allows end-users to understand exactly why process changes are happening now. When your ERP scope is anchored to your 1-Year Plan, the project transforms from a technology installation into a focused engine for business growth.
Final Thought
An ERP scope should never be an aggregation of departmental software requests. It must be a direct architectural reflection of the business priorities the company is committed to executing this year.
The 12-Year Rolling Horizon defines where you are going.
The 3-Year Picture defines the next stage.
The 1-Year Plan defines what must happen now.
Before you finalize your project scope, ask your leadership team one vital question:
Which specific annual priorities must this ERP help us execute this year?
Because an ERP system delivers its highest return on investment when it is purpose-built to support the actual work the business must complete today.
ERP from Vision to Execution
Weekly Monday Series | Article 10 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.
- Previous Article: The 3-Year Picture: Turning Strategic Ambition into ERP Direction
- Next Monday’s Article: Corporate Values: The Missing Input in ERP Design and Change Management