People management
Put the right people in the right seats
In a UAE team where nationalities, languages, and work styles mix daily, guessing who is good at what is expensive. This guide shows a practical way to identify the strengths of each team member using observation, structured feedback, and assessments, then use those findings to redesign roles.
Why it matters
Why strengths mapping pays off in the UAE
The UAE workforce is one of the most diverse in the world. According to the country’s demographic profile expatriates make up close to 88 percent of residents, and most teams in Dubai, Abu Dhabi, and Sharjah bring together people from more than a dozen backgrounds. Different education systems, communication norms, and career histories mean two employees with identical job titles can have very different strengths.
Mapping those strengths pays off in three concrete ways: hiring becomes sharper because you know what gap you are filling, retention improves because people are given work they are actually good at, and performance conversations stop being awkward because they are grounded in observed behaviour instead of opinion.
When to start the exercise
Some managers wait until a crisis, a resignation, a failed project, a client complaint, before asking who on the team is really strong at what. That is too late. Good moments to run a strengths review include: after a hiring wave, when you inherit a team, before restructuring departments, ahead of a big project, or once a year as part of a formal review cycle.
If your organisation follows an annual appraisal on the Gregorian calendar, tie the exercise to that. If it follows the fiscal year (many UAE free-zone companies do), attach it to Q1 planning. The key is to make it repeatable, not a one-off.
What to expect from the process
Honest surprises
The quiet developer often turns out to be your best mentor. The loud sales rep sometimes crumbles under real client pressure. Assume you will be wrong about at least one person.
Uncomfortable moves
You may need to move someone out of a management seat they wanted, or promote someone who never asked. Both conversations require care.
Continuous work
Strengths shift with experience and life stage. Treat the map as a living document, not a permanent label.
The five-step procedure
Work through these steps in order. Skipping the early ones and jumping straight to assessments is the most common mistake, the test result is only useful if you already know what you are looking for.
- Define the strengths that matter. Write down the six to eight qualities your team actually needs. For a Dubai retail operation this might be resilience under pressure, Arabic-English fluency, upselling, and conflict de-escalation. For a Riyadh-facing sales team it might be relationship building, patience with long sales cycles, and cultural fluency. Generic lists (“leadership, teamwork, communication”) are useless.
- Observe in real work. Spend two to four weeks watching people in normal conditions. Note who volunteers first when the brief is vague, who calms clients down, who spots the error in the spreadsheet, who quietly fixes team conflicts. Write it down the same day, memory decays fast.
- Collect 360-style feedback. Ask each person’s peers, direct reports, and one or two clients three simple questions: what does this person do better than anyone else on the team, where do they get stuck, and what would you trust them with tomorrow. Keep it anonymous.
- Run a structured assessment. Observation and feedback catch visible behaviour but miss stress response, decision style, and hidden leadership potential. A behavioural assessment test gives you a common vocabulary and a baseline you can compare across the team. Choose one that has been validated on regional workforces, not a free online quiz.
- Discuss and re-map roles. Sit with each person one-on-one, share what you found, and ask if it matches how they see themselves. Then decide together: stay in role, expand scope, shift responsibilities, or move sideways. Document the outcome and revisit it in six months.
Comparing the main methods
Each method surfaces a different layer. Use them together, not as substitutes.
| Method | What it reveals | Time cost | Best used for |
|---|---|---|---|
| Direct observation | Day-to-day behaviour, habits, initiative | Low (part of managing) | All team members, continuously |
| Peer and 360 feedback | How the person is experienced by others | Medium | Mid to senior staff, once or twice a year |
| Structured interviews | Motivations, career goals, self-awareness | Medium | New hires, promotion candidates |
| Behavioural assessments | Decision style, stress response, leadership fit | Low per person, higher setup | Full teams, restructures, succession planning |
| Project post-mortems | Real performance under pressure | Low (already happens) | After every major deliverable |
Signals to watch
Strengths hide in specific behaviours
- Potential leader: stays calm when the plan changes, is trusted by peers to mediate, asks about the wider goal.
- Strong technical fit (IT, engineering, finance): spots the second-order problem, prefers writing to talking, resists shipping something they do not believe in.
- Client-facing talent: remembers small personal details about clients, adapts tone across cultures, defuses complaints without escalating.
- Operations spine: notices when a process is silently broken, builds checklists nobody asked for, keeps the team on time.
- Coach or mentor: new joiners keep drifting to their desk, they explain without condescension, they ask more than they tell.
People are not resources. They are a portfolio of talents, and your job as a manager is to know what each one holds.
Common mistakes to avoid
- Confusing confidence with competence. The person who speaks first is not always the person who knows most.
- Rewarding good individual performers with a management role they do not want. Not every strong engineer wants to lead engineers.
- Assessing once and never revisiting. Life events, new skills, and new responsibilities all shift the picture.
- Keeping the results secret. If people never see their own map, they cannot act on it.
- Copy-pasting a Western framework without adaptation. Norms around hierarchy, feedback, and disagreement vary widely across the GCC.
Turn the map into action
Identifying strengths is only the first half. The second half is redesigning who does what, so that each person spends more of their week on work they are naturally good at. That is where retention, engagement, and output all move together.
Frequently asked questions
How long does it take to identify the strengths of a whole team?
For a team of eight to fifteen people, budget four to six weeks. That includes two to three weeks of observation, one week to collect peer feedback, one week to run a structured assessment, and one week for one-on-one conversations. Rushing the observation phase is the fastest way to get a shallow, misleading result.
Are behavioural assessments reliable for a multicultural UAE team?
They can be, if you choose one that has been validated on regional or international samples rather than a free online quiz. The strongest assessments measure behavioural patterns (how someone responds to pressure, ambiguity, or conflict) which travel across cultures better than personality labels.
Always combine the assessment result with observation and peer feedback. Treat it as one input, not a verdict.
What if an employee disagrees with what the strengths review shows?
Take the disagreement seriously. Sometimes the assessment or feedback captured a bad month rather than a real pattern. Ask the employee for specific examples that contradict the finding, and share the examples you observed. If the gap remains, agree on a three-month trial in a role that tests the disputed strength, then review together with fresh evidence.
Should I share peer feedback verbatim with the person it is about?
No. Summarise the themes and remove anything that could identify the source. The purpose of 360 feedback is to help the person grow, not to relay complaints. If a specific issue is serious enough to name, raise it as a manager in a separate conversation, not through the anonymous channel.
How often should the strengths map be updated?
Once a year for a full refresh, and any time a major event happens: a promotion, a new project, a team restructure, or a change in scope. People grow into new strengths and out of old ones. A three-year-old map is close to fiction.
Do small businesses in the UAE really need a formal process for this?
Yes, arguably more than large ones. In a team of five, one person in the wrong seat drags down 20 percent of output. Small businesses cannot carry that cost. The process does not have to be formal, a simple spreadsheet, honest one-on-ones, and one structured assessment per person is enough for most SMEs in Dubai or Abu Dhabi.
I am an accomplished coder and programmer, and I enjoy using my skills to contribute to the exciting technological advances that happen every day at Oswald Tech.