Most ERP programmes have a governance framework. A steering committee. A risk register. A change control process. And most of them are still failing. The problem is not the absence of governance. It is the quality of it.
What governance is not
Governance theatre is common in major transformations. A status reporting cadence where the programme reports RAG status to a committee that has no authority to change trajectory. A risk register that is maintained but never acted on. A change control process that approves everything because saying no to the business is political suicide.
None of that is governance. It is the appearance of governance. It creates the comfort of control without the substance of it.
Real governance is harder. It requires authority to be exercised. It requires uncomfortable conversations. It requires saying no when the data says the programme should say no.
Most organisations have not built the structures to make that possible.
What good governance actually looks like
Decision architecture
Good governance defines who has the authority to make which decisions, and that authority is exercised. Most programmes have RACI charts. Few have decision frameworks where the escalation paths are clear and actually used. When a decision hits an impasse, does it go to the programme board. To the sponsor. To the steering committee. Or does it sit unresolved because nobody knows who decides. The difference between a decision framework that is documented and one that is practiced is the difference between governance and theatre.
Independence of assurance
The people assessing programme health should not be the same people delivering the programme. The vendor has a commercial interest in reporting progress. The system integrator has a contractual interest in scope adherence. Neither is positioned to give the client an unfiltered view of what is actually happening. Good governance means having someone in the room whose job is to tell the truth about the programme, not to defend the programme. That independence matters.
Commercial alignment
Budget tracking is not commercial governance. Understanding whether the programme is still delivering value proportionate to the investment is. As a programme progresses, that balance shifts. Scope changes. Timelines extend. Market conditions evolve. Good governance connects delivery progress to commercial outcomes. It asks the hard question: given what we know now about cost, timeline, and benefit, should we continue. That is what commercial governance looks like.
Stakeholder accountability
Governance that only scrutinises the programme team is incomplete. The business must deliver its side. Data readiness. Process decisions. Change adoption. Testing resources. Testing availability. Good governance holds stakeholders to their commitments, not just the delivery team to theirs. When the business misses its obligations, governance escalates that risk just as it escalates a delivery slippage. That accountability balance is what separates real governance from one-way pressure.
Escalation discipline
Problems are escalated when they are still solvable, not when they have become crises. That requires a culture where raising a risk is rewarded. Programmes that punish the bearer of bad news end up learning about problems too late. Escalation discipline means the person closest to a problem has the confidence and safety to flag it up the chain before it metastasises. If your governance structure is still learning about critical risks in the steering committee meeting, escalation discipline is missing.
Why most governance fails
Governance fails for three reasons. First, it was designed by the vendor or system integrator. There is an inherent conflict of interest. A governance framework that holds the vendor to uncompromising delivery is less attractive to the client than one that creates flexibility. Governance structures designed by the people being governed lack teeth.
Second, governance was designed at the start and never adapted. Programmes mature. Early governance focuses on risk and feasibility. Later governance focuses on benefit realisation and value protection. Many frameworks do not evolve with the programme. They stay stuck in day-one thinking.
Third, the people in governance roles lack the programme experience to know what to ask. The programme manager knows the detail and can articulate a plausible narrative for any slippage. The business sponsor is accountable for outcomes but not immersed in delivery. The steering committee meets quarterly. Good governance requires someone in the room with enough transformation experience to know when a narrative is a plan and when it is a story. That person is rarely present.
The role of independent client-side leadership
This is where independent advisory and client-side delivery leadership fit into the governance picture. Not as an additional layer. As the mechanism that makes governance real rather than performative.
The client often lacks the transformation experience to know what good governance looks like. That is not a criticism. It is a structural reality. Major ERP and HRIS transformations happen once a decade for most organisations. When they do, the internal team is running the programme, not benchmarking governance models against other implementations. An independent person with 20+ major transformations across six platforms and six countries has seen what works and what does not. They know which risks matter and which are theatre.
Independent governance advisory serves two functions. First, it designs governance structures that actually work. Not governance frameworks that look good in a slide deck. Structures that are fit for purpose, adaptive, and calibrated to the actual risk profile of the programme.
Second, it operates within that governance structure. It brings pattern recognition into the room. It flags when the programme trajectory is off. It holds the vendor to its commitments and the business to theirs. It escalates the risks that matter and deprioritises the noise. It is the unfiltered voice that every major programme needs.
The four-party model describes how this works in practice. Client, vendor, system integrator, and the independent advisor. The client provides strategic direction. The vendor provides platform capability. The SI provides delivery execution. The independent advisor provides objective governance and client-side leadership. Each party has a defined role. None dominates the others. That balance is what makes the governance structure function.
Governance theatre versus real governance
Most ERP programmes have governance frameworks that are not working.
The problem is not the absence of governance.
It is the quality of it.
Good governance requires independent assurance, clear decision authority, commercial discipline, and the maturity to escalate risk early.
Very few programmes have all four.