ABP Consulting is a French management-training and coaching firm delivering professional development programmes in Singapore.https://www.abp-consulting.sg/en-SGhttps://www.abp-consulting.sg/en/blog/the-yes-that-does-not-mean-yes/https://www.abp-consulting.sg/en/blog/the-yes-that-does-not-mean-yes/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.Sun, 13 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 conversation at the pantry 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 sharper in Singapore than many managers arriving here expect. Seniority is respected, and in a great many teams it is respected in silence. Someone who thinks a decision is poor will often consider that saying so in the room 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, the meeting is almost always held in English, which nearly everyone follows easily and which, for a large share of the room, is a second or third language. Following a discussion and arguing in it are not the same skill. 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 a side chat, 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 "can, no problem" had covered over. ## What you have to accept in exchange These devices work, and they have a price: meetings become less comfortable. 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/training/management/manager-leader-toolkit/) 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.managementmanagementleadershipcommunicationsingaporehttps://www.abp-consulting.sg/en/blog/one-language-many-rulebooks/https://www.abp-consulting.sg/en/blog/one-language-many-rulebooks/A shared working language makes a multinational team look more aligned than it is. Four gaps that survive fluency, and what a manager can do about each.Fri, 11 Sep 2026 00:00:00 GMTManagers who arrive in Singapore from a single-culture workplace often say the same thing after a few weeks: the team is easier than they expected. Everyone speaks English, meetings run smoothly, nobody seems lost. A few months later the picture is less simple. Deadlines were understood differently. A problem that one person flagged clearly — in their own terms — was not heard as a problem at all. Two colleagues who never argue in meetings have stopped working together. None of this is about language in the narrow sense. It is about everything the shared language makes it easy to overlook. ## Fluency is not alignment When a team visibly struggles to understand each other, people check. They repeat, they write things down, they ask. When everyone is fluent, nobody checks, because there is no obvious reason to. That is why the most fluent multinational teams are often the ones where misunderstandings run longest before anyone notices. The same sentence can be read three ways in the same room. "Let's try to have it by Friday" is a firm commitment to one colleague, a hope to another, and a polite way of saying "not urgent" to a third. Nobody mistranslated anything. ## Four gaps that survive a shared language **Hierarchy: who speaks first, and who speaks at all.** For some colleagues, disagreeing with a senior person in a meeting is part of doing the job well. For others it is a breach of respect that they would only consider one to one, if at all. Both are normal; a meeting run as if only one of them existed will hear only half the team. The mechanics of that are covered in a separate article on [the yes that does not mean yes](/en/blog/the-yes-that-does-not-mean-yes/). **Directness: what counts as clear, and what counts as rude.** Feedback that one person experiences as refreshingly straightforward, another experiences as a public humiliation. The reverse is just as costly: a carefully softened correction that the recipient simply does not register as a correction. Adjusting the delivery without diluting the message is a skill, and it is the core of [Self-awareness and positive communication](/en/training/communication/self-awareness-and-positive-communication/). **Time: what a deadline means.** A date can be a commitment, a target or an opening position. Teams rarely say which, and each member fills the gap with the convention they grew up with professionally. **Bad news: who delivers it, and how.** In some working cultures a problem is raised the moment it appears. In others it is raised only once there is a solution to go with it, or passed upward through someone more senior. A manager who has not made the route explicit discovers problems late — and often concludes, wrongly, that someone was hiding them. ## Passports are a poor guide to people The temptation, once these gaps are visible, is to map them onto nationalities. It is the wrong move. The variation inside any one nationality is far larger than the averages suggest, people who have worked in several countries carry several rulebooks at once, and colleagues quickly notice when they are being managed as a stereotype. A more reliable reading grid is working style. Tools such as DISC give a team a way of describing its friction in terms of how people prefer to decide and communicate — which is usually more accurate than nationality, and always less charged. The one-day [DISC course](/en/training/communication/disc-reading-and-adjusting/) is built for exactly that use. ## What a manager can actually put in place None of this needs a cultural briefing. It needs a handful of explicit rules, agreed with the team and written down: - **How we disagree.** For example: objections are written before a decision is discussed, and the senior person speaks last. - **What a date means.** "By Friday" means delivered by Friday at 6 pm unless someone says otherwise by Wednesday. - **How a problem is raised.** Early, to whom, and with or without a proposed fix. - **How a decision is checked.** Two people restate it in their own words before the meeting closes. Add one practical habit: plan the team's calendar with every relevant festival and public holiday in front of you, so that no one has to ask for an exception for something that should never have been one.singapore-businessmanagementmulticultural-teamscommunicationsingaporehttps://www.abp-consulting.sg/en/blog/keeping-your-people-in-a-tight-labour-market/https://www.abp-consulting.sg/en/blog/keeping-your-people-in-a-tight-labour-market/When a competitor can always outbid you, retention stops being a salary question. What a manager can do in the year before the resignation letter, not after.Wed, 09 Sep 2026 00:00:00 GMTA manager in a Singapore firm learns that one of their best people is leaving. The new employer is offering more money, and it is a good firm. The manager wonders whether they could have matched the salary. Usually they could not have, and usually that was not the real question. ## The comparison you will not win Singapore's labour market is tight for qualified people, and pay for those profiles is benchmarked across the region. For almost any role, somewhere in the city there is an employer willing to pay more — often a short commute away. A retention strategy built on outbidding everyone else runs out of money before it runs out of competitors. That is not a reason for despair. It simply moves the question to the things that are not decided by the market: how the job feels, where it leads, and how the person is treated by the one individual they deal with every day. ## Why people actually leave When people who have left are asked honestly why, the money is rarely the whole answer. The same few reasons recur: - **No visible next step.** Not a promise of promotion — a credible picture of what they will be doing, learning or responsible for in twelve months. - **Feedback that is too rare.** Hearing nothing for months and then receiving a rating once a year. - **Recognition that arrives too late,** or only in the annual review. - **A working relationship with the manager** that has quietly become costly. - **No control over their own time,** particularly when a competitor offers flexibility the current employer treats as an exception. Every item on that list sits within a manager's reach, and none needs a budget. The two-day course on [non-financial motivation levers](/en/training/management/non-financial-motivation/) works through twelve of them. ## The counter-offer trap The resignation letter arrives, and the reflex is to match the offer. It sometimes works for a few months. But if the real reasons were on the list above, a higher salary leaves every one of them in place, and the person — now paid more, and still without a next step — often has the same conversation with another employer within the year. The useful moment was earlier. ## Ask before they decide The single most effective habit is also the simplest: a regular conversation about why the person stays. Not an appraisal and not a project update — ten minutes, every few months, with three questions: 1. What keeps you in this job? 2. What would make you start looking elsewhere? 3. What would you like to be doing in a year? The answers are occasionally uncomfortable, and that is the point. They tell you what an exit interview would have told you, while there is still time to act on it. Building those conversations into the rhythm of the year, rather than saving them for the appraisal, is covered in [The manager-leader toolkit](/en/training/management/manager-leader-toolkit/). ## Younger professionals are not a separate species A common conclusion in Singapore firms is that younger staff simply move every two years and nothing can be done about it. Part of that is the market. But the pattern follows the same three levers as everywhere else: a visible prospect, frequent feedback, and work whose purpose has been explained. Managers who work on those three tend to find that "generational" turnover is less generational than it looked — the subject of [Non-financial motivation levers and team coaching](/en/training/management/non-financial-motivation/). None of this guarantees that a good person stays. Some will leave for reasons that have nothing to do with you, and some should. The aim is narrower and more achievable: that nobody leaves for a reason you could have fixed and never heard about.singapore-businessretentionmotivationmanagementsingaporehttps://www.abp-consulting.sg/en/blog/managing-a-regional-team-across-time-zones/https://www.abp-consulting.sg/en/blog/managing-a-regional-team-across-time-zones/Regional teams run on a narrow window of shared hours. What to decide without meeting, which rituals to keep, and how to stop the people outside the hub feeling second-class.Mon, 07 Sep 2026 00:00:00 GMTSingapore is where many regional teams are run from, and it sits at a convenient point on the clock. Jakarta and Bangkok are an hour behind; Manila, Kuala Lumpur, Perth and Hong Kong share the same hour; Tokyo and Seoul are an hour ahead, Sydney two or three. Mumbai is two and a half hours behind. Europe is six or seven hours behind, which means the European morning is the Singapore afternoon. On paper that looks manageable. In practice it produces a very particular kind of working day. ## The window that swallows the day Take a regional team spread across four of those locations, reporting to a head office in Europe. The hours when everyone is at work at once are few, and the hours that also overlap with head office are fewer still — often a slice of the Singapore late afternoon. Every meeting that involves the whole team has to fit in that slice. So do the calls with head office. The window fills up, the meetings run back to back, and the rest of the day passes with people unable to reach the person they need. The manager ends up in meetings for the entire shared window and doing their own work in the evening. ## Decide what does not need a meeting The first move is to protect the shared window by taking out of it everything that can happen in writing: - **Status updates** go into a short written weekly note or a shared board, not a call. - **Decisions with a clear owner** are taken by that owner and announced, with the reasoning, rather than brought to a meeting for approval. - **Questions that need several inputs** are opened in writing with a deadline for replies, and only come to a meeting if the replies conflict. What stays in the window is what genuinely needs a conversation: disagreements, trade-offs, anything emotionally charged, and the relationships themselves. A shared progress board does much of that work on its own. When everyone can see where each piece of work stands, a large share of "where are we on this?" calls simply stop. ## Share the inconvenience Some meetings will fall at a bad hour for someone. The question is who. In many regional teams the answer is, without anyone deciding it, always the same people — usually those furthest from head office. It is worth making it an explicit decision: rotate the awkward slot across locations, and take your turn. It costs the manager a few early mornings or late evenings, and it tells the team something no speech about fairness can. ## Do not let the hub become the team The quietest risk in a regional team is that the real decisions start happening among the people who sit together in Singapore. A question gets settled over lunch; the conclusion reaches Jakarta two days later as an instruction. Colleagues outside the hub rarely object to not being in the room. They object to discovering afterwards that the room decided without them. The rule that prevents it is simple and demanding: a discussion that happens locally ends with its conclusion, and the reasoning behind it, posted where everyone can see it before anyone acts on it. ## One-to-ones matter more, not less When people share an office, a manager picks up a great deal informally: who seems tired, who has gone quiet, who is stuck. At a distance, all of that has to come through a deliberate conversation. The regular one-to-one — kept, not moved every time the window gets crowded — is the tool that replaces the corridor. The one-to-one itself is at the core of [The manager-leader toolkit](/en/training/management/manager-leader-toolkit/). Regional managers often also lead people who do not report to them: country teams, partners, colleagues in other functions. For that half of the job, the frame-setting and feedback work in [The manager-leader toolkit](/en/training/management/manager-leader-toolkit/) applies just as well.managementremote-workregional-teamsmanagementsingaporehttps://www.abp-consulting.sg/en/blog/flexible-work-requests-what-the-manager-decides/https://www.abp-consulting.sg/en/blog/flexible-work-requests-what-the-manager-decides/Formal flexible work requests now follow a defined process in Singapore. What that process leaves to the line manager, and how to decide without it becoming personal.Sat, 05 Sep 2026 00:00:00 GMTA team member asks to work from home two days a week, or to start and finish earlier, or to compress their hours. A few years ago many managers would have handled that with a quick conversation. In Singapore, a formal request now sits inside a defined framework. The **Tripartite Guidelines on Flexible Work Arrangement Requests**, which have applied since December 2024, expect employers to have a process through which employees can make formal requests, to consider those requests properly, and to give their decision in writing. They do not oblige an employer to say yes. This article is not a legal guide; the current text, the time limits and the paperwork are for your HR function. It is about the part of the process that usually lands on the line manager's desk: deciding whether the work can actually be done that way. ## Separate the process from the judgement HR owns the process: how a request is submitted, how it is recorded, the deadlines, the written reply. The manager is usually the person best placed to answer the question in the middle of it — and the person most likely to answer it badly, because it arrives mixed up with everything else they think about the employee. Keeping those two apart is the first discipline. A request is not a vote of confidence, and a refusal is not a verdict on someone's commitment. ## Judge the work, not the person The useful questions are about the job: - **Which parts of the work need a particular place or time?** Client meetings in person, a production line, a counter that has to be staffed, a daily hand-over with another time zone. - **Which parts do not?** Analysis, writing, preparation, most internal coordination. - **What would the arrangement change for colleagues** — cover, response times, who picks up the phone? - **How would we know if it is working?** The question to avoid is the one many managers ask silently: *will this person still work as hard?* A decision based on that belief is hard to defend, and it damages the relationship whether the answer is yes or no. ## Make results visible first Most of the difficulty in granting flexibility comes from not knowing what "doing the job well" looks like beyond being seen at a desk. A manager who has already set clear objectives, measured by results rather than presence, finds these requests far easier: they can grant them with confidence, review them honestly, and adjust them without it becoming personal. Setting that kind of frame is part of the core [manager-leader toolkit](/en/training/management/manager-leader-toolkit/). ## Every decision is a precedent The first request in a team is never only about one person. Whatever you decide becomes the reference point for the next request, and the rest of the team is watching for consistency. State the criteria you are using — the requirements of the role, the needs of cover, the client commitments — and apply them the same way to the next person. And look after the colleagues who did not ask: flexibility granted to some must not quietly become extra load for the others. ## Try it, then review it Where the answer is not obvious, a trial period with a fixed review date is usually better than a hard yes or no. Agree what will be looked at — deadlines met, client response times, the team's workload — and look at it together on the date. If it works, it continues on evidence. If it does not, the conversation is about the arrangement, not about the person. That review is itself a feedback conversation, and it goes better with a method; [Self-awareness and positive communication](/en/training/communication/self-awareness-and-positive-communication/) covers one. Running the arrangement day to day — rules, rituals, one-to-ones at a distance — builds on the one-to-one practice in [The manager-leader toolkit](/en/training/management/manager-leader-toolkit/).managementflexible-workremote-workmanagementsingaporehttps://www.abp-consulting.sg/en/blog/disc-or-the-enneagram/https://www.abp-consulting.sg/en/blog/disc-or-the-enneagram/Both are used in self-awareness training and they are often confused. They answer different questions, suit different situations, and share one firm limit.Thu, 03 Sep 2026 00:00:00 GMTSelf-awareness is where most of ABP's programmes start, and two instruments do most of that work: DISC and the Enneagram. They are often mentioned in the same breath, and a surprising number of people who have taken one believe they have taken the other. They are not interchangeable. They answer different questions. ## DISC: how someone behaves DISC describes four behavioural preferences — Dominance, Influence, Steadiness and Conscientiousness — as they show up in a working context. It is deliberately simple. You can see the signals in a meeting: the pace someone speaks at, how much detail they want, whether the relationship comes before the subject or after it, how they handle disagreement. That simplicity is its strength. In a single day a team can learn the model, each person can receive their own profile, and everyone can practise adjusting how they announce, ask and disagree. The [two-day DISC and Driving Forces course](/en/training/communication/disc-reading-and-adjusting/) is built exactly that way. What DISC does not do is explain *why* someone behaves as they do. Two people with the same visible profile can be driven by entirely different things. ## The Enneagram: what drives someone The Enneagram describes nine types, each defined by a core motivation and by what that type seeks to avoid. It works a level below behaviour: what someone is really after, what they protect themselves from, and how they change under pressure — which is often where the most costly workplace patterns appear. It asks more of the participant. Identifying your type is done through guided reflection rather than a score, and the most useful part of the work is recognising your own habits, not analysing other people's. That is why the [Enneagram-based course](/en/training/communication/self-awareness-and-assertiveness/) takes three days, and why it fits naturally alongside coaching. ## How to choose A practical way to decide: - **Friction between people in a team, meetings that go badly, a team that needs a shared language:** start with DISC. - **A manager who wants to adapt how they lead each person:** DISC first; the Enneagram when behaviour alone does not explain what you see. - **A pattern that keeps repeating in someone's career, a leadership transition, individual coaching:** the Enneagram. Many people take both, in that order. ## The limit they share Neither instrument is a selection tool. Neither predicts performance, neither measures competence, and neither should be used to recruit, to appraise or to sort people. Organisations that do so rest decisions on a criterion with no predictive value — and quickly teach their staff to treat the whole exercise as a test to be gamed. Used for what they are valid for, both are remarkably effective: understanding yourself, and adjusting how you work with someone else. ## A note for multinational teams In a Singapore team drawn from many countries, there is one further reason to use a shared behavioural model. Friction between colleagues is easily put down to nationality — and once it is, it becomes delicate to discuss. A vocabulary of working styles gives people another way to describe the same friction: "you want the conclusion first, I need the reasoning" is more accurate than a remark about someone's background, and much easier to act on.communicationdiscenneagramself-awarenesscommunication