The ERP decision that matters most happens before you commit
Let’s paint the picture.
You are at the start of your ERP journey…
The board paper is approved. The target date for go-live has been announced based on all the organisations other priorities and budgets. A preferred platform is clear and the organisation expects delivery to begin. Then the evidence changes: process ownership is unclear, critical data is less reliable than assumed and the people needed to design the future are already committed elsewhere.
At that point, your ERP programme has not necessarily failed. But your organisation has lost room to respond honestly. Every new fact now competes with a public promise to your teams.
That is why ERP readiness should not be treated as a confidence score or a final checkpoint before mobilisation. It is an executive decision tool used while choices are still available and allows you to look at the programme holistically and not just through a technology lens. Its purpose is not to prove that the organisation is ready. Its purpose is to shape a commitment the organisation can support and expectations are managed on the journey you’re about to embark on.
So how can you stop yourself from jumping in? You complete a readiness assessment.
Committing to what’s ahead can help leaders remain honest throughout implementation
Before commitment, looking pragmatically at your organisation can change the plan. After commitment, the plan often starts to change the interpretation of the reality of your organisation. A missing process owner becomes “something to resolve in design”. Limited subject-matter capacity becomes “a resourcing action” for later. A disputed operating model becomes “stakeholder alignment”. The language softens while the underlying constraint and risk remains.
For the executive team, this matters because an ERP programme is not simply a technology purchase. It changes how decisions are made, how work moves across functions, how data is governed, how performance is understood and, in some cases, your team’s perspective of working in your organisation. Technology may enable that change, but it cannot settle competing business priorities or create organisational capacity.
The question before approval is therefore not: “Are we ready?” It is: “What must be true before we commit, what can we manage during delivery, and where are we still making an assumption?”
No organisation will be equally strong across strategy, governance, process, data, architecture, leadership, capacity, change capability and operational resilience. Nor does it need to be. Readiness is about understanding which weaknesses materially affect delivery and making deliberate choices on how you need to flex the plan.
This is where enthusiasm can be misleading. Leaders may support the ambition while the organisation remains unable to release the right people, resolve cross-functional decisions or absorb disruption. Support is useful, but evidence is more useful: named owners, agreed outcomes, visible dependencies, realistic availability and clear decision routes.
A readiness review should expose contradictions
The most valuable findings are rarely isolated problems at this stage of the programme. They are contradictions between expectations across teams. Finance may expect enterprise standardisation while business functions assume local variation will continue. Technology may plan to retire an interface or report that operations still depends heavily on. The business case may assume productivity benefits while functional leaders cannot release people for design, testing and adoption.
These are not communication issues to be managed later. They are choices about the transformation itself. A credible assessment brings them into the same conversation and tests stated confidence against true evidence of the organisation.
That means interviewing leaders and delivery teams across all levels, reviewing existing decisions and asking process, data and operational owners to test the assumptions beneath the plan. The goal is not a larger risk register, it is a sharper view of the decisions that will determine viability before you are in the deep end of delivery. This review can take time but it is worth it in the context of overall ERP deliveries which can often range between 18-24 months.
I’ve got a view of readiness, what’s next?
Test whether the organisation can decide and deliver. Governance is ready when it allows cross-functional decisions to be made at the pace delivery needs it to. A good time to test if your governance works is after completion of the readiness assessment, this will allow you to see if decisions can be made quickly in a lower stakes environment.
Turn every finding into one of three decisions:
- A pre-condition. Something must change before commitment. Examples include the absence of an accountable sponsor, no agreed business outcome or no viable route to essential capability. Proceeding would mean accepting a risk that cannot yet be sensibly mitigated.
- A managed risk. The programme can proceed because ownership, mitigation and consequences are clear. The risk should influence the plan, not sit beside it. That may mean additional capacity, stronger governance, a different sequence or a narrower initial scope.
- An uncertainty with a decision point. Some questions cannot be answered early. Executives should state what evidence is needed, who will decide and when the decision must be made. An explicit uncertainty is manageable, but an optimistic assumption disguised as fact is not.
Ensure governance is set up correctly:
- Confirm who owns end-to-end processes, who holds business design authority, how disagreements will be escalated and what evidence is required for consequential decisions. “The steering committee will decide” is not enough if its members have different assumptions about the outcome.
- Capacity deserves the same realism. Nominal allocation is not the same as availability. The people who understand critical processes, controls and data are usually carrying operational responsibilities and other change commitments. Test whether they can sustain design, validation, testing, adoption and post-go-live support, not merely attend workshops. Data and architecture should also be examined early. Executives do not need every technical answer before approving the programme. They do need a credible route to obtain those answers, accountable owners and visibility of the dependencies that could change scope, cost or sequence.
Why is this all so important?
The assessment earns its value when it changes the commitment. A readiness review that produces a red-amber-green dashboard but leaves the plan untouched is just assessment theatre. Every material finding should affect something tangible: scope, sequencing, governance, sourcing, investment, capacity or timing.
That may lead to a focused preparation phase before procurement even begins. It may support a phased roadmap, a narrower first release or earlier investment in data and process ownership. It may reveal that the proposed date is still achievable, but only if leaders stop treating scarce business capacity as free capacity. Most importantly it may help the organisation to understand the level of ownership required to deliver an ERP – a major risk is relying on system integrators to drive the plan and take control.
This is not bureaucracy before action. It is how the executive team preserves control before external expectations, contracts and sunk costs make honest adaptation harder.
Make the promise fit the organisation
ERP transformation readiness is not about removing every uncertainty. It is about making the important uncertainties visible while the organisation still has choices. The strongest commitment is not the boldest date or broadest scope. It is the promise leaders can actually stand behind because it reflects the real organisation: its strategy, processes, governance, data, capacity and ability to sustain change. This will not only increase the likelihood of success but will have a greater chance of improving buy-in across teams.
Assess before you commit. Then commit with enough clarity to make progress controlled, adaptable and credible.
So what do you do now? Get started by taking our free digital readiness assessment and understanding where your ERP transformation might need more certainty.
