Organisational Change Delivery in the UAE: Why Programmes Stall and How to Keep Them Moving

Organisational change programmes in the UAE stall not because people resist change, but because the programme was not structured to maintain momentum when resistance appeared. Resistance to change is normal and predictable. A delivery structure that treats resistance as an exceptional condition rather than a planned-for variable will lose momentum the first time it encounters pushback — which is typically within the first six weeks.

This distinction matters practically. The response to a culture diagnosis is investment in communication, leadership visibility, and engagement activities — all of which take time and have uncertain outcomes. The response to a structural diagnosis is a governance correction that can be made quickly: clarifying the decision rights, repositioning the PM function relative to the programme sponsor, or redesigning the workstream structure so that dependencies are managed rather than assumed. These are not the same interventions, and applying the culture response to a structural problem is a significant reason why UAE change programmes take longer and cost more than their business cases assumed.

Several structural conditions are specific to the UAE operating environment and are underweighted in global change management methodology. Each one is predictable — and each one is manageable if it is planned for rather than encountered.

High workforce turnover disrupts change programmes mid-delivery. UAE organisations across most sectors experience staff turnover that is materially higher than comparable markets in Europe or North America. On a twelve-month change programme, it is not unusual for a UAE business to lose between 20 and 35 percent of the staff who were in scope at programme initiation. Each departure takes institutional knowledge out of the programme and requires a new hire or internal transfer to be onboarded into a change process they did not help design. A change programme that was designed around the initial population becomes progressively misaligned with the actual population delivering it. Independent PM oversight tracks this drift and recalibrates the programme design — communication materials, training sequencing, role mapping — against the current workforce rather than the one that existed at launch.

Decision velocity creates a specific UAE change problem. UAE organisations make strategic decisions quickly. The same velocity does not always carry through to operational decision-making during delivery. A programme that required ten cross-functional decisions in its first month to stay on schedule may find those decisions deferred, escalated without resolution, or made by individuals below the authority threshold needed to make them stick. The result is a programme whose workstream leads are working hard but whose progress is blocked by open decisions that nobody owns. TrustForce's approach on UAE change programmes is to build a decision register at programme initiation — a pre-populated log of the decisions the programme will need, the authority level required for each, and the window within which each must be made before it becomes a programme risk. This register is reviewed at every steering committee and drives the agenda rather than responding to it.

Regulatory change is running in parallel with operational change. Since 2023, UAE businesses have been absorbing corporate tax implementation, updated ESG reporting expectations from UAE authorities and international investors, and in some sectors additional regulatory obligations under revised federal frameworks. A change programme running alongside a regulatory compliance workstream is competing for the same senior management attention, the same finance and legal resource, and in some cases the same operational systems. Without programme-level governance that maps the interaction between the change programme and the regulatory workstream, they collide rather than coordinate — generating rework, conflicting priorities, and senior management fatigue that is often misread as change resistance.

Multi-nationality communication complexity undermines adoption. UAE change programmes typically run across workforces with significant language diversity — English, Arabic, Hindi, Tagalog, and other languages may all be present in the same change scope. Communications designed in English reach the leadership layer but not always the operational staff whose behaviour the programme needs to change. Training materials that are translated but not contextualised for different cultural assumptions about authority, hierarchy, and process compliance land differently across different workforce segments. This is not an insurmountable challenge — but it requires a communication and training design that is built for the actual workforce rather than adapted from a global template at the point of delivery. A PM who understands the workforce composition at programme design stage can build this requirement into the programme plan rather than discovering it when adoption rates are lower than expected.

The problem was that the programme had no decision register, no workstream dependency map, and no mechanism to escalate blocked decisions to the steering committee in between its monthly meetings. The change team was producing outputs — communications, training materials, engagement surveys — but the structural decisions that would determine how those outputs were used had not been made. Which roles were changing. Which processes were being redesigned. Which systems would be updated and when. Each of these was described in the programme design document but none had been formally decided and owned by a named individual with the authority to make the decision stick.

TrustForce's first action was to build the decision register retrospectively — identifying every structural decision the programme needed, its current status, and its owner. Of the thirty-one decisions logged, nineteen were either undecided or had been decided by someone below the authority threshold. The steering committee approved a revised governance model at an extraordinary session two weeks later: a fortnightly programme board replacing the monthly steering committee, a named decision owner for each open item, and a two-week decision window before any open item was escalated to the CEO. Within eight weeks, all nineteen decisions had been made. Workstreams began closing. The programme completed six weeks behind the original schedule — which, given it had been effectively stationary for four months, represented a significant recovery.

The following questions identify structural weaknesses in a UAE change programme before they generate stalling. They are applicable at initiation, during delivery, or when a programme that appeared to be progressing has lost momentum.

• Has every structural decision the programme requires been logged, with a named owner and a decision deadline — not a target date, but a deadline after which the programme is formally at risk?
• Does the steering committee agenda lead with open decisions and blocked workstreams, rather than with progress updates? Progress updates confirm what has happened; decision-focused agendas determine what happens next.
• Is there a workstream dependency map that identifies which workstreams are blocked by outputs from another workstream, with those dependencies tracked as programme risks rather than as the problem of the downstream workstream lead?
• Has the programme design been reviewed and updated to reflect actual workforce composition at the current point in delivery — not the population in scope at launch?
• Are the regulatory compliance workstreams affecting the same business areas as the change programme mapped against the programme timeline, with explicit coordination points identified?

A no answer on any of these does not mean the programme will fail. It means the programme has an unmanaged structural condition that, when activated by a predictable event — a personnel departure, a deferred decision, a regulatory deadline — will produce stalling that will be diagnosed as a culture problem and addressed with the wrong intervention.

If you are leading or sponsoring an organisational change programme in the UAE — whether a restructuring, a process redesign, an operating model transformation, or a post-acquisition integration — and you want the programme governance structure assessed before it stalls, TrustForce provides programme management for business change engagements across the UAE. We operate from Ras Al Khaimah with experience across group restructuring, operating model change, and regulatory-driven transformation in the UAE market. Contact TrustForce to discuss your programme's governance structure.

For context on the strategy-to-delivery handoff where most UAE transformation programmes first lose momentum, see Why UAE Transformation Projects Lose Momentum at the Strategy-to-Delivery Handoff. For context on how programme governance applies to UAE market entry programmes with parallel workstreams, see The UAE Market Entry Checklist: What to Have in Place Before You Start.