"This isn't what we approved."

Most executives who have lived through a large ERP program remember the moment that thought arrived. The project in front of them stopped resembling the project they originally funded. What had been described as a finance upgrade, a reporting initiative, a platform refresh, or a like-for-like system replacement had quietly become something categorically different. The budget was still the same budget. The timeline was still the original timeline. The governance was still treating it as the original project.

The transformation had already happened. Nobody had said so out loud.

The Governance Condition

Organizations do not typically approve transformations. They approve components. Each request is reasonable, contained, and justifiable in isolation. Then something shifts. More stakeholders appear. More requirements surface. More departments identify dependencies not visible at the point of approval. The component expands. The governance does not.

In one global consumer products business, the program began as a finance module upgrade. Eighteen months later it had expanded to include supply chain, procurement, HR, and a data migration from three legacy systems. The governance structure had been constituted to oversee a finance upgrade. It never formally redesigned itself to govern the transformation that had replaced it. The steering committee continued meeting monthly to review milestones of a program that no longer existed in the form it had been constituted to govern.

In a multi-site manufacturer in Central Europe, what was described internally as a cloud migration had by the point of go-live touched fourteen countries, required the redesign of sixteen core business processes, and created integration dependencies with four external platforms not contemplated at the point of approval. The original business case was never revised. The governance structure was never formally reconstituted.

The systems integrator, in most cases, does not surface this change. Their commercial interest is in the program as contracted. Expanding the scope of the governance conversation is not within their mandate. The category change is managed incrementally by the delivery structure until it becomes a governance event.

Governance Pattern: The Transformation Trap

Observed when:

  • The number of stakeholders involved has materially exceeded the number involved at the point of approval
  • Business units not part of the original scope are now central to delivery
  • The complexity of the work has changed category since the business case was written, but the business case has not been revised
  • The governance structure was designed for a project and has not been redesigned for the transformation it is now governing
  • The executive sponsor's role has grown significantly beyond what was described at the point of appointment

Commercial consequence:

A program governed by a structure designed for a different level of complexity, producing decisions too slow and reporting too narrow for what the program has become. Stakeholder conflict that is structural rather than interpersonal.

If This Feels Familiar
  • The program's original scope document no longer accurately describes what is being delivered.
  • Departments not part of the original approval are now deeply involved in delivery.
  • The steering committee is making decisions about a program materially larger than the one it was constituted to govern.
  • When you compare the program as it exists today to the program that was approved, you would not recognize one from the other.

Board Questions

1.At what point does a project stop being an upgrade and become a transformation? Has that conversation happened in this program?
2.Which elements of the current program were not part of the original approval? Have those additions been formally assessed and approved?
3.Is the governance structure designed for the program as it exists today, or for the program as it was originally described?
4.Has the business case been revised to reflect what the program now is? If not, what is the board governing against?
5.Who, independently of the delivery chain, is telling the board that the program has changed category?

Governance Intervention

Governance Design Review. When a program changes category, its governance structure must change with it. An examination of whether existing governance is designed for the program that exists or the program that was originally approved.

Transformation Alignment and Readiness Review. A structured assessment of whether the organization is prepared for the program it is now running rather than the one it originally approved.

Executive Alignment Review. When the nature of a program has changed, executive alignment must be re-established against what the program now is.

TRC Solutions provides independent governance for SAP and ERP transformation programs. The Governance Engine is the institutional framework through which TRC carries that accountability.