Most stalled ERP programmes can be recovered but only if project owners and decision makers stop thinking in “IT fixes” and start leading a structured restart.
Reframe the problem as a business outcome issue
As the sponsor or owner, the first step is to move the conversation away from “the system is not working” to “which outcomes are not being delivered”.
- Ask your team: where is the business feeling pain today, month‑end close, inventory visibility, compliance, cash flow, customer lead times?
- Select 3–5 outcomes that matter to you as a leader (e.g. close on time, trust in numbers, fewer manual workarounds) and use these as anchors for the restart.
Without this clarity, every “fix” becomes another change request, not a transformation step.
Demand a focused diagnostic, not another workshop
A stalled ERP programme needs a short, sharp diagnostic you can stand behind.
- Instruct your partners and internal team to review four dimensions: Systems, People, Process, Data.
- Insist on a concise executive summary: top 5 causes of stalling, mapped directly to business impact and risk.
Your role is to decide priorities, not to debate every technical detail. You need a clear view of “what is blocking us” and “what it is costing”.
Reset vision, scope, and governance at your level
If the programme has stalled, it is often because the original vision either faded or was never specific enough.
- Re‑state, in one page, what ERP is meant to enable for your organisation over the next 12–18 months.
- Confirm what is in and out of the restart phase; remove nice‑to‑have scope that drains focus.
- Tighten governance: smaller, empowered steering group, clear decision rights, and a firm cadence for resolving conflicts.
When you show up with a clear vision and boundaries, the programme regains direction and confidence.
Structure the restart around the 4 Pillars
As an owner, your decisions should reinforce a simple structure your teams can execute against:
- Systems – Reduce complexity
- People – Put ownership back in the business
- Process – Stop copying the past
- Data – Treat it as a board‑level risk
Your sponsorship here signals that ERP is not just a technology refresh — it is how the organisation will run for the next decade.
Insist on a phased roadmap with real milestones
As decision makers, you should not accept vague timelines. Ask for a roadmap that you can manage and measure.
- Require 2–3 waves, each with:
Examples of the kind of milestones you should see:
- Wave 1: “Close by working day X with less than Y manual journals.”
- Wave 2: “80% of purchase orders raised and approved in ERP, not by email.”
- Wave 3: “Forecasting for key products driven from ERP data with agreed accuracy thresholds.”
Your role is to hold the line on these milestones and protect the team from unplanned scope that dilutes impact.
Make risk and course correction explicit
Stalled projects often got there because risks were downplayed. As the owner, you can change that tone.
- Ask to see a live risk and issue list at every steering meeting, with owners and due dates.
- Normalise course correction: if a design choice is not working, backing a change of direction early is stronger leadership than forcing a bad decision to “stay consistent”.
This is how you turn ERP from a cost overrun into a controlled, transparent programme you can explain to your board.
Lead the narrative — internally and externally
Finally, people watch your narrative. If leadership talks about “fixing IT”, the organisation will treat ERP as a system problem.
- Speak about ERP and AI as part of your transformation story: how they support strategy, resilience, and growth.
- Be visible when milestones are hit: communicate wins, reinforce the 4 Pillars, and show that the restart is delivering tangible value.
When project owners and decision makers lead with this level of clarity and discipline, a stalled ERP implementation stops being an embarrassing problem and becomes a turning point in the organisation’s digital transformation.
Need support on this journey? Contact us to get the right conversations going and recover your project
Enjoyed this article? Follow us on LinkedIn to never miss an update.