← All executive briefings

Recovering an amber or red S/4HANA programme without losing another year

When go-live dates slip repeatedly and steering meetings stop producing straight answers, replacing people or adding headcount rarely fixes the root cause. Here is how to isolate the real blockers in three weeks.

Executive takeaway

Troubled SAP programmes almost always stall across four unresolved fault lines: unowned commercial policy, global-versus-local template fights, broken cross-module data handoffs, and custom code masking business indecision.

When a multi-country SAP transformation slips from green to amber, the first instinct inside most steering committees is to ask the delivery team for a revised plan and add resource to late workstreams. Six months later, the new go-live date slips again.

After nearly thirty years inside complex SAP programmes, the pattern behind stalled rollouts is remarkably consistent. Programmes rarely stall because engineers cannot configure SAP S/4HANA. They stall because technical workstreams are asked to solve commercial and operating-model disagreements that leadership has not yet settled.

Four fault lines to check in the first fifteen days

Before re-baselining any schedule or renegotiating statements of work, an effective recovery diagnostic looks straight past RAG status slides to inspect four concrete fault lines:

  1. Unresolved finance and commercial policy. Are group reporting segments, intercompany pricing rules, and revenue or cost recognition policies written down unambiguously, or are functional consultants guessing inside workshops?
  2. Global template versus local autonomy. Have regional managing directors genuinely signed up to standard processes, or is every country re-litigating the template through change requests?
  3. Cross-workstream handoffs and master data. Finance, procurement, manufacturing, and order-to-cash often report 90 percent completion inside their own silos while end-to-end integration tests fail on customer, material, or profit-centre data.
  4. Custom code hiding indecision. When two business units cannot agree on one standard workflow, teams frequently commission custom ABAP extensions so both sides keep their legacy habit. Scope swells and testing grinds to a halt.

Adding headcount to an unaligned architecture only produces rework faster. Recovery starts by restoring a single source of architectural truth.

Stabilising without blowing up relationships

A common mistake in programme turnarounds is treating recovery as an audit exercise aimed at assigning blame between internal IT and the system integrator. Defensive teams hide problems, which delays recovery further.

A productive recovery lead sits calmly between the executive sponsor, regional business heads, programme director, and system integrator. By translating technical deadlocks into plain commercial options with explicit cost and timeline consequences, the steering committee can make five or six overdue decisions in a fortnight. Once those decisions hold, delivery partners gain the clarity they need to build cleanly and close out testing.

Confidential principal inquiry

Facing a similar question on your SAP programme? Speak directly with Ambaji Kodam.

Whether you are shaping an S/4HANA business case, reinforcing a delivery team, or looking for calm leadership on a stalled rollout, reach out directly in confidence.

Ambaji Kodam·akodam@sapphire-di.com·+44 (0) 791-025-8658·London, UK