ERP Governance Looks Fine on Paper. So Why Does It Still Fail?
Steering Committees are in place.
Reports are being produced.
Decisions are being recorded.
From the outside, governance appears structured and controlled.
Yet inside the program:
- Issues surface late
- Decisions feel reactive
- Value remains unclear
This disconnect is not caused by missing governance.
It is caused by something far more subtle:
No one has clearly defined what “good governance” actually means at an executive level.
The Assumption That Quietly Breaks Programs
Most organisations operate on a simple belief:
“If we have a Steering Committee, governance is working.”
So the focus becomes:
- Who attends
- What gets reported
- How often meetings occur
But one question is rarely asked:
What standard is this governance expected to operate to?
Without that standard, structure becomes a formality—not a control mechanism.
Where It Starts to Drift
When expectations are not clearly set from the top:
- Each member defines governance in their own way
- Questions become inconsistent
- Accountability becomes unclear
- Decisions default to what is easiest, not what is right
Over time:
- Governance becomes passive
- Conversations become safe
- Signals become diluted
Nothing appears broken.
But performance begins to erode.
The Missing Anchor: A Clear Executive Mandate
In high-performing ERP programs, governance does not evolve by chance.
It is defined upfront by the Project Sponsor or CEO.
They set:
- What governance is meant to achieve
- How decisions must be made
- What behaviours are expected
- What culture must exist in the room
This is not implied.
It is made explicit.
Because once the expectation is clear:
- Behaviour aligns
- Standards become consistent
- Decisions improve
Without this anchor, governance becomes dependent on personalities.
With it, governance becomes a system.
So What Good ERP Governance Actually Looks Like?
It is not about better reports.
It is not about more meetings.
It is about behaviour—driven by a clearly defined executive expectation.
Across high-performing programs, the same patterns consistently emerge.
They Don’t Look for Comfort. They Look for Truth.
Because the expectation is clear, members do not seek reassurance.
They ask:
- What are we missing?
- Where could this fail?
- What assumptions are we relying on?
Challenge is not seen as disruption.
It is seen as responsibility.
They Don’t Observe. They Own.
The mandate is clear:
Governance owns outcomes.
So members:
- Think beyond their function
- Take responsibility for cross-functional impacts
- Do not defer accountability back to the project team
Ownership becomes visible.
They Remove Ambiguity Early
Clarity is not left to the project team.
It is driven at the governance level:
- What does success look like?
- What matters most right now?
- What trade-offs are we making?
This reduces confusion before it becomes risk.
They Don’t Decide Blindly
There is an implicit understanding:
You cannot govern what you do not understand.
So members:
- Invest time in understanding the system and risks
- Ask deeper questions
- Build their own capability
Decision quality improves as a result.
They Show Up to Decide, Not Just Attend
Attendance is not the standard.
Contribution is.
Members are expected to:
- Engage actively
- Come prepared
- Make decisions
This creates pace and direction.
They Think Like Owners of the Whole Organisation
The expectation is clear:
Decisions must serve the organisation, not individual functions.
This changes behaviour:
- Less protection of silos
- More focus on end-to-end outcomes
Local optimisation reduces.
System-wide thinking improves.
They Make It Safe to Surface Reality
Culture is not left to chance.
It is set.
Members create an environment where:
- Issues are raised early
- Bad news is not suppressed
- Conversations are honest
This is where governance starts to work as intended.
They Care About Outcomes, Not Activity
Progress is not measured by:
- Tasks completed
- Milestones achieved
It is measured by:
- Business impact
- Value realised
- Capability improved
The focus shifts from motion to results.
They Go Beyond the Surface
They do not accept updates at face value.
They ask:
- Why is this happening?
- What is driving this risk?
- What assumptions are we relying on?
Understanding becomes the goal—not just answers.
They Listen, Challenge, and Then Decide
The room operates differently:
- People listen with intent
- Questions are deliberate
- Decisions are made with clarity
Discussion leads to outcomes—not more discussion.
What Changes When This Standard Exists
When the executive mandate is clear:
- Behaviour becomes consistent
- Decisions improve
- Risks surface earlier
- Alignment strengthens
- Execution stabilises
When it is not:
- Governance depends on individuals
- Standards drift
- Performance becomes unpredictable
The Shift Most Organisations Need to Make
ERP governance is often treated as:
- A structure
- A cadence
- A reporting mechanism
It needs to be understood as:
A system of behaviours—defined and enforced by executive expectation.
Where to Start
- Define the Mandate Clearly
- What is governance expected to achieve?
- What behaviours are required?
- Make It Explicit
- Do not assume alignment
- State expectations clearly
- Reset the Steering Committee
- Move from attendance → accountability
- Move from reporting → decision-making
- Reinforce the Standard
- Observe behaviours
- Challenge deviations
- Maintain consistency
Final Thought
Most ERP programs do not struggle because governance is missing.
They struggle because:
The standard for governance has never been clearly defined.
Once that standard is set,
everything else—
questions, decisions, behaviour, outcomes—
begins to change.
