Feedback training fails in multicultural teams not because the concept is wrong, but because the standard model was built for one kind of workplace. If you have run a giving-feedback-across-cultures programme in the UAE and watched participants revert to their old patterns within a week, the design is almost certainly the problem — not the people. This article is about what you actually change on Monday morning.
Most off-the-shelf feedback programmes assume that the barrier is knowledge: teach people the SBI model, run a role-play, send them back to their desks. In a team where everyone shares roughly the same professional socialisation, that can work. In a team where a Filipino analyst, an Emirati line manager, a British consultant and an Indian engineer sit in the same room, the model produces polite compliance during the session and zero transfer afterwards. The gap is not conceptual understanding. It is design.
The four situations below are not hypothetical. They reflect the kind of friction that appears consistently in corporate training for multicultural workforces in the UAE and across the Gulf. Each one describes what happens, why it happens in this specific context, and — most importantly — what you change in the training design.
What Standard Feedback Training Gets Wrong in Multicultural Workplaces
The default programme structure does three things that quietly undermine transfer in a diverse team. It presents feedback as a neutral, universal skill. It treats the role-play as the learning moment. And it runs the debrief as a group confession.
None of those assumptions hold in a feedback culture in multicultural workplaces. Feedback is not neutral — it carries different social weight depending on who is giving it, who is receiving it, and who is watching. The role-play produces performed behaviour, not real behaviour, because participants know the rules of the exercise. And a public debrief in a group with steep internal hierarchy creates a dynamic where junior participants perform psychological safety without experiencing it.
The result is a programme that scores well on post-session surveys and produces no measurable change. If you have seen that pattern, you are not imagining it. The fix is not more content. It is a different architecture.
Four Situations Where the Standard Model Breaks Down — and What to Do Instead
Each situation below identifies a specific failure point, explains why it is particularly acute in UAE and Gulf-region organisations, and gives a concrete design change you can implement.
Situation 1 — The Silent Receiver
What happens: A participant — typically from a background where receiving feedback from a peer or junior is socially unusual — gives no visible response during a feedback role-play. No pushback, no engagement, no body language. The facilitator reads this as acceptance. The participant has actually disengaged entirely.
Why it happens here: In many of the national groups common to UAE corporate environments, receiving developmental feedback from someone at a similar or lower level is not a neutral act. It carries connotations about face, status, and public positioning that the exercise has done nothing to address. The participant has not been given a legitimate way to respond, so they do not respond.
What you change: Before the exercise runs, explicitly name the response. Give every participant a structured response protocol — not “what do you say when you agree” but “here are three things you can say when you are processing, disagree, or need time.” Run the first round with same-nationality pairs so participants can calibrate without an audience. Move to cross-nationality pairs only after the response behaviour has been practised in lower-stakes conditions. The goal is not to eliminate discomfort — it is to give people a way to stay in the conversation.
Situation 2 — Upward Feedback That Evaporates
What happens: The programme includes an upward feedback exercise. Participants complete it in writing. Nothing changes in behaviour, and when the facilitator follows up three weeks later, the manager has not referenced the feedback once.
Why it happens here: In organisations with strong hierarchy distance — common in both GCC national cultures and in the large South and East Asian communities that make up much of the UAE private-sector workforce — upward feedback is not experienced as information. It is experienced as a risk. The manager who ignores it is not being defensive; they are operating entirely rationally within their social context. The exercise did not change the context.
What you change: Separate the skill of giving upward feedback from the act of giving it to your actual manager. Run the skill practice with fictional scenarios or with managers from other departments. Build in a facilitated conversation between managers and their teams about how feedback will be received and acted upon before any real upward feedback is collected. If the organisation has not created a credible mechanism for managers to visibly act on upward feedback, do not run the exercise — you will train people to take a risk that is not worth taking, and you will lose their trust.
Situation 3 — Direct and Indirect Communication Misfiring in the Same Room
What happens: During a cross-cultural communication training exercise, one participant gives blunt, specific feedback (“your presentation had no clear recommendation”). Another participant gives the same feedback wrapped in qualifications and appreciation. The first participant reads the second as evasive. The second participant reads the first as aggressive. Both are correct within their own reference frames. Neither changes.
Why it happens here: In teams that span Northern European, South Asian, Arab, and East Asian communication norms — all present in the UAE workforce — the range of direct and indirect communication styles in a single room is wider than most facilitators account for. The standard exercise asks people to observe the difference. It does not ask them to work together across it.
What you change: Design the exercise so that cross-style pairs must reach a shared outcome, not just exchange feedback. Give them a shared task — a short written document, a prioritised list, a decision — that requires them to negotiate meaning, not just deliver it. Debrief the task outcome first (“did you reach agreement?”) and then the process (“what made it difficult?”). This shifts the reflection from personal style to functional collaboration. It also surfaces the cost of miscommunication in a way that feels real, not theoretical.
Situation 4 — Psychological Safety That Is Performed, Not Felt
What happens: Participants say the right things. The facilitator observes nodding, participation, positive affect. Post-session feedback is excellent. Three weeks later, no one has had a difficult conversation.
Why it happens here: In multicultural corporate environments in the UAE, participants are often extremely skilled at reading what a professional context requires and performing it fluently. This is not cynicism — it is a sophisticated social competence. But it means that a session that looks like psychological safety has been established may have produced nothing more than well-practised professional behaviour. The real test of psychological safety is not what happens in the room. It is what happens in the corridor afterwards.
What you change: Add a 48-hour commitment exercise to the programme. At the end of the session, each participant writes one specific feedback conversation they will have before the next touchpoint — with a named person, on a named topic. At the next session, the debrief starts with: what happened? This design does two things. It moves the learning transfer point from the session to the workplace. And it creates a low-stakes form of accountability that does not require anyone to report failure publicly — they simply describe what occurred.
What Changes in the Programme Design: A Practical Reference
The table below maps the standard programme element to the adjusted version for multicultural teams in the UAE and Gulf context. These are not optional refinements — they are the difference between a programme that transfers and one that does not.
| Standard Design Element | Adjustment for Multicultural Teams in the UAE/Gulf |
|---|---|
| Mixed-nationality pairs from the start | Same-nationality pairs first; cross-nationality pairs in round two |
| Upward feedback collected from direct manager | Upward feedback practised with fictional or cross-department scenarios first |
| Group debrief after each exercise | Small-group debrief (3–4 people), then plenary synthesis |
| Role-play with a scripted scenario | Task-based exercise with a real shared output |
| Session-end reflection (“what did you learn?”) | 48-hour commitment (“what will you do, with whom, by when?”) |
| Single facilitator | Co-facilitation with a facilitator who has regional experience in GCC contexts |
| One-day programme | Minimum two touchpoints, 2–3 weeks apart, to allow real transfer |
The Debrief Is Where the Design Either Holds or Collapses
The debrief is the highest-leverage moment in any experiential learning programme. In a multicultural team, it is also the moment most likely to be mishandled — not because the facilitator lacks skill, but because the standard debrief format assumes that open group reflection is safe for everyone in the room.
It is not. In a group with strong internal hierarchy, the most junior participants will not speak candidly in front of their direct line manager. In a group where face is a genuine professional concern, participants will not publicly identify a breakdown in their own behaviour. These are not personal failings. They are rational responses to the social structure of the room.
The design fix is sequencing. Start the debrief in pairs or trios. Give participants time to process privately before the group surfaces. Ask specific, behavioural questions rather than open invitations: “what was the moment in the exercise where you had to make a choice?” is safer than “how did you feel about the exercise?” Move from the concrete to the reflective, not the other way around. And always close with a forward-facing question — not “what did you learn?” but “what will you try differently tomorrow?”
For HR directors and L&D managers running leadership development in the UAE, the debrief structure is not a facilitation nicety. It is the mechanism by which the experiential learning transfers into actual behaviour change. A well-designed exercise with a poorly designed debrief produces the same outcome as a mediocre exercise. The experience is not the learning — the reflection on the experience is.
Frequently Asked Questions
Why does feedback training work in some multicultural teams but not others?
The teams where it works have usually had at least one prior cycle of the programme, so participants understand the conventions and trust that feedback is being given in good faith. First-time programmes in high-hierarchy, high-diversity environments fail at higher rates because neither condition is in place yet. The design needs to build both before it can expect transfer.
Do we need to separate participants by nationality during exercises?
Not permanently, and not as a policy. Same-nationality pairing in the first round of practice is a scaffolding technique — it lowers the social stakes while the new behaviour is being built. Cross-nationality pairing should follow as quickly as the group is ready. Keeping nationality groups separated throughout the programme defeats the purpose.
How do we handle a participant who refuses to give feedback to a senior colleague?
Do not name it as a refusal in the room. Design the exercise so that no participant is asked to give developmental feedback to their own direct manager during a training session. Peer feedback and skip-level scenarios are safer starting points. Reserve manager feedback for later in a longer learning journey, once trust in the process has been established.
Should the facilitator address cultural differences explicitly?
Directly naming cultural patterns risks reducing individuals to national stereotypes, which is both inaccurate and counterproductive. The better approach is to name the dynamics without attaching them to groups: “in some professional contexts, receiving peer feedback carries a different weight — let’s design for that.” The design accommodates the diversity without making any participant feel they are being explained.
How long does it take to see real behaviour change in feedback culture?
A single session does not change feedback culture. A well-designed programme with two or three touchpoints over six to eight weeks, combined with manager modelling and follow-through, begins to produce observable change. Single-day programmes produce single-day change.
What is the difference between this kind of soft skills training and standard communication workshops?
Standard communication workshops transfer knowledge about feedback. What is described here transfers behaviour. The distinction is the design: task-based exercises with real outputs, commitment loops that bridge the session and the workplace, and debriefs structured to produce reflection rather than performance. Soft skills training in the UAE that does not build in those elements will produce articulate participants who behave exactly as they did before.
Build the Design Around the Room You Actually Have
Feedback training fails in multicultural teams when the programme is designed for an imagined team rather than the actual one. The fix is not a new model or a new framework — it is a different set of decisions about pairings, sequencing, debrief format, and how transfer is checked. These decisions are made at the design stage, not the delivery stage. By the time the facilitator is in the room, most of the leverage has already been used or wasted.
If you are responsible for how experiential programmes are built for Emirati organisations and want to design feedback training that transfers across a multicultural workforce, the starting point is a conversation about the specific team composition, the hierarchy structure, and what has already been tried.
Speak to the HDS Learning team to discuss how your next feedback programme can be designed for the team you actually have — not the one a standard template assumes.
