You think ERP success is decided at go-live. It is actually decided the day after.

Most executive teams are told to focus on delivery—timeline, budget, go-live readiness.
That creates a false finish line.

Because the moment the system goes live, a quieter, more important question emerges:

Who will make this system better every month from now on?

If that question is not answered clearly, the investment starts to decay immediately.
If go-live is success, why do most ERP benefits never fully materialise?

It feels logical to hand ERP to IT. That is where the trap begins.

The reasoning is simple and widely accepted:

• ERP is a system
• IT owns systems
• Therefore, IT owns ERP

From an operational standpoint, this makes sense. IT ensures:

• System uptime
• Security and access
• Technical support
• Upgrades

Everything appears controlled.

But this is surface-level thinking. It assumes ERP is primarily a technology asset.
It is not.

ERP is how your organisation operates, makes decisions, and controls performance.
 If ERP defines how your business runs, why would ownership sit outside the business?

The system works. The business quietly stops using it properly.

What unfolds post go-live is predictable:

• Reports exist, but teams export data into Excel
• Processes are defined, but workarounds emerge
• Data is captured, but not trusted
• Features are available, but not used

Example:

A payroll and HR system is implemented to streamline employee lifecycle management.
Six months later:

• Managers still track approvals via email
• HR builds shadow trackers outside the system
• Payroll corrections increase due to poor upstream data

Nothing is “broken.”
But the system is no longer shaping behaviour.

Another example:

Finance implements automated procurement workflows.
Without ongoing optimisation:

• Approval chains become bottlenecks
• Users bypass controls
• Spend visibility reduces

The ERP becomes a passive tool, not an active control mechanism.
If the system is live but decisions are still made outside it, what exactly did you implement?

The real issue is not capability of the system. It is absence of ownership- Who Owns ERP After Go-Live?

This happens because of a structural gap:

IT teams are designed to:

• Maintain stability
• Manage access
• Apply patches and upgrades

They are not designed to:

• Redesign business processes
• Improve workflows across departments
• Drive behavioural adoption
• Ensure the system is used optimally

So what happens?

The ERP is maintained, but not evolved.

No one is accountable for:

• Improving how work flows through the system
• Ensuring users adopt best practice
• Rolling out new capabilities
• Extracting increasing value over time

This is where value is lost—quietly, structurally, and predictably.
If no one owns improvement, why would the system ever get better?

The cost is not visible in budgets. It shows up in missed potential.

This is not an implementation failure.
It is a value erosion problem.

• 30–60% of ERP capability remains unused
• Manual work persists under a digital façade
• Decision-making remains fragmented
• ROI plateaus early

From an executive perspective:

You funded transformation.
You received system stabilisation.

The organisation adapts just enough to function—but not enough to improve.

Over time, this creates a false narrative:
“The system is not delivering what we expected.”

In reality:
The organisation never structured itself to extract value from it.
If you are not actively increasing value from ERP, are you slowly losing it?

The shift: from system ownership to capability ownership.

ERP should not be treated as a system to support.
It must be treated as a capability to continuously develop.

This requires a different construct:

A Capability Development Function

Not a project team.
Not IT support.
But a business-aligned function responsible for making ERP better over time.

This function sits between:

• Business operations
• Technology platform

Its purpose is simple but critical:

Ensure the organisation operates optimally through the ERP.

Think of it this way:

• IT keeps the system running
• The Capability Function ensures the business runs better because of the system

Without this, ERP becomes infrastructure.
With this, ERP becomes a performance engine.
If ERP is meant to improve your organisation, who is actively improving the ERP?

What this Capability Development Function actually does (in practical terms)

This is not theoretical. It is operational and measurable.

1. Process Optimisation

• Continuously review and refine end-to-end workflows (e.g. procure-to-pay, hire-to-retire)
• Remove inefficiencies, bottlenecks, and workarounds
• Align system usage with best-practice processes

Example:
Reducing a 7-step approval process to 3 without losing control—improving speed and compliance.

2. Adoption and Training

• Develop structured training materials aligned to real roles
• Monitor system usage and identify gaps
• Reinforce correct behaviours through targeted interventions

Example:
Instead of one-off training at go-live, introducing quarterly refreshers based on actual usage patterns.

3. Continuous Improvement

• Maintain a backlog of enhancements
• Prioritise improvements based on business impact
• Roll out new features in controlled cycles

Example:
Activating unused ERP modules (e.g. budgeting, asset tracking) in phases to unlock additional value.

4. Value Realisation

• Define measurable outcomes (e.g. reduced cycle times, improved data accuracy)
• Track benefits over time
• Report value back to executives

Example:
Demonstrating that invoice processing time reduced by 40% due to system-driven workflow improvements.

5. Governance and Proper Use

• Define and enforce standards for system usage
• Ensure data integrity and compliance
• Prevent regression into manual or inconsistent practices

6. Data Quality and Reporting

• Ensure data is accurate, complete, and trusted
• Build meaningful dashboards that drive decisions
• Eliminate shadow reporting outside the ERP

7. Enhancement and Feature Rollout

• Introduce new system capabilities to the business
• Align releases with operational priorities
• Ensure adoption of new functionality

This function is the difference between:

• A system that exists
• A system that improves the organisation every quarter

If no one is driving these activities, how will your ERP ever move beyond where it is today?

The practical move executives need to make

ERP does not fail because of poor implementation.
It underperforms because of weak ownership after go-live.

The organisations that extract value are not those who implemented best.
They are the ones who designed how the system would be continuously improved.

You have already paid for the system—are you willing to invest in making it actually deliver?