Recovering a transformation across a GCC group

Updated 17 October 2026

A transformation across several entities can stall while every local team reports progress. Group management sees a common programme. Each business sees a different set of customers, systems and obligations.

In a GCC group, the recovery plan needs to reflect the actual countries, ownership arrangements and operating businesses involved. The label “GCC” provides a geographical starting point. It does not explain why a particular programme is delayed.

Leadership should examine the conditions of the assignment before reaching for a cultural explanation or a familiar change framework.

Establish what the group can decide

Separate decisions held by group management from those reserved to shareholders, boards or local entities. Check formal authority and the practical process used to exercise it.

Consider an illustrative shared finance programme. The group selects a common platform, but local entities retain responsibility for important process decisions. The programme assumes common definitions and reporting dates before the responsible executives have agreed them. Implementation begins against an unresolved operating model.

The recovery needs a decision on what will be common, which exceptions are justified and who can approve them. Escalating every disagreement to the chief executive may clear individual issues while leaving the underlying ambiguity untouched.

Distinguish necessary differences from avoidable variation

Some differences between entities reflect applicable obligations, contracts or legitimate customer needs. Others reflect history or preference. Treating all variation as resistance can lead to a poor design; accepting every variation can make the common programme uneconomic.

Ask each entity to explain the basis and consequence of a proposed exception. Use appropriate local specialists where interpretation is required. Record the decision so the same issue does not return at the next workshop under a different description.

Leadership then has a visible choice about the cost and benefit of standardisation. That choice belongs in the investment case as well as the design documents.

Test readiness in the entities doing the work

A central plan can hide local capacity constraints. Identify the staff required for testing, data preparation and training in each entity. Confirm what other commitments they carry and who can release their time.

Examine existing systems and data before promising a common launch date. Where readiness differs materially, assess whether a phased approach would reduce risk or create expensive temporary interfaces. Both possibilities deserve analysis.

Communication should fit the people affected, including relevant language and role requirements. Ask users to demonstrate the new tasks and explain where they would seek help. General claims about employee age or regional attitudes add little to that assessment.

Bring a recovery choice to leadership

Show the remaining benefit, cost to complete and consequences of the available options. Identify the decisions required from each authority and the external dependencies that could still change the plan.

Report progress by entity where the differences matter. A group average can conceal a business that is not ready and may delay everyone else. Keep the original commitments visible alongside any revised forecast.

For the next recovery review, choose one blocked outcome and trace its authority, local requirements and capacity needs. A specific explanation gives leadership something it can resolve. A general diagnosis of “regional resistance” does not.