It is common to see this pattern—across councils, organisations, and programs

It is common to see executives invest heavily in ERP initiatives with the expectation that clarity, control, and performance will follow.

The program is approved.
The system is implemented.
The reporting improves.

Yet, when observing how the organisation actually operates post go-live, a consistent pattern emerges:

• Numbers are still being validated before meetings
• Different leaders interpret the same data differently
• Risks surface late
• Decisions are delayed pending confirmation

Nothing appears broken.

But control is not where it should be.

This is not a system failure.
It is a standards failure.

1. What executives typically believe: ERP is not failing

Most ERP initiatives are framed as disciplined delivery exercises:

• Scope is defined
• Budget is controlled
• Timeline is tracked
• Vendors are managed

The underlying assumption:

If the system is implemented correctly, the organisation will perform better.

This assumption is reasonable.

It is also incomplete.

Because systems do not create clarity.
They reveal whether clarity has been designed.

2. What actually happens after go-live

Once the system is live:

• Data is integrated
• Reports are standardised
• Dashboards are available

However, in practice:

• Finance is still asked to confirm figures
• Reports still require interpretation
• Issues still emerge reactively
• Decision-making speed does not materially improve

The result is consistent:

More information, but not more control.

This is where expectations and reality diverge.

3. The gap that was never defined

Across most ERP programs, one critical element is missing.

Executives are rarely asked to define:

• What must be visible at any point in time
• What decisions must be made without dependency
• What risks must be detected before escalation

Instead, the focus remains on:

• System capability
• Functional modules
• Reporting outputs

This creates a structural disconnect between:

• What is delivered
  and
• What is required at the executive level

This is the Executive Standard Gap

4. Making this visible in a real scenario

Before a Council or Board briefing

What effective executive control looks like:

A single view provides:

• Current financial position
• Forward forecast variance
• Capital program performance
• Workforce cost exposure
• Enterprise risk signals

No follow-up required.
No interpretation needed.

What is typically observed instead

Executives ask:

• “Are these numbers current?”
• “Has this been reconciled?”
• “Is there anything we should be aware of?”

Information is then provided through:

• Spreadsheets
• Static reports
• Verbal explanations

At that point, the role shifts:

• From decision-making → validation
• From steering → confirming

The system exists.

But institutional control does not.

5. Why this pattern persists

ERP programs are optimised for delivery:

• Vendors optimise for functionality
• Project teams optimise for go-live
• IT optimises for system stability

No one is explicitly accountable for defining:

What capability must exist at the executive level once the system is live?

As a result:

• Outputs are delivered
• Outcomes are diluted

6. What an executive standard actually looks like

A clear executive standard defines what must be visible and actionable without friction.

This includes:

• Real-time financial position
• Forward-looking financial risk
• Capital program performance across directorates
• Workforce cost and vacancy exposure
• Procurement commitments before spend is realised
• Asset risk and infrastructure backlog
• Service demand and escalation patterns
• Compliance exposure and audit signals

Not across multiple reports.
Not through interpretation.

In one coherent, reliable view.

7. What changes when the standard is clear

At the executive level

The shift is immediate:

• From validating numbers → to setting priorities
• From delayed decisions → to early intervention
• From relying on individuals → to relying on systems

The key question changes from:

“Is this accurate?”

to:

“What action should be taken?”

Across the organisation

• A single version of truth emerges
• Finance moves from reconciliation to forecasting
• Risks surface earlier
• Decision-making accelerates

The organisation transitions:

From managing uncertainty
to managing trade-offs.

8. The cost of not setting the standard

If the standard is not defined:

• Systems will still be implemented
• Reporting will still improve

But:

• Decisions remain slow
• Risk visibility remains delayed
• Dependency on individuals continues

The outcome is consistent:

A modern system operating with legacy behaviour.

9. Reframing the decision — with concrete examples

The decision is not:

• Which ERP platform to select
• Whether delivery will meet time and budget

Those are necessary, but insufficient.

The real decision is:

What decisions will become faster, earlier, and more reliable as a result of this investment?

Example 1 — Financial control

Typical approach:
“Provide monthly financial reports for review.”

Reframed standard:
“Executives can see real-time financial position and a 3-month forward forecast at any time.”

What this changes:

• Forecasting becomes embedded, not manual
• Finance shifts from reporting → advising
• Decisions on cost control happen earlier

Example 2 — Capital program oversight

Typical approach:
“Track project status through periodic updates.”

Reframed standard:
“Executives can identify which capital projects will miss milestones before delays become visible externally.”

What this changes:

• Project data is linked to financial impact
• Early warning indicators are built into the system
• Intervention occurs before escalation

Example 3 — Procurement control

Typical approach:
“Monitor expenditure against budget.”

Reframed standard:
“Executives can see committed spend before it is incurred.”

What this changes:

• Purchase orders become visible at commitment stage
• Budget control becomes proactive
• Financial surprises reduce significantly

Example 4 — Risk and compliance

Typical approach:
“Report risks through periodic governance forums.”

Reframed standard:
“Executives can see emerging risks 30–90 days before impact.”

What this changes:

• Risk signals are embedded in operational data
• Compliance issues are surfaced early
• Governance becomes predictive, not reactive

10. What needs to happen next — practical actions

1. Define the executive visibility standard

This must be explicit and documented.

Examples:

• “CEO can view real-time financial position and forward variance at any time”
• “Top enterprise risks are automatically surfaced weekly”
• “Capital delays are visible at least 4 weeks before milestone breach”

If this is not written, it will not be delivered.

2. Anchor system design to decisions

Every design choice must answer:

• What visibility does this create?
• What decision does this enable?

Examples:

• A dashboard that shows past spend only → low value
• A dashboard that shows forecast variance → decision-critical
• Procurement configuration that records invoices → reactive
• Procurement configuration that tracks commitments → proactive

3. Align ownership to outcomes

Clarity of ownership is essential.

Examples:

• Infrastructure team owns asset data accuracy
• People & Culture owns workforce data
• Finance owns financial structure and integrity

IT supports the system.

It does not own business truth.

4. Design ERP as a control system

ERP must actively enable control, not just reporting.

Example:

• Rising overtime cost appears in executive view
• Drill-down identifies department and vacancy gap
• Action is taken before budget impact escalates

This is system-enabled control.

5. Establish a capability function

ERP does not sustain itself post go-live.

A capability function must own:

• Process optimisation
• System utilisation
• Adoption
• Continuous improvement
• Value realisation

Example:

• Monitoring procurement cycle time post-implementation
• Tracking whether decision speed has improved
• Identifying underutilised system features

Without this, ERP value declines over time.

Final position

Across organisations, the pattern is consistent:

ERP systems are delivered.
Executive control is not.

The difference is not technology.

It is whether a clear executive standard was defined at the start.

When that standard is explicit:

• Design becomes aligned
• Delivery becomes purposeful
• Outcomes become measurable

ERP then becomes what it was intended to be:

Not a system implementation,
but the foundation of institutional clarity and control.