ABP Consulting is a French management training and coaching firm, delivering professional development programmes in Mauritius.https://www.abp-consulting.mu/en-MUhttps://www.abp-consulting.mu/en/blog/horaire-decale-et-management/https://www.abp-consulting.mu/en/blog/horaire-decale-et-management/A team whose day is set by Paris, London or Bangalore is not living with an organisational constraint but with a decision constraint. The two are not treated the same way.Sat, 12 Sep 2026 00:00:00 GMTA team in Ébène starts at ten because its European client starts at eight. Another finishes at eleven at night because it serves a US time zone. A third lives on two windows, India in the morning and Europe in the afternoon, which leaves two hours in the middle when work can actually happen. That is ordinary life across a substantial part of Mauritian service activity, and most managers treat it as an organisational constraint. It is not one. It is a decision constraint, and that shift changes everything about what needs doing. ## What the gap actually costs Fatigue is visible, so it gets talked about. It is not the main cost. The main cost is waiting. In a team that shares its hours with its client, a question is asked and settled within the minute. In a team whose shared window is three hours, a question arriving after the window stays open until the next day. The work does not stop: it proceeds meanwhile, on an assumption, and sometimes has to be redone. Multiply that by the number of questions in an ordinary day and you have the real cost of the gap. It appears in no dashboard, because it takes the form of work redone rather than work not done. ## The first decision is not a rota Hence the most useful conclusion in the whole subject: before building a schedule, a manager working across time zones has to draw up a list. **Which decisions get taken without them, and without the client?** The exercise is uncomfortable because it forces you to name thresholds: up to what value, up to what deviation from the specification, up to what consequence for the end client. It is uncomfortable too because it exposes that some decisions have always travelled upwards for no real reason, out of habit. The four levels of delegation worked on in the [manager-leader toolkit](/en/formations/management/outils-du-manager-leader/) are the instrument for building that list. But there is no alternative. A team without that list waits, and waiting is exactly what the gap makes expensive. A team that has it works while the other sleeps, which is the only genuine advantage of the arrangement. ## Protecting the shared window Overlapping hours have an unfortunate property: they fill themselves. Since it is the one moment when everybody is available, every meeting settles there, and the window becomes the worst time of day to produce anything. The rule that works is a simple filter. Put in it only what requires a real-time exchange: a decision to be taken together, a trade-off, a complex explanation where the questions arrive as you go. Everything else — progress, information, sign-off on a compliant deliverable — is written, and read during the hours the other team is not there. The corollary is worth saying: **the written record is the most profitable management tool a time-shifted team has**. It works through the other side's night. A manager who spends fifteen minutes at the end of the local day writing what was decided and what is waiting on an answer buys a full cycle of advance. ## Who carries the gap Here is where teams degrade quietly. The burden of a shifted schedule never distributes itself: it falls on the people who agree, and the people who agree are usually the most committed, the youngest, or those with the least means to refuse. After a year, two or three people are covering every late meeting. They do not complain — that is the mechanism itself — and then they leave. Three rules are enough to prevent it, provided they are written down. An explicit rotation of the uncomfortable slots. A ceiling: nobody takes more than a set number of out-of-hours meetings per month. And time back that does not have to be asked for, because what has to be asked for is not asked for by the people who need it most. ## The warning sign There is only one to watch, and it is easy to miss: **the late meeting that becomes normal without ever having been decided**. It starts as a justified exception — a launch, a crisis, an important client. Then the slot stays in the calendar because it is convenient for the other side. Six months later it is part of the job, with no conversation having taken place and with it appearing in nobody's job description. Where the team is multilingual as well, the two subjects compound and are best handled together. The question to ask every three months is therefore precise: which out-of-hours meetings exist today, and which of them was ever actually decided? The gap between the two lists is the measure of the drift.managementmauritiusmanagementleadershiphttps://www.abp-consulting.mu/en/blog/le-oui-qui-ne-veut-pas-dire-oui/https://www.abp-consulting.mu/en/blog/le-oui-qui-ne-veut-pas-dire-oui/Leaving a meeting with everyone's agreement is more often a bad sign than a good one. It is almost never bad faith: it is a problem of process.Sat, 12 Sep 2026 00:00:00 GMTA manager announces a reorganisation of their department. They explain, they answer two or three questions, they ask whether everyone is on board. Nobody objects. They leave the meeting thinking it went well. Three weeks later, nothing has changed. Deadlines slip, the old habits hold, and in a corridor conversation they discover that part of the team had considered the decision unworkable from day one. They conclude there is a commitment problem. That is almost always wrong. ## Nobody lied Surface agreement is not a collective lie. In most cases everyone said the only thing available to them at the moment they were asked. Three things make "no" unavailable in a meeting. The first is the order of speaking: once the senior person has given their view, and especially once they have defended it, the discussion is closed before it opens. Contradicting is no longer discussing a proposal but opposing a person, which is a different act and carries a different price. The second is the presence of colleagues. An objection raised one to one is a contribution; the same objection raised in front of twelve people is a position, and it commits whoever voices it well beyond the subject at hand. The third is particular to Mauritius, and rarely named. Hierarchical distance is respected here, and it is respected in silence. Someone who thinks a decision is poor will often consider that saying so publicly is not their place — not out of fear, but out of a convention of respect that is not irrational and that nobody is going to abolish with an invitation to speak freely. On top of that, in many teams, the meeting is held in a language people follow easily but argue in less willingly. The cost of objecting rises again. ## Disagreement does not disappear, it relocates This is the most underestimated part. A disagreement that could not be voiced before the decision does not evaporate. It resurfaces elsewhere, in forms the manager does not connect back to the meeting: - deadlines that slip with no precise explanation; - the instruction followed exactly to the letter and never beyond it; - repeated technical questions which, taken together, say the project makes no sense; - the informal version circulating in the corridor, which is the only place you hear what people actually think. It is also what makes reorganisations fail. Each of those signals costs time. Together they cost far more than the ten minutes a real discussion would have taken. ## Six devices that produce the objection What works is not exhortation. Nobody speaks up more because they were told speech is free. What works is procedural. **Have people write before they talk.** Two minutes, everyone notes the two obstacles they can see. Then the notes are read out. A written objection has already come out; saying it aloud has become much cheaper. **Hold your own view back.** The senior person speaks last, without exception. It is the cheapest measure and the hardest to sustain. **Change the question.** "Any questions?" never gets an objection. "What could stop this working?" almost always does, because it asks for expertise rather than for opposition. **Assign the objector role.** One person is charged, for this meeting, with finding what will not hold. With the role assigned, contradicting costs nothing socially — it is what they were asked to produce. **Start with the least exposed.** Ask the least senior or most recently arrived people first. Once the department head has spoken, nobody is going back. **Check by having it said back.** Ask two people to state, in their own words, what they are going to do and in what order. It is the only reliable test of understanding, and it surfaces the disagreements that "that's clear" had covered over. ## What you have to accept in exchange These devices work, and they have a price: meetings become less pleasant. You hear objections, some badly worded, some poorly founded. They have to be received without being treated as attacks, including the ones that call the manager's own work into question. Holding that requires a frame set beforehand, which is what the core programme on the [manager-leader toolkit](/en/formations/management/outils-du-manager-leader/) works on. That is the real condition for the whole exercise. A team always tests once: it raises a serious objection and watches what happens to the person who raised it. If the response is defensive, the process is dead and will not restart. If nothing unpleasant happens, the rest follows on its own.managementmanagementleadershipcommunicationmauritiushttps://www.abp-consulting.mu/en/blog/manager-en-trois-langues/https://www.abp-consulting.mu/en/blog/manager-en-trois-langues/A Mauritian team routinely works in three languages without anyone having decided to. Most managers only notice the subject the day a clear decision produces nothing.Sat, 12 Sep 2026 00:00:00 GMTA team meeting in Ébène opens in French because the manager opened it in French. Ten minutes in, two people settle a technical point between themselves in Kreol, because it is quicker. A document arrives, it is in English, and the discussion moves into English for as long as it takes to read it. Nobody decided anything, and everybody followed. That is the ordinary experience of managing in Mauritius, and most managers only identify it as a subject the day a decision they believed was clear produces nothing. The temptation then is to make it a general explanation: "it's a language problem". Sometimes true, and often convenient. ## Following is not being able to contradict The gap that matters is not between those who understand and those who do not. In a Mauritian professional setting, almost everyone understands. The gap is between those who can object and those who can only nod. Arguing in a language requires a considerably higher level than following one. You have to qualify, come back on what you have just said, find the phrasing that expresses disagreement without attacking — and do it in real time, in front of colleagues, sometimes in front of a superior. Someone perfectly comfortable receiving an instruction in English can be unable to say, in that language and at that moment, "I don't think this will work, and here is why". What the manager gets instead is a silence they read as agreement. It is the most expensive mechanism in the whole subject, and it is invisible: nothing happens in the meeting, everything happens three weeks later. The rule that follows is easy to state and uncomfortable to apply: **choose the language in which the least fluent participant can still contradict**, not the one the group understands on average. It is uncomfortable because it sometimes means running a meeting in French when everyone "speaks English", or the reverse. ## Kreol is not a lapse in professionalism There is a reading of Kreol as the language of the informal — tolerated, not encouraged. It misses what the language actually does: it is the one in which a misunderstanding gets recovered fastest, and the one in which a technical move is explained without detour. A team leader who switches for two minutes into Kreol to explain why a procedure exists is doing their job. Banning it in the name of professionalism means removing the most effective tool from the box. The real question is not permission but who is in the room. The same switch that brings two people together puts the colleague who does not speak Kreol outside the conversation — an expatriate, a recent arrival — and it does so without anyone noticing, because the exclusion takes the form of a warm exchange. ## Written English becomes a promotion criterion nobody decided on Here is the most serious effect, and the least discussed. In many Mauritian organisations, a share of the documents that travel upwards — a board paper, a note to the regulator, correspondence with a parent company — are written in English. The people who write them become visible. The people who do not stay competent and invisible. After a few years, the management line has been assembled by selection on a writing skill that nobody ever put in a job description or assessed as such. That is not necessarily unjustified: if the role involves writing to the regulator, the skill counts. What is a problem is that it operates without being stated. A manager who wants to correct it has two immediate levers: name the skill explicitly where the role genuinely requires it, and stop routinely handing the drafting to the same person on the grounds that they write better. ## What language does not explain One last caution, and it is worth as much as the rest. Language is an explanation that is available, visible, and politically comfortable: it implicates nobody. It therefore attracts problems that are not its own. Three sources of friction are commonly confused in a Mauritian team: - **language** — the person does not have the means to express what they think in the register being asked for, what the glossary calls [code-switching](/en/glossaire/); - **hierarchical distance** — the person has the means, in any of the three languages, and considers that it is not their place to say it; - **the person** — the disagreement is about the substance, and would be exactly the same in a monolingual team. All three produce the same silence. They do not call for the same response, and treating the second as a language problem guarantees it is never resolved: you will translate documents for two years while nobody speaks up any more than before. [Individual coaching](/en/coaching/) is sometimes the right place to tell the three apart, when the manager is themselves part of the problem. The test is easy to run. Ask the same question one to one, in the person's language of comfort. If the objection comes out, it was available: language was not the obstacle. If it still does not come out, the subject is elsewhere.mauritian-businessmauritiusmanagementcommunicationleadershiphttps://www.abp-consulting.mu/en/blog/retenir-quand-lailleurs-recrute/https://www.abp-consulting.mu/en/blog/retenir-quand-lailleurs-recrute/A Mauritian employer will not win a salary comparison against an Australian or Canadian recruiter. What decides the outcome sits elsewhere, and much earlier than people think.Sat, 12 Sep 2026 00:00:00 GMTA department head learns that one of their best people has had an offer. It comes from Australia, Canada, France or Dubai, and it is half again what they can put on the table. They ask their leadership for headroom, get part of what they asked for, and make a counter-offer. The person stays. They leave eight months later. ## Why the salary comparison is lost before it starts This is the particularity of the Mauritian market for qualified profiles, and it is worth stating plainly: **your competitor is not the company next door**. For an experienced accountant, a developer, a floor manager or an engineer, the candidate's real alternative is abroad. One strategic consequence follows that many employers have not drawn. Matching local market salaries does nothing against that competitor: the local market is not the reference point of the person doing the comparing. And matching the overseas market is impossible, because the company's cost structure does not allow it. Staying on that ground therefore means losing an auction expensively. You have to change ground — and change it before the offer arrives. ## The decision is not taken when the offer arrives This is the most useful point in the whole subject. The offer is the visible moment; it is almost never the moment of decision. When someone accepts a role abroad, they usually began thinking about it twelve to eighteen months earlier, and the reason for that shift is almost never salary. It is the accumulation of twelve months in which nothing visible happened: no change of remit, no training, no conversation about what comes next, no feedback beyond an annual appraisal dispatched in forty minutes. When the offer arrives, it does not create the wish to leave. It supplies the occasion for a departure already decided. That is also why the counter-offer fails: it answers the wrong question at the wrong moment. ## Seven levers that genuinely weigh These levers are the subject of a two-day programme: [non-financial motivation levers](/en/formations/management/leviers-de-motivation-non-financiers/). **Prospect.** Knowing what could change in your work within a year, and by what route. It is the most powerful lever and the cheapest. Most people are not asking for a guaranteed promotion: they are asking to know whether the subject exists at all. **Real autonomy.** Not "we trust you", but specific decisions taken without asking permission. The test: name three decisions the person takes alone. If you cannot find three, they have no autonomy, whatever they have been told. **Recognition at the right moment.** Precise feedback on the day the work was done is worth more than a general compliment at year end. Precision matters more than frequency: "what you said changed the outcome of Tuesday's meeting" lands; "you're doing good work" does not land at all. **Control over your own time.** On an island where the Curepipe–Port Louis run at peak hour weighs on a whole day, flexible hours are not a cosmetic benefit: they hand someone back two hours a day. **Skill gained.** Serious training, a new responsibility, a cross-functional project: these increase the person's value. Some employers hesitate, on the grounds that it will make leaving easier. True — and the alternative, offering nothing, makes them leave sooner. **The direct manager.** This is the factor whose effect is best established and most often treated as a fixed variable. People rarely leave a company; they leave their immediate manager. Training the management line is a retention investment, even when nobody calls it that — which is what the [manager-leader toolkit](/en/formations/management/outils-du-manager-leader/) is for. **Proximity to family.** This one is specifically Mauritian and almost nobody puts it into the conversation. Leaving means leaving an extended family, a network, a place. It is not an argument to use against someone — "you'd be leaving your parents" would be contemptible — but it is a reality the person already has in their own balance, and it makes the other levers more decisive here than they would be elsewhere. ## Three things that have no effect **The counter-offer after the resignation.** Covered above. It buys time and damages the pay structure. **Generic collective perks.** The fruit basket, the annual outing, the subscription nobody needed. They are not harmful; they simply have no bearing on the decision to stay, and they consume a budget that would have funded useful training. **Talk of loyalty.** Telling someone they owe something to the company that trained them is the surest way to accelerate their departure, with resentment added. Training is an investment by the employer, not a debt owed by the employee. ## What to do this week One thing, and it needs no budget. Take the three people whose departure would cost you most — and if you want to know what your team actually thinks of your management, a 360° is the only instrument that says so without softening it, and ask each of them, one to one, two questions: what has changed in your work over the past year, and what would you want to change in the year ahead. If you have no answer to the first, you already know the risk. If the second produces a specific request, you have twelve months to answer it — which is far more than the time you will have on the day an offer arrives.mauritian-businessmauritiusmanagementleadershiphttps://www.abp-consulting.mu/en/blog/saison-cyclonique-et-continuite/https://www.abp-consulting.mu/en/blog/saison-cyclonique-et-continuite/A cyclone warning is not an unforeseen event: it is foreseeable six months a year. What costs money is not the interruption but discovering at seven in the morning that nobody knows what to do.Sat, 12 Sep 2026 00:00:00 GMTA manager gets a message at twenty to seven in the morning. The warning has moved to class III. They check their phone, they call their leadership who are not answering yet, they write their team an instruction they will have to correct an hour later. In the meantime half the team has set off and the other half is waiting at home, not knowing whether their day counts. This will happen another three or four times before April. And again next year. ## A recurring constraint is not an unforeseen event That distinction settles most of the subject. An unforeseen event is one whose occurrence could not be anticipated. A cyclone season is not unforeseen: it returns every year, over the same months, with a graded warning system everyone knows. A recurring, predictable event belongs to preparation, not to reaction. Handling it by reaction is a choice — rarely a conscious one — and it is that choice which costs, far more than the interruption itself. The lost day is visible, so it gets counted. What does not get counted: the hour spent reaching everybody, the contradictory instructions in circulation, the people who set off for nothing, and the conversation with the client where you announce a delay without a restart date to offer. ## The one-page protocol What is needed is not a forty-page business continuity plan. One page is enough, written in October, and it answers five questions. **Who decides.** One named person, one designated deputy. It is the most important point and the most often vague. With no owner for the decision, each manager rules for their own area and the company issues three different instructions on the same morning. **By what time.** A cut-off before which the decision is communicated — half past six, say — so that nobody sets off while waiting for information. **Through which channel.** One only, known to everybody, tested once before the season. Work email is the worst choice: nobody reads it at six in the morning, and it assumes connectivity. A messaging group works, provided everyone is actually on it and the test has been run. **Who works remotely and who stops.** By name where possible, by role otherwise. The reachability rules and rituals that implies need deciding in advance. It means having checked in advance what is doable from home — and accepting that for part of the team the answer is no. **What does not get caught up.** The counter-intuitive point, and the most useful. A team that tries to recover everything accumulates a debt that weighs on the following weeks. Deciding calmly which activities can slip without consequence avoids deciding it under pressure, when the temptation is to hold everything. ## What gets settled at booking For anything scheduled — a course, a seminar, a trip, a meeting with people travelling in — the postponement clause is agreed at signature, not on the morning of the warning. That applies to our own sessions: every [course](/en/formations/) booked in this window comes with a postponement clause agreed at signature. Three lines are enough: in which cases postponement applies, with what notice it is confirmed, and at what cost. Does a session interrupted on day one resume at the next module or from the beginning? That question has a simple answer when asked beforehand and becomes a dispute when asked afterwards. Few organisations do this, and the argument against is always the same: it invites bad luck, or it reads as negative in a proposal. In practice a provider who raises it unprompted signals that they know the ground. ## The human point One last element, and it is not logistical. A warning does not weigh the same on everybody: it depends on whether you have children whose school closes, an elderly parent at home, an exposed house, or a route through an area that floods. The most constrained people are also, almost always, the ones who will ask for least. They will come in, or they will manage in silence, and the manager will learn nothing. A change of rules announced in October is received; the same one announced on the morning of a warning is not. That is the practical reason — not the moral one — why an explicit rule beats case-by-case flexibility. Flexibility granted on request benefits those who ask. A written rule benefits everybody, including the people who will never say they needed it.managementmauritiusmanagementleadershiphttps://www.abp-consulting.mu/en/blog/un-marche-ou-tout-le-monde-se-connait/https://www.abp-consulting.mu/en/blog/un-marche-ou-tout-le-monde-se-connait/The small market is usually summed up as one advantage: the network. That is half the story. A market where everything is known also changes the arithmetic of every decision taken in haste.Sat, 12 Sep 2026 00:00:00 GMTIn any given sector in Mauritius, the people who decide on a services purchase would fit around one meeting table. Many were educated at the same institution, cross paths in the same professional associations, and know who has worked for whom. The usual conclusion drawn from this is the flattering one: the network matters. True, and half the story. The other half is that a market where everything is known does not only change how you find clients: it changes the economics of every decision taken in haste. ## Reputation arrives before you do In a large market, a salesperson can force a deal and disappear into the crowd: the next buyer will know nothing. In a narrow market, the next buyer has already asked. That completely inverts the arithmetic of pressure techniques. They are usually judged on an ethical criterion, which lets the people who use them call themselves pragmatic. The problem is that they are not pragmatic: in a market where the number of serious buyers is finite, each damaged relationship removes a share of the total. A salesperson who wins three deals by forcing and loses five they never saw coming has done a poor piece of business, and will never know it, because deals lost that way do not announce themselves. It is why the [negotiation course](/en/formations/commercial/vente-conseil/) teaches no pressure techniques: in this market they do not pay. The same reasoning applies to the quotation that moves between the conversation and the document, to the deadline promised without belief, and to the problem you hope the client will not notice. ## Parting with someone is a commercial act Here is the least anticipated consequence. In a market this size, a company's former employees make up a significant share of the people it will be dealing with in future. The person who leaves your department this year will, in five years, be a manager at a potential client, perhaps at a competitor, perhaps at an influencer in your market. Their memory of how they left will weigh on a decision you will never connect back to that departure. This is not an argument for keeping everyone, which is impossible. It is an argument for handling the exit as carefully as the entry: a notice period worked properly, a handover organised, an honest conversation about why they are leaving. These are management gestures, and they have a deferred commercial return that nobody measures. [Consultative selling](/en/formations/commercial/vente-conseil/) and management meet here more than people expect. ## The recommendation, and the wrong moment to ask In a market where people check before they buy, a recommendation is worth more than a campaign. That much is agreed. What is said less often is that almost nobody asks for one at the right moment. The right moment is not year end, nor the contract renewal, nor the moment you need references for a tender. It is **just after a result**, when the client has just seen something happen and is able to say precisely what. A recommendation requested six months later produces a general sentence of no value. Requested on the day the client says "that worked well", it produces a fact — and a fact is the only form of social proof that holds in a market where your contact can check. ## The real drawback: nobody says anything It is worth ending on what the genuine cost of a small market is, and it rarely appears in enthusiastic accounts of networking. When everyone knows everyone, everyone spares everyone. A mediocre supplier is not told; they are simply replaced without explanation. A manager whose practice is poor does not find out, because their peers will not tell them and their team has even less reason to. A bad professional habit can run for fifteen years without meeting a single candid contradiction. That is why the arrangements that produce honest feedback matter more here than elsewhere: a genuinely anonymous 360°, a peer group outside your own company, an end-of-engagement conversation that asks something specific rather than for a general view. They are not a large-company luxury. In a market where politeness is the norm, they are the only places where anything gets learned.commercialmauritiuscommercialleadership