Failed ERP programs rarely leave behind a single casualty.

They leave behind a trail. Transformation directors. CIOs. CFOs. Program sponsors. Sometimes entire leadership teams. Most were not removed because they lacked capability. Most were not removed because they made poor decisions. Many were removed because they carried accountability for outcomes they did not fully control.

The moment an executive says yes, they begin carrying risk. Usually far earlier than they realize. The business case creates risk. The sponsorship creates risk. The governance structure creates risk. The ERP system is often the least dangerous part of an ERP program.

The Governance Condition

ERP programs create accountability everywhere. What programs create far less reliably is authority. The authority to influence the outcome the accountability describes. The authority to surface a problem without political consequence. The authority to require decisions, not just request them.

A governance structure does not merely determine whether a program succeeds. It determines who carries the consequences when it does not.

In one multi-country European program, the CFO who owned the business case was held accountable for a budget variance that originated in assumptions the systems integrator had built into the original estimate. The CFO had accepted those assumptions at the point of approval because there was no independent mechanism to challenge them. By the time the variance surfaced, the CFO’s name was attached to a number that had never been realistic. The program recovered. The CFO did not stay to see it.

In a North American industrial transformation, the COO who had championed the business case left the organization at month eleven. Their replacement inherited accountability for a program they had not designed, a governance structure they had not built, and commercial commitments they had not approved. Within three months they had commissioned an independent review. The findings were structural, not human.

Accountability Without Authority

Accountability without authority is not accountability. It is exposure.

The transformation director is accountable for delivery but cannot approve scope changes without escalating to a sponsor who is unavailable to decide. The CFO owns the business case but cannot compel the business participation required to validate it. The program sponsor’s name is attached to outcomes they cannot directly govern.

Governance Pattern: The Accountability Illusion

Observed when:

  • Individuals are named as accountable for workstreams that depend on cooperation they cannot compel
  • Escalation paths exist on paper but do not produce timely decisions in practice
  • The transformation director reports to a sponsor not available to exercise the authority the transformation director lacks
  • Business unit leads are accountable for data quality or testing but have not been given the time or authority to deliver it
  • Accountability is assigned at program start and not reviewed as conditions change

Commercial consequence:

Decisions requiring authority are deferred, creating compounding delay. The people most informed about program risk are unable to surface it without political cost. When the program is in difficulty, accountability structures are invoked to explain the difficulty rather than resolve it.

If This Feels Familiar
  • There is a governance structure. Decisions still feel difficult to reach.
  • The transformation director is experienced. They look tired in a way not explained by workload alone.
  • Escalated items return from the sponsor without clear direction, or after a delay the program cannot absorb.
  • When asked who is accountable for a specific outcome, the answer is immediate. When asked whether that person has the authority to deliver it, the conversation becomes more complicated.

Board Questions

1.Which executives in this program are carrying responsibility for outcomes they are not empowered to influence?
2.If this program fails, who is most likely to pay the personal price? Does that person have the authority required to prevent it?
3.When an accountable party escalates a decision, how long does it take to receive clear direction?
4.Does the program sponsor have the availability and mandate to fulfill the governance function the program requires?
5.Is there an independent source of assessment that can tell the board whether accountability and authority are aligned in practice?

Governance Intervention

Governance Design Review. Before accountability is assigned, the authority required to fulfill each accountability should be explicitly mapped. A structural examination of whether the program has created the conditions in which accountable parties can act.

Decision Authority Framework. A documented, agreed hierarchy for program decisions that defines who can decide, at what threshold, and within what timeframe.

Executive Sponsorship Review. A formal examination of whether the program sponsor has the availability, mandate, and authority to fulfill the governance role the program requires.

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