Why Organisational Change Can Fail in UAE Companies: Seven Human Factors Leaders Overlook

By Mafalda Carvalho

The UAE is not short of transformation ambition. Its Digital Economy Strategy, launched in 2022, aims to double the digital economy’s contribution to GDP from 9.7% to 19.4% within ten years. PwC’s 2026 UAE AI Jobs Barometer reports that the share of job postings requiring AI skills rose from 1.0% in 2021 to 3.2% in 2025. The strategic case for change is clear. Leaders must also understand what makes people able and willing to implement it.

A platform can go live while employees continue using workarounds. Training can be completed while managers quietly signal that the old process is safer. These are illustrative warning signs, not findings about any particular UAE organisation. They show why leaders should examine everyday behaviour alongside project milestones.

1. Clarity about everyday work

What looks like resistance may be uncertainty about purpose, roles or consequences. Leaders should answer four questions plainly: What is changing? Why now? What will be different in my work? What happens if the new process creates a problem?

Ask employees to demonstrate the revised task. If they cannot explain or perform it, investigate unclear instructions and process design before attributing the difficulty to attitude.

2. Capacity to absorb change

PwC’s 2025 Middle East workforce survey of 1,286 employees found that 75% had used AI at work in the previous year and 82% said AI improved productivity. Yet 45% reported fatigue.

These are regional self-reports, not UAE-only measures or proof that AI causes fatigue. They suggest leaders should examine capacity alongside enthusiasm. Protect time for training and migration, stop superseded tasks and measure overtime, rework and backlog before adding expectations.

3. Middle managers as implementation partners

Senior leaders announce change; employees experience it through the manager allocating work and handling exceptions.

Brief managers before rollout, explain decision boundaries and adjust targets that reward the old process. Give each manager an escalation route and a named programme contact. A weekly review should establish which problems were resolved, which remain open and who owns the next action.

4. Communication across a multinational workforce

In UAE organisations with multinational teams, test understanding across languages, shifts and professional backgrounds. One English-language presentation may not reach everyone equally.

Use plain-language instructions, demonstrations and translations where needed. Offer private or anonymous feedback alongside open discussion, without stereotyping nationalities. Ask employees to explain changes affecting roles, performance and technology; publish answers to recurring questions, including concerns about job security.

5. Psychological safety with accountability

People need a practical route to report confusion, risk or failure. Managers should respond constructively while keeping standards and responsibilities clear.

Record the concern, assign an owner, agree a response date and tell the employee what happened. Psychological safety is not permission to ignore standards; accountability is not a reason to punish someone for identifying a faulty process. Treat silence as incomplete information rather than agreement.

6. Human responsibility for automation

In PwC’s regional survey, 85% identified job security as a priority when considering new roles. Explain honestly what automation changes, what remains uncertain and how people will be supported.

Name the person accountable for decisions involving safety, ethics, employment or contested exceptions. Provide a human review route and define when staff should override or escalate a system recommendation. Do not promise that jobs are protected if that has not been decided.

7. Measurement beyond project completion

Track active use, demonstrated competence, errors, rework, absence, turnover, complaints and unresolved exceptions. Compare teams and shifts against their own baselines.

Training attendance alone does not demonstrate competence, and rising usage alone does not establish better outcomes. Investigate divergence: a green dashboard alongside shadow spreadsheets, routine workarounds or longer working hours. Check the quality and completeness of the data before declaring success.

Two documented UAE examples

Emirates NBD’s digital and branch services

Emirates NBD’s 2024 digital transformation included ENBD X services and a new branch queue-management system with a service-ambassador platform. The implementation task was to make customer journeys work across digital and branch channels.

Its Q4 2024 investor presentation reports close to 200 instant ENBD X services, over 1.4 million registered users, digital adoption of 91% and approximately 30% shorter branch waiting times.

These are bank-reported customer adoption and service measures. They do not establish employee engagement, the absence of resistance or successful internal change management. The practical lesson is to link a named process improvement to observable service outcomes, then investigate staff experience separately.

Dubai Paperless

Dubai Paperless addressed reliance on paper across internal government procedures and customer transactions. Launched in 2018, it enrolled government entities in five phases, using integration and automation across participating organisations.

Digital Dubai’s December 2021 completion announcement reports implementation across 45 entities, more than 1,800 digital services, over 336 million sheets of paper avoided and savings exceeding AED 1.3 billion and 14 million working hours.

These are official programme-reported outcomes, not an independent causal evaluation. The documented approach illustrates staged implementation across organisational boundaries. It does not, by itself, measure employee wellbeing or explain every adoption difficulty.

A practical 30/60/90-day framework

The following is a proposed management framework, not a description of either organisation’s programme. Set decision thresholds before the pilot and tailor them to the process and its risks.

In a multinational team, include employees who use different languages, have different levels of digital confidence and work outside the main office. A pilot involving only confident volunteers may miss barriers that become visible when rollout reaches other groups.

Days 1–30: Diagnose and prepare

The executive sponsor defines the outcome and human decision boundaries. The process owner maps the existing workflow with frontline staff, including exceptions and duplicate tasks. HR and line managers assess workload, affected roles and learning needs. The programme analyst records adoption, errors, turnaround time and complaints.

End this phase with a baseline, stakeholder map, named owners and a pilot plan. Proceed only when staff can explain the change and support capacity is available. Decide in advance who can stop the pilot, which incidents require immediate escalation and how employees can obtain help without abandoning essential work.

Days 31–60: Pilot and learn

The process owner runs a controlled pilot across representative teams and shifts. Managers protect practice time; trainers observe task performance rather than attendance. IT resolves defects, while the analyst tracks usage, rework, exceptions and service outcomes.

Review findings weekly with employees. Expand only if competence and outcomes meet agreed thresholds. Pause for unresolved safety concerns, recurring errors or unsustainable workload; redesign when users repeatedly need workarounds.

Keep a short exception log showing the task, impact, temporary response and resolution owner. Distinguish unfamiliarity requiring supported practice from a system defect or an impractical workflow requiring redesign.

Days 61–90: Decide and sustain

The sponsor and process owner compare pilot results with the baseline, checking that gains are not achieved through overtime or poorer service. Scale in stages where evidence is satisfactory.

Assign an owner for each remaining exception, retire redundant processes and publish changes made following feedback. HR reviews workforce indicators; managers monitor continued use and competence. If results vary substantially between teams, investigate and redesign before extending rollout. Maintain review after day 90.

Leaders can misdiagnose confusion as resistance, overload as negativity or poor design as a training problem. UAE organisations pursuing digital and AI strategies should make these distinctions explicit. A useful implementation review asks what people understand, what they can do, what prevents progress and which evidence justifies the next decision.

About the author

Mafalda Carvalho is a UK-based author, founder and adult social care leadership practitioner. Through Prestige Care Consulting, her work focuses on the human implementation of organisational change: leadership behaviour, trust, workforce capability, culture and responsible technology. She is the author of The Prestige Leader: The Human Side of Healthcare Leadership. She has not advised UAE organisations directly; this article’s UAE analysis is based on authoritative local strategy and workforce evidence.

Featured photograph: cottonbro studio / Pexels. Author photograph: Courtesy of Mafalda Carvalho.