ABP Consulting is a French management-training and coaching firm delivering professional development programmes in Dubai, United Arab Emirates.https://www.abp-consulting.ae/en-AEhttps://www.abp-consulting.ae/en/blog/motivating-a-multicultural-team/https://www.abp-consulting.ae/en/blog/motivating-a-multicultural-team/Most managers in Dubai control far less of the pay than of the things that actually drive engagement. The trouble is that the standard advice on those levers assumes a team that shares expectations.Fri, 14 Aug 2026 00:00:00 GMTAsk a manager in Dubai what would improve engagement on their team and the first answer is usually about salary. Ask what they actually control and the answer is usually: not salary. That gap is where most management energy gets wasted. The useful question is not whether pay matters — it plainly does — but what is available to a manager once pay is fixed for the year. ## Four levers a manager controls Four things reliably affect how engaged someone is at work, and a line manager influences all four without needing a budget. **Autonomy** is the degree to which someone decides how their work gets done. It is the cheapest lever and the most commonly withheld, usually by managers who would describe themselves as supportive. **Recognition** is being seen accurately. Not praised generically — seen. The distinction matters, because generic praise from someone who does not understand what was difficult reads as noise. **Visible progress** is knowing that something moved. On work with a two-week cycle this takes care of itself. On work with an eighteen-month cycle it has to be manufactured deliberately, or people experience months of effort as months of nothing. **Meaning** is understanding what the work is for. It is the lever most often addressed with a poster and least often addressed with a conversation. ## Why the standard advice underperforms here Each of those levers has a standard implementation, and each standard implementation quietly assumes a shared set of expectations. Take recognition. The default advice is to praise good work publicly and promptly. In a team drawn from a dozen countries, public praise singles out one person in front of colleagues who may read it as favouritism, or embarrasses someone whose norm is that individual credit belongs to the group. The advice is not wrong. It is under-specified. Autonomy has the same problem in reverse. Handing someone full latitude reads as trust to one person and as abandonment to another — particularly to someone who was trained in a working culture where a manager who gives no direction is a manager who is not doing their job. The fix is not a different set of levers. It is to stop inferring what someone wants from what you would want. ## How to find out The most efficient method is also the most obvious one, which is presumably why it is skipped so often: ask. Not "are you happy here", which produces a polite yes. Ask what a genuinely good week looks like. Ask which part of the last project they would want more of. Ask what they would change about how their work is organised if nobody said no. Those questions produce specifics, and specifics are actionable in a way that a satisfaction score is not. For managers who want a structure underneath those conversations, the [Enneagram](/en/glossary/#enneagram) is useful precisely because it deals in motivation rather than behaviour — what a person moves toward and away from, which is the thing you are trying to find out. We use it for that in [Motivating without a budget](/en/training/management/motivation-without-budget/), alongside the practical work of redesigning how a job is shaped. ## The situation this does not fix If someone is paid materially below market, none of this holds them. It might buy a few months. Managers get this wrong in a specific way: they treat a pay problem as an engagement problem, because engagement is the thing they can act on. Six months of thoughtful autonomy-building later, the person leaves anyway, and the effort was real but aimed at the wrong target. Diagnose which problem you have first. If it is pay, your job is to escalate it with evidence, not to compensate for it with recognition. ## Where to start this week Pick one person. Ask what a good week looks like. Then change one thing about how their work is organised in response to what they actually said. That is a smaller intervention than a motivation programme and it works more often, mainly because it starts from evidence rather than from a framework.managementmotivationmanagementmulticultural-teamshttps://www.abp-consulting.ae/en/blog/disc-or-enneagram/https://www.abp-consulting.ae/en/blog/disc-or-enneagram/Both models get used for the same purpose and they are not interchangeable. One describes behaviour you can observe in a meeting; the other describes motivation you cannot.Thu, 06 Aug 2026 00:00:00 GMTLeadership teams tend to arrive at these two models through a recommendation rather than a comparison. Someone did DISC at a previous company; someone else found the Enneagram genuinely revealing; a decision gets made on the strength of whoever spoke most recently. They are not interchangeable, and the difference is easy to state. Short definitions of both sit in the [glossary](/en/glossary/#disc); what follows is how to choose between them. ## What each one actually measures **DISC describes behaviour.** How direct you are, how fast you decide, how much detail you want, how much warmth you need before getting to the point. It sorts these into four preferences and it describes what you do, in a working context, observably. **The Enneagram describes motivation.** Nine patterns, each built around a core drive and a core fear. It addresses why someone behaves as they do — which is a different question, and often a more surprising answer. The practical consequence: two people can share a DISC profile for completely different reasons. Both appear decisive and impatient with detail. One is driven by a need to achieve; the other by a need to avoid being controlled. They look identical in a meeting and they respond to entirely different management. ## Choosing between them The useful question is what your team's problem actually is. **If the problem is friction** — meetings that grind, two directors who cannot run a project together, a leadership team that produces decisions nobody implements — start with DISC. Friction is usually a mismatch of style, and style is what DISC describes. It is also fast: a group can be using the vocabulary usefully by mid-afternoon of day one. **If the problem is misunderstanding** — a colleague whose reaction seemed wildly disproportionate, a pattern that keeps recurring across different teams, someone whose behaviour genuinely puzzles you — the Enneagram is the better instrument. It deals in the layer where those answers live. **If you are not sure**, do DISC. It is quicker, cheaper, and it will tell you whether the remaining problem is deeper than style. A team that finishes a DISC session having resolved most of its friction did not need the Enneagram. A team that finishes it saying "we understand each other better and we still cannot work together" has just diagnosed itself. ## Where both go wrong The failure mode is the same for both, and it has nothing to do with the models. A profile is a hypothesis. It becomes useful when it prompts someone to ask a better question. It becomes actively harmful the moment it becomes a label: *she's a D, that's why she's like that.* At that point the model has stopped generating inquiry and started ending it, and the team is worse off than before, because it now has vocabulary for not thinking. Two guardrails help. First, nobody profiles anyone who is not in the room — absent colleagues do not get typed by a group. Second, every profile statement gets tested against observed behaviour rather than used to explain it away. ## What we do Both models are used in [Self-awareness and positive communication](/en/training/communication/self-awareness-communication/), DISC on day one and the Enneagram on day two, in that order and for the reasons above. DISC on its own also runs through [Consultative selling and negotiation](/en/training/commercial/consultative-selling/), where the application is commercial rather than developmental. Individual results belong to the participant in both cases. Where a company commissions a session, we may report anonymised group patterns if that is agreed in advance — never individual results, and participants are told exactly what will be shared before they answer anything.leadershipdiscenneagramleadershiphttps://www.abp-consulting.ae/en/blog/silence-in-a-meeting/https://www.abp-consulting.ae/en/blog/silence-in-a-meeting/A manager asks whether everyone agrees, nobody objects, the decision proceeds. Three weeks later it turns out half the room never agreed. This failure is common, expensive and fixable.Wed, 29 Jul 2026 00:00:00 GMTThe pattern is familiar enough that most managers in Dubai will recognise it immediately. A proposal is presented. The manager asks whether everyone is comfortable. Nobody objects. The decision proceeds. Three weeks later, implementation has quietly stalled, and it emerges that several people in that room had serious reservations they did not voice. The manager concludes the team is passive. The team concludes the manager does not want to hear disagreement. Both conclusions are wrong, and they will produce the same failure next quarter. ## Four things silence can mean **Agreement.** Sometimes it really is this. **Deference.** In many working cultures, contradicting a senior person in front of others is not candour, it is a discourtesy — and one that reflects on the person doing it. Someone can hold a strong objection and still consider a room full of colleagues the wrong place to raise it. **Confusion.** Following a discussion in a second or third language is cognitively expensive. By the time someone has parsed the proposal precisely enough to object to it, the meeting has moved on. **Disagreement being saved.** The objection is real and will be raised later, privately, to someone the person considers a safer audience. Four meanings, one signal. A manager who defaults to reading it as agreement will be wrong most of the time — and will keep being wrong until the meeting format changes, which is what [The manager-leader toolkit](/en/training/management/manager-leader-toolkit/) spends a full module on. ## Why asking harder does not work The instinctive fix is to ask more insistently. *Does anyone disagree? Last chance. Nobody?* This makes things worse. "Does anyone disagree" is a closed question that has already declared what the expected answer is, and answering it requires volunteering to be the one person obstructing a decision the room appears to have reached. The pressure lands hardest on exactly the people least likely to speak. Asking again does not remove the barrier. It raises it. ## Four practices that do work **Ask for one risk each, not for agreement.** Go around the room and ask every person to name one thing that could go wrong with the proposal. This changes the task: nobody is objecting, everybody is contributing, and the discomfort is distributed evenly instead of falling on one person. It produces real information almost every time. **Collect input before the meeting.** Ten minutes with two people beforehand surfaces most reservations, and surfaces them in a setting where raising them costs nothing. It also means the meeting starts from a more honest position. **Write the decision down and circulate it.** Reading a written decision back against your own understanding is a far lower-stakes act than objecting to it live. Disagreement that would never have been voiced in the room routinely arrives by email the next morning — which is exactly when you want it. **Separate the discussion from the decision.** Two shorter meetings, with a gap, beat one long one. The gap lets people who process slowly, or in a second language, arrive at the second meeting with a formed position. None of these require you to guess anyone's cultural background, which is their main advantage. They work by removing the need to read an ambiguous signal at all. ## The underlying point The instinct to treat silence as consent is not laziness. It is a manager applying a rule that worked in the environment where they learned to manage. In a room where everyone learned the same rule, it works. In Dubai, it usually does not, and the cost surfaces weeks later as a decision nobody implemented.uae-businessmeetingsmulticultural-teamsdecision-makinghttps://www.abp-consulting.ae/en/blog/choosing-a-training-language/https://www.abp-consulting.ae/en/blog/choosing-a-training-language/Most groups pick the language everyone can follow. That is the wrong test. A training session works when participants can argue in the language, not when they can follow it.Tue, 21 Jul 2026 00:00:00 GMTA UAE training group frequently has no shared first language. Twelve participants might hold six between them. The conventional way to resolve this is to find the language everyone can follow, which in practice means English. It is a reasonable default and it is based on the wrong test. ## Following is not participating Comprehension and production are different skills, and they separate widely under pressure. Plenty of people understand a session in their third language without difficulty and cannot argue in it — not because the vocabulary is missing, but because arguing requires composing a position in real time, in front of colleagues, fast enough to be relevant. Which matters, because a training session is not a lecture. Its value comes from participants disagreeing with the method, testing it against their own situation, and rehearsing conversations out loud. A course like [Self-awareness and positive communication](/en/training/communication/self-awareness-communication/) is almost entirely practice, and a participant who cannot practise is a spectator. Someone who can follow but not contest receives a fraction of what the session offers, and usually the least useful fraction. So the test is not "can everyone follow this". It is: **can the least fluent person in the room comfortably disagree with the trainer?** That is a higher bar, and it changes the answer more often than people expect. ## When to split the group If the answer is no, splitting the group is usually better than compromising the language. Two cohorts of eight, each working in a language its participants can argue in, will deliver more than one group of sixteen in a language half of them merely tolerate. It costs more. It is generally still the right call, and it is worth putting that trade-off to whoever holds the budget rather than quietly accepting the cheaper option. ## Why mixing languages does not work The intuitive middle path — run mostly in English, switch when someone struggles, let colleagues translate for each other — sounds accommodating and reliably fragments the room. Side translation creates a parallel conversation that excludes whoever is not part of it. The trainer loses the group's shared attention. Practice exercises stop being comparable, because two pairs are working in different languages on what is supposed to be the same task. And the person being translated for is marked out as needing help, which does not help them contribute. One language, chosen properly, beats three used opportunistically. ## Materials Written materials should be in the session language. Translating handouts into a language not used in the room seems generous and produces two versions of the content. Participants read one and hear the other, and any discrepancy between them — and there is always a discrepancy — undermines both. Where a summary in another language genuinely helps someone, make it visibly a summary rather than a parallel edition. ## What ABP does Training and coaching are delivered in **English, French or Spanish**. This site is published in English and Arabic, and we state the difference plainly rather than letting a bilingual website imply Arabic-language delivery. For a mixed group in the UAE, English is usually the right choice. Where a group shares French or Spanish, running in that language is nearly always better than defaulting to English on principle — comfort in the working language is worth more than consistency with everyone else's booking. Where a group genuinely needs Arabic-language delivery, we will say so rather than take the booking. That is an easier conversation to have before the invoice than after the session — and the same principle governs how we handle [fees and formats](/en/faq/#pricing).uae-businesslanguagestraininguae-businesshttps://www.abp-consulting.ae/en/blog/motivating-and-retaining-gen-z/https://www.abp-consulting.ae/en/blog/motivating-and-retaining-gen-z/Young professionals are described as impossible to retain. They are not — they are expensive to retain badly. Five factors decide it, and four of them are the direct manager rather than the company.Tue, 13 May 2025 00:00:00 GMTThe standard account is that young professionals cannot be retained: no loyalty, unrealistic expectations, gone in eighteen months. The standard response is a perks package, a purpose statement and a flexible working policy, and it does not move the number. Both the account and the response are wrong in the same way. They treat retention as a property of the generation rather than of the offer, and they aim company-level money at a problem that is mostly decided by a direct manager in weekly increments. ## What does not work **Perks.** Table football, snacks, an office redesign, a wellbeing app. These are hygiene factors in the strict sense: their absence generates complaints, their presence generates nothing. Nobody has ever stayed in a job they were leaving because of a coffee machine, and everybody has heard the joke. **Purpose, stated corporately.** A mission statement about transforming an industry is read, correctly, as marketing pointed inward. Meaning does matter, but not at that altitude — which is a distinction worth taking seriously rather than dismissing. **Flexibility as a policy on its own.** Now a baseline expectation rather than a differentiator. Its absence costs you candidates; its presence buys nothing, because the company across the road has it too. **The counter-offer.** The literature on this is consistent and the practitioner experience matches it: most people who accept one leave anyway within the year. By the time a resignation is on the table, the reasons that started the search have been in place for months and money is rarely among them. ## The five things that decide it ### 1. Learning velocity In the first years of a career, what is being accumulated is not salary, it is capability — and capability is what sets salary a decade out. A role that stops teaching has a falling return, and the people best equipped to notice this are precisely the ones you want to keep. The practical measure is uncomfortable and useful: could this person name three things they can do now that they could not do a year ago? If not, the clock is running, whatever the engagement survey says. This costs nothing but attention. Rotate who takes the difficult client. Let someone run the meeting badly once rather than running it well yourself for the third year. Give the stretch assignment to the person who is not quite ready, which is the only way anyone ever becomes ready. ### 2. Feedback cadence An annual appraisal was a legible instrument when a career lasted twenty years at one employer. At a three-year horizon, waiting eleven months to learn where you stand is not patience — it is operating without instruments. That mismatch, and the three others like it, is the subject of [Gen Z and baby boomers](/en/blog/gen-z-and-baby-boomers/). Ten minutes a fortnight, on the work and not on the person, outperforms any annual process. It also improves the annual process, which stops containing surprises. ### 3. A next step somebody has actually described Not a career ladder document. A specific answer to a specific question: what would my job look like in two years if this goes well, and what has to be true for that to happen? Most managers have never said this out loud. The employee therefore concludes that no answer exists — and when no internal answer exists, the external market provides one within a fortnight of updating a profile. Titles are the weakest form of this and the most requested, because they are the only currency visible from outside. Scope, budget, client ownership and the right to decide are worth more and cost less. Say which one is on offer and when. ### 4. Perceived fairness Salary bands, promotion criteria and the allocation of good work. This generation compares more information, more publicly, and with better data than any before it, and an inequity that would once have gone undetected for years now surfaces in a month. Fairness here does not mean equality of outcome. It means that the basis for a difference can be stated and survives being stated. A manager who cannot explain why one person got the client-facing role has a problem whether or not the decision was sound. In a Dubai team this deserves particular care, because pay and progression have historically correlated with passport in this market and everybody knows it. The levers a manager controls directly — visibility, difficult assignments, credit given by name — are exactly where that pattern gets reproduced or broken, a point covered further in [managing across nationalities in Dubai](/en/blog/managing-across-nationalities-in-dubai/). ### 5. The direct manager The factor that dominates the other four. People join organisations and leave managers, which is a cliché because it keeps being true, and no company-level programme has ever compensated for a manager who does not give feedback, does not delegate anything interesting, and takes credit upward. The uncomfortable implication is that a retention problem concentrated in one team is not a generational problem. It is a management problem with a generational explanation attached to it, and the explanation is doing useful work for somebody. ## Meaning, at the right altitude Meaning matters and the corporate version misses it, because it is pitched three levels above where it is experienced. What lands is granular: who used the thing you built, what it changed for them, and what would have happened had you not done it. Most junior work is invisible in exactly this respect — the analysis disappears into a deck that goes into a meeting the analyst was not in, and nothing comes back. Closing that loop is cheap. Forward the client's reply. Say which decision the analysis informed. Name the person in the room where the work is discussed. This is the same visibility problem that, left unattended, produces the profiles in [who is actually working](/en/blog/who-is-actually-working/) — and it is a manager's job in both directions. ## Two practices worth adopting **The stay interview.** Exit interviews sample the wrong population at the wrong moment: the people who already left, after the decision hardened, with an incentive to be diplomatic. Ask the people who are still here, twice a year, in private, three questions — what would make you consider leaving, what would you change about your role, what do you want to be doing in two years. The answers are actionable while there is still time to act on them. **An honest term.** Pretending to offer a twenty-year career to someone who does not believe in one costs credibility on day one. Naming a real horizon — here is what you will learn in three years, here is what it makes you worth afterwards, here is what exists beyond it if you want it — retains people longer than the implied version nobody accepts. It also makes departures amicable, which matters more than it sounds: former employees are a hiring channel and a referral source, and in a market as mobile as this one, they are usually a client eventually. Where the currency is attention rather than cash, the practical toolkit is [motivating without a budget](/en/training/management/motivation-without-budget/), and the manager-as-coach posture that makes the fortnightly conversation work sits at the heart of [The manager-leader toolkit](/en/training/management/manager-leader-toolkit/).managementgenerationsmotivationretentionmanagementleadershiphttps://www.abp-consulting.ae/en/blog/managing-across-nationalities-in-dubai/https://www.abp-consulting.ae/en/blog/managing-across-nationalities-in-dubai/A Dubai team spanning a dozen nationalities does not need a country-by-country manual. Three dimensions explain most of the friction, and two of them are structural rather than cultural.Tue, 26 Sep 2023 00:00:00 GMTA team of twelve in Dubai routinely spans eight nationalities, three or four first languages, and four or five distinct assumptions about what a meeting is for. Managers arriving from a single-culture market ask for a country-by-country briefing: how to manage Indians, how to manage Filipinos, how to manage Emiratis. That briefing does not work, and it is worth being clear about why before describing what does. The variation inside any national group is larger than the average difference between two groups — a Mumbai-raised engineer with a decade in London and a colleague from the same city who has never left have less in common professionally than either has with a peer from anywhere else in the same situation. And Dubai selects for people who are already adapted: most of the room has worked in mixed teams for years and has adjusted accordingly. What survives that objection is narrower and more useful. A small number of dimensions genuinely predict friction, and two structural features of the Gulf labour market amplify all of them. ## Three dimensions that actually matter ### How disagreement is voiced This is the largest single source of misunderstanding in a Dubai team, and the one with the greatest consequences. At one end sit professional cultures where contradicting a proposal in a meeting is normal, expected, and read as engagement. Dutch, French, German and Russian workplace norms sit broadly here, and so does a good deal of engineering culture regardless of nationality. At the other sit cultures where public disagreement with a superior costs the superior face and the speaker standing — much of South Asia, much of Southeast Asia, and much of the Arab world, in different ways and for different reasons. The practical failure is always the same. A manager from the first group presents a plan, invites objections, receives none, and concludes there is consensus. There was no consensus. There was an absence of a mechanism for saying so. **What to change:** stop treating silence as data. The related failure — reading a quiet meeting as agreement — is the subject of [what silence in a meeting actually means](/en/blog/silence-in-a-meeting/). Ask for objections in writing before the meeting, or in pairs during it, or from the most junior person first. All three cost about four minutes and change the information you get. ### How visible hierarchy is expected to be A manager who insists on first names, sits among the team and asks to be challenged is signalling accessibility. That signal is not read identically across the room. For colleagues whose expectation is a visible hierarchy, a manager who declines the role does not become approachable. They become unpredictable — and where authority is ambiguous, the safe strategy is to do exactly what was last instructed and nothing more. The flat manager gets the compliant behaviour they were trying to avoid. The reverse error is equally common. A manager operating with visible authority in a team of Western European professionals will be read as controlling, and the people best able to challenge a bad decision will stop. **What to change:** be explicit about the register rather than assuming it transfers. Saying *I want to be challenged in this meeting and it will not count against anyone* is a sentence that has to be said out loud, and then demonstrated the first time someone tests it. The first test is the whole thing: the team watches what happens to the person who spoke. ### How much context a message carries Some professional cultures put the message in the words. Others put a substantial part of it in the relationship, the setting, and what was not said. In a mixed team this produces two symmetrical complaints. One group finds the other's communication blunt to the point of rudeness. The other finds the first group's impossible to act on. Both are correct about the effect and wrong about the intent. **What to change:** default to explicit for anything that matters, and write it down. This is the single highest-return habit in a multicultural team, because a short written summary of who decided what, by when, corrects simultaneously for indirectness, for hierarchy and for second-language comprehension. It is dull, it takes five minutes, and it prevents most of what this article describes. ## Two structural factors that are not cultural These get attributed to culture and are not. Both are specific to the Gulf, and both change behaviour more than any national difference on the list above. **Residency is tied to employment.** For most of the people in the room, losing the job means leaving the country, moving children out of school, and in many cases interrupting the remittances that support a family elsewhere. This is not a background detail. It is the dominant fact of professional life for a large share of a Dubai workforce, and it makes disagreeing with a manager a materially riskier act than it is in a market with unemployment insurance and portable residency. A manager who reads the resulting caution as passivity, or as a cultural trait, has misdiagnosed it. The behaviour is a rational response to the stakes. The only thing that shifts it is a demonstrated track record that raising a problem is safe — demonstrated, not stated, and over months rather than weeks. **English is a second language for most of the room.** Not an obstacle for most purposes, but it produces one specific and expensive error: fluency gets read as competence. The colleague with the best English in the meeting is assumed to have the best grasp of the problem, and gets the visibility, the client contact and eventually the promotion. Sometimes that is correct. Often it is a measurement of schooling. The corrective is to create channels where the language is not the filter: written input before a decision, small-group work, technical demonstrations. It is also the honest reason we state plainly which languages a session is delivered in — English, French or Spanish — rather than leaving a prospect to discover it. ## Three things that need saying out loud **Perceived fairness is fragile in this market.** Compensation practices in the Gulf have historically varied by nationality for the same role, and teams are entirely aware of it. A manager who cannot control pay bands can still control what they distribute: visibility, difficult assignments, client exposure, credit in front of senior people. Distributing those on any basis that correlates with passport is the fastest way to lose a mixed team. **The calendar is shared and not uniform.** Ramadan shortens the working day and shifts energy to the morning. Colleagues observing it work alongside colleagues who are not. Diwali, Eid, Christmas, Chinese New Year and Orthodox Easter all land somewhere in a Dubai team, and the leave requests that matter most are the ones attached to families in another country — long, planned far ahead, and non-negotiable in practice. Plan the year around them rather than adjudicating them one by one. **Turnover is the norm, not a symptom.** Careers here are shorter and more mobile by design. A team is a rotating group, which means knowledge has to live in documents rather than in people, and a manager's induction process matters more than their retention rate. ## What to do first If you take one action: after every meeting where something was decided, write three lines — the decision, the owner, the date — and send them to the room. It corrects for the colleague who could not say no, for the one who did not catch the fourth sentence, for the one who was waiting to be asked directly, and for the one who assumed the outcome was obvious from context. One habit, four failure modes closed. The motivation side — which follows different rules again in a team where half the room is planning around a family in another country — is covered in [motivating a multicultural team](/en/blog/motivating-a-multicultural-team/).uae-businessuaemulticulturalmanagementleadershipcommunicationhttps://www.abp-consulting.ae/en/blog/who-is-actually-working/https://www.abp-consulting.ae/en/blog/who-is-actually-working/Every team has someone whose own account of their contribution does not match anyone else's. Four versions of it, and the diagnostic question that separates a visibility problem from a real one.Tue, 08 Nov 2022 00:00:00 GMTThere is a conversation that happens in almost every team we work with, usually in the second individual interview of the day. Someone explains, with visible sincerity, that they are carrying more than their share. Two hours later a colleague names that same person as the one who does the least. Both are telling the truth as they experience it. That is what makes the situation hard, and it is why the reflex response — a firmer conversation about effort — usually makes it worse. Four versions of it recur. ## 1. The one who is never not busy Genuinely overloaded, and genuinely the last to leave. The diary is full. The inbox is handled. Nobody, including the person themselves, could describe what this week produced. Activity and output are different quantities. This profile converts a large amount of the first into a small amount of the second, and the fullness of the diary is precisely what conceals it, from everyone and most of all from them. Their working belief is that they are behind because there is too much. Usually they are behind because nothing has been declined in two years. They are also the most demoralised profile of the four when confronted, because the effort is real. Effort is not what is being questioned. **What helps:** not time management. A conversation about what to stop. The practical version is to name the three outputs that matter this quarter and agree, explicitly and in writing, what is being dropped to protect them. This person will not drop anything without permission, because dropping things is what they believe they are being criticised for. ## 2. The one whose work is genuinely invisible Here the team is wrong, and this is the profile most often mishandled. Some of the most valuable work in a team leaves no trace. The client who was about to escalate and did not. The dependency someone spotted three weeks out. The newcomer who was unblocked in a ten-minute corridor conversation. The specification that was argued into shape before it reached the developers. None of it appears in a status report. All of it is noticed only when it stops, by which point nobody connects the deterioration to the person who left. Two forces compound it. Work of this kind is disproportionately carried by people who do not narrate their own contribution — and it is disproportionately carried by the same individuals over time, which is worth a manager's attention on its own. And where part of the team is remote, [proximity bias](/en/glossary/#proximity-bias) adds a straightforward visual correction: presence in the room reads as contribution, absence reads as absence. **What helps:** the manager making the work visible, not the person. Asking someone to advertise their own coordination work puts them in an impossible position. Naming it yourself, once, specifically, in a setting where the team can hear it, changes the collective account in a single sentence. ## 3. The one who works on what they find interesting High output, real competence, and a body of work that only intermittently intersects with what the team needed. The tooling that was rebuilt because the old one was inelegant. The analysis nobody commissioned. The refactor that was necessary but not this quarter. Each piece is defensible in isolation, which is why this profile survives review after review, and why the team's frustration never quite finds an argument. They experience the criticism as philistinism, and they have a point in the narrow sense: the work is often good. It is simply not the work. **What helps:** priorities that exist somewhere other than in the manager's head. This profile self-assigns in the absence of a visible order of importance, and they will keep doing it as long as the order is implicit. Written priorities, reviewed monthly, remove the vacuum. Where this pattern is widespread across a team, the problem is not four individuals, it is that nobody has said what matters most. ## 4. The one whose currency is presence Arrives early, leaves late, is on the messaging tool at eleven at night. Sincerely believes that this constitutes commitment, and is sincerely aggrieved when it is not treated as such. Sometimes this is a workload problem in disguise. Sometimes it is an environment that once rewarded exactly this and has not said that it stopped. Frequently it is a person for whom leaving on time feels like an admission of something, which is a different conversation altogether. What makes it corrosive is the standard it sets. A team that reads hours as virtue penalises everyone with a constraint on their hours, which is not a random subset of the team, and produces the sharpest resentment of the four profiles. **What helps:** the manager naming the measure explicitly and then living by it. If output is the measure, say so, and stop remarking approvingly on late departures. This profile is responding accurately to signals that are still being sent. ## The diagnostic Before responding to any of the four, three questions, in this order. **What was agreed?** If nothing was written down, there is no performance question to answer yet, only a manager's expectation that was never communicated. Start there. **What arrived, and when?** Against the agreement, not against an impression. This is the step that separates the profiles: the invisible worker has delivered, the misdirected one has delivered something else, the busy one has delivered late, the present one has delivered a normal amount over abnormal hours. **Who else knows?** If the outputs are real and the team does not know about them, the gap is yours to close and it is not a performance issue at all. The common error is to skip all three and go straight to a conversation about attitude. Attitude conversations are unfalsifiable, they leave the person with nothing actionable, and they are how a visibility problem becomes a conflict — with the roles described in [four people, one conflict](/en/blog/four-roles-in-a-team-conflict/) assembling around it shortly afterwards. Defining the output rather than policing the effort is the core of the [manager and leader toolkit](/en/training/management/manager-leader-toolkit/), and it becomes non-optional once part of the team is remote.managementmanagementperformanceteam-cohesionfeedbackhttps://www.abp-consulting.ae/en/blog/gen-z-and-baby-boomers/https://www.abp-consulting.ae/en/blog/gen-z-and-baby-boomers/The two ends of a team are described as having incompatible values. In the room, what they actually disagree about is four unwritten rules — and the disagreement is settled by writing them down.Tue, 22 Jun 2021 00:00:00 GMTEvery team of any size now spans forty years of working life, and the two ends of it are routinely described as though they held incompatible values. The older group is said to value loyalty, hierarchy and effort; the younger one meaning, balance and immediacy. Sit in the room and that account does not survive. What the two ends actually disagree about is narrower, more specific, and considerably easier to fix: a handful of rules that were never written down. ## First, the size of the effect Research that compares work values across age cohorts keeps producing the same uncomfortable result: differences between generations are small, and differences between individuals of the same generation are large. A manager who predicts someone's motivation from their year of birth will be wrong most of the time. Two things also get mistaken for generational effects. **Career stage** is the first — much of what is described as generational is simply what the start of a career looks like, and always has. **The deal** is the second, and it is the one that matters. The older rules were not arbitrary. They were the rational response to an arrangement in which an employer offered long tenure, predictable progression and a pension in exchange for patience and availability. Under those terms, staying five years before expecting a promotion is a sound investment. That arrangement has been withdrawn nearly everywhere. Expecting the behaviour that it purchased to survive its withdrawal is the actual error, and it is not a generational one. ## The four rules ### 1. What loyalty means **The older rule:** loyalty is measured in duration. Leaving inside three years says something about the person. **The younger rule:** loyalty is measured in commitment while present. Leaving when the learning stops is not a betrayal, it is a plan. **Where it bites:** in how a departure is treated. A team that treats a resignation as a defection loses the leaver, teaches everyone else to conceal their intentions, and forfeits the returning-employee pipeline that is now one of the cheapest sources of experienced hires. **The explicit version:** say what the deal is. What someone will learn here, over what horizon, and what happens after. An honest three-year proposition retains people longer than an implied twenty-year one nobody believes. ### 2. How often feedback arrives **The older rule:** no news is good news. Feedback is an event, and it is annual. **The younger rule:** silence means my work is invisible, and invisible work is work that will not count. **Where it bites:** in the manager's diary. It is read as neediness. It is not neediness, it is a different calibration of how long is reasonable to wait for a signal, and the older calibration was set by a twenty-year tenure. **The explicit version:** short and frequent beats long and formal. Ten minutes a fortnight, on the work rather than on the person, costs less in total than one annual review and removes almost all of the ambiguity. It also improves the annual review, which stops containing surprises. ### 3. When someone is reachable **The older rule:** availability demonstrates seriousness. The message on Sunday evening is not an imposition, it is how one shows commitment. **The younger rule:** the hours are the hours. Being contactable outside them is a request, not a default. **Where it bites:** hardest for the manager in the middle, who receives the Sunday message from above and forwards it downwards. **The explicit version:** separate sending from expecting. A team rule that messages may be sent at any time but are answered in working hours, unless explicitly marked urgent, resolves most of this. The rule only works if the most senior person observes it, which is the part that usually fails. ### 4. Where authority comes from **The older rule:** authority follows position and seniority. It is granted by the organisation. **The younger rule:** authority follows demonstrated competence. It is granted by the person being led, and it is renewable. **Where it bites:** in the phrase *because I am asking you to*, which lands as legitimate on one side of the team and as an admission that no reason exists on the other. **The explicit version:** give the reason. Not always, and not for everything, but by default. Where the decision is genuinely not open, say that too, which is the honest form covered in [non-violent communication at work](/en/blog/non-violent-communication-at-work/). A manager who explains is not weakening their position, they are refinancing it on terms the whole team accepts. ## What actually resolves it Three moves, in order of effect. **Write the rules down.** Most of this friction exists because each side is following a rule it believes to be self-evident. A team charter of six lines — response times, feedback cadence, how decisions get made, how disagreement gets raised — removes the ambiguity that the generational narrative fills. **Apply them upward.** A rule the senior people exempt themselves from is not a rule, it is a hierarchy with extra steps, and the youngest members of the team will identify that within a week. **Pair them on real work.** Structured intergenerational workshops produce warmth that fades. A shared deliverable with genuine mutual dependence — the experienced colleague holding client history and organisational memory, the younger one holding tools and current practice — produces a working relationship, which lasts. Mutual mentoring works when it is attached to an output and fails when it is attached to a programme. The manager's own posture is what determines whether any of this holds; that is the subject of the [manager and leader toolkit](/en/training/management/manager-leader-toolkit/). Where the team is also split across sites and time zones, the same rules have to be written more explicitly still.managementgenerationsmanagementconflictleadershiphttps://www.abp-consulting.ae/en/blog/self-awareness-tools-compared/https://www.abp-consulting.ae/en/blog/self-awareness-tools-compared/Seven instruments, sold for the same purpose, measuring different things with very different levels of evidence behind them. A comparison of what each is genuinely good for, and where each one should not be used.Tue, 15 Sep 2020 00:00:00 GMTEvery leadership team we work with has already done at least one of these. The usual sequence is that someone encountered a tool at a previous company, found it striking, and brought it in. Nobody compared it with anything. That matters, because the seven instruments below are not seven versions of the same test. They measure genuinely different things, with very different amounts of evidence behind them, and they fail in different ways. Picking one is a question of what you actually want to know. ## The short version | Tool | Measures | Strongest use | Main weakness | | --- | --- | --- | --- | | **DISC** | Observable behaviour, four preferences | Reducing friction fast, adapting a sales or management approach | Describes style only; says nothing about why | | **MBTI** | Cognitive preferences, sixteen types | A shared language for difference, personal reflection | Weak retest stability; forces continuous traits into binaries | | **Enneagram** | Core motivation and core fear, nine types | Understanding a behaviour that genuinely puzzles you | Not psychometrically validated; invites amateur psychology | | **Process Communication** | Communication channels and stress sequences | Predicting and defusing behaviour under pressure | Costly, requires certified facilitation, hard to self-teach | | **Big Five (OCEAN)** | Five personality traits, on a continuum | Research, serious assessment, avoiding pseudoscience | No memorable types; output feels clinical to participants | | **CliftonStrengths** | Talent themes, ranked | Career development, positioning someone in a role | Deliberately ignores weaknesses; proprietary and per-seat | | **Belbin** | Contribution to a team, nine roles | Composing a project team, diagnosing a stuck one | Describes the role, not the person; ratings by peers required | ## Behaviour: DISC Four preferences — Dominance, Influence, Steadiness, Conscientiousness — describing how someone acts at work: how direct, how fast, how much detail, how much relationship before content. Its strength is speed. A group can be using the vocabulary usefully by mid-afternoon on day one, and the adaptation it suggests is concrete: lead with the conclusion for one colleague, with the reasoning for another. It is also the easiest of the seven to apply to someone who has never been assessed, because you are reading observable behaviour rather than a report. Its limit is that it describes the surface. Two people with the same profile can be driven by opposite things, and DISC will not tell you which. A fuller treatment of that boundary sits in [DISC or the Enneagram](/en/blog/disc-or-enneagram/), and a short definition in the [glossary](/en/glossary/#disc). **Use it for:** team friction, commercial relationships, first exposure to self-awareness work. ## Cognitive preference: MBTI Sixteen types built from four dichotomies. Easily the best known of the seven, and the most contested. What it does well is give a mixed group a shared, non-judgemental language for difference — the observation that a colleague needs to think out loud where you need to think alone lands well, and lands quickly. The problems are real and worth stating plainly. The dichotomies cut continuous distributions at the midpoint, so people near the middle are assigned to a side by a small margin and then described as though they were at the extreme. Retest stability is the weakest of the instruments here: a meaningful proportion of people are given a different type when they take it again some months later, which is difficult to reconcile with the idea that a type is a stable attribute. **Use it for:** personal reflection and shared vocabulary. Not for decisions. ## Motivation: the Enneagram Nine patterns, each organised around a core drive and a core fear. It asks why rather than how, and it is the tool that most often produces a genuine change of perspective in a room. It has never been validated as a psychometric instrument, and anyone presenting it as one is overclaiming. We use it as a structured way of thinking about motivation and we say so. Its second risk is proximity to therapy: nine types defined by fears, in a room of colleagues, needs a facilitator who will stop the session becoming amateur analysis of an absent third party. **Use it for:** a recurring pattern nobody can explain, in a team with existing trust. A definition is in the [glossary](/en/glossary/#enneagram). ## Stress: Process Communication Developed by Taibi Kahler, and built around a distinction the others do not make: each type has a preferred communication channel in normal conditions, and a predictable sequence of behaviour when its psychological needs go unmet. The model describes those degradation sequences precisely, in observable terms. This is why it is the strongest of the seven where it matters most. Nobody needs a profile to handle a calm colleague. The value arrives at the moment someone becomes rigid, sarcastic, or unreachable — and Process Communication is the only one of these tools that tells you what to do next, in the moment, in words. Its cost is real: proprietary questionnaires, certified trainers, and a model that is genuinely hard to use from a book. **Use it for:** high-pressure environments, executive teams, roles where a relationship failing under stress is expensive. ## Traits: the Big Five Five dimensions — openness, conscientiousness, extraversion, agreeableness, neuroticism — each a continuum rather than a category. It is the only instrument in this list built from research rather than from a practitioner's framework, and the only one that would be accepted in an academic setting. Of the five, conscientiousness is the trait with the most consistent relationship to work performance across occupations. Its weakness in a corporate setting is presentational. It returns five percentile scores and no memorable type, participants do not repeat it in the corridor afterwards, and a low score on a trait named neuroticism is a difficult thing to hand someone without careful framing. **Use it for:** any context where being defensible matters more than being memorable. ## Talent: CliftonStrengths Thirty-four talent themes, ranked, with the working assumption that development effort returns more when spent on existing strengths than on correcting weaknesses. That premise is also the objection. Some weaknesses are not optional. A manager whose lowest themes are all relational does not get to skip that, and a report that never mentions it is not doing them a service. Used for career direction and for positioning someone in a role, it is genuinely useful. Used as a licence to ignore a development need, it is expensive. **Use it for:** individual development conversations, role design, career moves. ## Role: Belbin Nine team roles describing contribution rather than personality: who generates ideas, who finishes things, who holds the group together, who challenges the consensus. It is the only tool here whose unit of analysis is the team rather than the person, which makes it the right instrument for a specific and common problem: a project team that has four people generating options and nobody closing them. Belbin includes observer assessments alongside self-reporting, which is a real methodological advantage. The caveat is that a role is contextual. The same person completes differently in two different teams, and treating a Belbin role as a fixed identity misses the point of the model. **Use it for:** composing a project team, diagnosing a team that keeps stalling at the same stage. ## How to choose, in one paragraph Ask what the problem is. Friction between people who are trying to cooperate: DISC. Behaviour that becomes destructive under pressure: Process Communication. A colleague whose reactions you genuinely cannot explain: the Enneagram. A team that produces ideas and no output: Belbin. A career conversation: CliftonStrengths. A context where you will be asked to justify the method: the Big Five. A general wish to give a mixed group a common language, with no specific problem to solve: MBTI, on the understanding that it is a conversation opener rather than a measurement. And in every case, the same guardrail. A profile is a hypothesis to test against observed behaviour, not a verdict to explain it away. Nobody gets typed in their absence, individual results belong to the participant, and any group reporting is anonymised and agreed in advance. Those are the terms we work under in [Self-awareness and positive communication](/en/training/communication/self-awareness-communication/) and, applied commercially, in [Consultative selling and negotiation](/en/training/commercial/consultative-selling/).leadershipdiscenneagrammbtileadershipself-awarenesshttps://www.abp-consulting.ae/en/blog/four-roles-in-a-team-conflict/https://www.abp-consulting.ae/en/blog/four-roles-in-a-team-conflict/Two colleagues are said to be in conflict and everyone else describes themselves as a bystander. In practice a lasting conflict needs four roles filled, and two belong to people who feel uninvolved.Tue, 05 Nov 2019 00:00:00 GMTAsk a team about its conflict and you get a stable answer: two names, a shared history, and a general sense that everyone else is watching from a safe distance. That account is almost always wrong, and it is wrong in a way that matters, because it points the intervention at the two loudest people. A conflict between two people does not last. Tempers cool, work resumes, the episode becomes a story. What lasts is a conflict that is being fed. And feeding it requires roles that the two named parties cannot fill on their own. There are four. In most teams they are already cast. ## 1. The one who is right Usually the most competent person in the room, and usually correct on the facts. The specification was ambiguous, the deadline was unrealistic, the decision was taken without the data. All true. Being right is what makes this role so durable. It removes any reason to examine one's own conduct. Every re-litigation of the facts confirms the position, and the manner in which it is asserted, in front of others, repeatedly, is never up for discussion, because that would be changing the subject. The intervention here is not to dispute the facts. It is to separate two questions that this person has fused: *was I right?* and *did the way I said it work?* Handled together, the second question always loses to the first. Handled apart, most people concede the second readily. They have often noticed. ## 2. The one who keeps the peace The most sympathetic figure, and the most consistently underestimated. They cut the tension with a joke, they reformulate an attack into something milder, they catch each party afterwards to say the other did not mean it. Every one of those acts is well intentioned and each one removes the pressure that would otherwise force a resolution. Conflict resolves when the cost of continuing exceeds the cost of stopping. The peacekeeper's entire function, in practice, is to lower the cost of continuing. They are also the person who suffers most, because they absorb the discomfort that the group has stopped feeling. Burnout in a team in conflict very often arrives here first, and not in either of the two people who are arguing. Telling them to stop does not work. What works is giving them a different job: they are usually the only person both parties trust, which makes them useful in preparing a confrontation rather than in preventing it. ## 3. The referee nobody appointed Someone in the team has become the place where the conflict is adjudicated. People bring them a version, they give a verdict, the verdict circulates. They hold no mandate and they are almost never the manager. This is the most damaging role, and the hardest to see, because it looks like being helpful. Three things go wrong. Verdicts are issued on one side's account of events. They are issued in corridors, where nothing is recorded and nothing can be appealed. And each verdict gives one party a reason to stop negotiating, because a ruling has already been obtained. There is also a structural consequence: if arbitration happens informally, the manager's own decisions become one opinion among several. Authority that is not exercised does not stay idle, it relocates. The move here is not to confront the referee, who will experience it as punishment for helping. It is to make the formal channel faster and more useful than the informal one. People take the shortest path to a decision. Make the official one shortest. ## 4. The one who has already left The quietest person in the team, and the one nobody lists when the conflict is described. They stopped contributing to the argument some time ago, which is generally read as maturity. They have not risen above it. They have concluded that this team is not a place where saying something changes anything, and they have redirected their effort accordingly: precise on their own deliverables, absent from anything collective, courteous, unreachable. They are, in most cases, the first to resign, and the resignation is experienced as a surprise. This is where the actual cost of an unresolved conflict sits. Not in the two people arguing, whose energy is at least still in the room, but in the ones who have quietly stopped investing it. In a team of eight, two people arguing and three disengaged is a majority of the team out of action. ## What this changes about the intervention The reflex is to sit the two protagonists down together. Done first, it fails, because the roles reassemble the following week around the same people. What works is close to the reverse. **Start with the four, separately.** Each person hears which role they are filling, described in behaviour rather than character, and what it produces. Most recognise it. Nobody chose it deliberately. **Rule on the substance yourself, early.** If there is a factual question at the heart of it — a scope, a priority, a division of responsibility — decide it and say so. A conflict left open because the underlying decision was never taken is not a relational problem, and no amount of facilitation will fix a missing decision. **Then bring the protagonists together**, with the substantive question already settled, so the conversation is about how they work rather than who was right. The preparation for that conversation is exactly the discipline described in [non-violent communication at work](/en/blog/non-violent-communication-at-work/): observations rather than interpretations, consequences rather than emotions. **Speak to the one who has left, last and individually.** They will need evidence, not intent. Something has to visibly change before they re-engage, and they are the slowest to come back. Where this sits in our work: the individual behaviours are covered in [Self-awareness and positive communication](/en/training/communication/self-awareness-communication/), the collective version in a [Team coaching programme](/en/training/coaching/team-coaching-programme/), and the manager's own posture, which is what usually determines whether the roles form in the first place, in the [manager and leader toolkit](/en/training/management/manager-leader-toolkit/).managementconflictmanagementteam-cohesionleadershiphttps://www.abp-consulting.ae/en/blog/non-violent-communication-at-work/https://www.abp-consulting.ae/en/blog/non-violent-communication-at-work/Most people leave a session on the method convinced, and stop using it within a fortnight. The method is sound; the version taught for personal relationships does not transfer to an office as it stands.Tue, 09 Apr 2019 00:00:00 GMTNon-violent communication is one of the few methods that people find genuinely convincing in a training room and almost never use afterwards. That gap is not a motivation problem. The method was built for personal relationships, and the version that circulates in companies is usually the personal one, unadapted. Four steps, in the original form: state the **observation**, name the **feeling** it produced, identify the **need** underneath, formulate a **request**. Three of those survive an office intact. One does not, and the failure of that one takes the other three down with it. ## The step that transfers best The first one, and it is worth the price of the method on its own. An observation is what a camera would have recorded. An interpretation is what you concluded from it. Almost every workplace dispute we are called into is built on interpretations exchanged as though they were facts. > *You are not committed to this project.* That is an interpretation. It is unprovable, and the only available responses are denial or capitulation, which is why the conversation goes nowhere. > *The last three project meetings were rescheduled by you, twice on the morning > of the meeting.* That is an observation. It cannot be denied, so the conversation has to move on to why, which is where it was supposed to go in the first place. Separating the two is harder than it sounds, because interpretations arrive feeling like perceptions. The test is simple: could someone who dislikes you disagree with this sentence? If yes, it is an interpretation. ## The step that fails The second step asks you to name what you felt. In a couple, that is the heart of the method. At work it runs into two problems. The first is register. *I felt hurt when you interrupted me in the steering committee* is a sentence most professionals will not say, and forcing it produces a stilted performance that everyone in the room can hear. The second is heavier. When a manager tells a subordinate what they feel, that is not a disclosure. It is information about the mood of the person who controls their appraisal. The listener stops processing the message and starts managing the manager. The step designed to create symmetry produces the opposite. What works in its place is stating the **consequence** rather than the emotion. Not *I felt disrespected*, but *I stopped raising points in that meeting, and two issues went unmentioned as a result*. It carries the same weight, it is verifiable, and it does not require either person to perform vulnerability. Between peers, with existing trust, the original step works fine. It is the vertical use that breaks, and most workplace uses are vertical. ## The request that is not one The fourth step is a request. The method is explicit that a request is only a request if no is an acceptable answer. Most workplace requests fail that test. A manager asking a team member to take on a file is not making a request. Wrapping an instruction in the grammar of a request does not make it one. It makes it an instruction the other person is now not allowed to recognise as such, which is worse than the plain version. The honest move is to say which one you are making. *This one is not negotiable, and I would rather tell you that than pretend you have a choice* costs nothing and buys a great deal. Where there genuinely is latitude, say where the latitude ends. People calibrate their effort against the boundaries they can see. The same logic applies in a commercial setting, where a request disguised as a question is one of the fastest ways to lose a buyer's trust. That is ground we cover in [Consultative selling](/en/training/commercial/consultative-selling/). ## A worked example A deliverable arrives two days late, for the third time this quarter. **The version that starts a fight.** *You have a real problem with deadlines and it is starting to affect the whole team.* **The version that sounds like a technique.** *When you delivered late, I felt frustrated, because I have a need for reliability, and I would like to request that you deliver on time.* This is the version that makes people give up on the method, and rightly. **The version that works.** *The last three deliverables came in two to three days after the agreed date. I have been rebuilding the downstream schedule each time, and last week the client noticed. I want to understand what is happening before we agree what changes.* Observation, consequence, and an opening, with the request deliberately held back until the cause is known. Three sentences, no vocabulary anyone has to be trained in. ## Where it does not apply The method assumes both parties are acting in good faith and that the problem is one of expression. When that assumption is false, applying it does harm. Harassment, discrimination, safety breaches and deliberate sabotage are not communication failures and do not have communication remedies. Neither does the colleague who has understood you perfectly and has decided their interests lie elsewhere. Those situations need a procedure, a record and, often, someone with authority. A manager who keeps reformulating in the face of bad faith is not being patient. They are letting a situation run. Recognising which of the two you are in is the actual skill, and it is where the conflict and aggression work in [Knowing yourself to communicate better and stand your ground](/en/training/communication/assertiveness-without-authority/) starts. The phrasing work comes after, in [Self-awareness and positive communication](/en/training/communication/self-awareness-communication/), where the point is to prepare a conversation rather than to memorise a script.communicationcommunicationconflictfeedbackassertiveness