Crab Mentality in the Philippines: Is It Real, and Why Does Promoting One Person Turn the Whole Team Against You?

What Does Crab Mentality Actually Mean?

Crab mentality is the image of a bucket of crabs where any one that starts climbing out gets dragged back by the rest — shorthand for resenting a peer's success and preferring that nobody rises. Local media, career writers and employees themselves all use it, and Tagalog has its own equivalents.

Two things matter about that. First, it is a term of self-criticism, not a label applied from outside. When you hear a colleague mutter "crab mentality talaga," they are complaining about their own countrymen. Second, precisely because it is self-criticism, it is heavily overused. Situations that are really structural — opaque promotion criteria, an unfair pay ladder, a manager with visible favorites — get waved away by everyone involved as crab mentality. A foreign manager who adopts that framing inherits a diagnosis that points at nothing actionable.

The correct usage is narrow: treat crab mentality as the name of a symptom, not the name of a cause. It describes peer drag as an outcome. The cause differs every time and has to be found each time. The rest of this article is that search.

Is Crab Mentality Real in Philippine Workplaces?

Partly. Peer-levelling pressure genuinely exists and standing out carries a social cost — but that is not the same as saying employees lack ambition or that teams lack drive. Keeping those two statements apart is what makes your interventions accurate.

Three nameable mechanisms actually drive the drag:

• Pakikisama — getting along, not disrupting group harmony. It is a genuinely positive value locally: willingness to cooperate, no special treatment. The side effect is that anyone perceived to have stopped being one of the group in order to climb gets flagged immediately.
• Hiya — shame, or more precisely the injury of losing face publicly. The trigger is rarely "he got promoted." It is "his promotion made me look inadequate in front of everyone."
• Information vacuum — when promotion criteria were never stated, people fill the gap with the cheapest available explanation: he is close to the boss, he is from the boss's hometown. Most of what gets called crab mentality is speculation caused by opacity.

The counter-evidence is easy to find: the same population performs entirely differently inside a company where the ladder is published and promotions are predictable. That is why the personality explanation is useless in practice. Personalities do not change. Mechanisms do.

Why Your Filipino Staff Seem to Agree and Then Not Comply

Resistance here almost never looks like open pushback. It arrives in four quiet forms: agreeing without executing, doing only the literal instruction, routing questions around you to a senior peer, and collective silence in meetings. Miss those signals and you will believe the team is fully on board right up until the deadline collapses.

1. "Yes" does not mean agreement. In a conflict-avoiding communication style, a verbal yes often means only "I heard you." The fix is to replace confirmation with restatement — have the person say back, in their own words, what they will do, by when, and what would make them come to you.
2. Doing only what was literally asked. This is usually scar tissue: initiative once drew criticism, so the safe move is the minimum. The fix is to state the purpose behind the task, and to publicly acknowledge the first time someone goes beyond it.
3. Going around you to a senior colleague. Not disrespect — a risk calculation. Asking you exposes what they do not know to the person who evaluates them. The fix is a fixed, low-stakes channel: ten minutes daily, unrecorded, not part of any review.
4. Collective silence. No objections in the meeting, plenty afterwards. Do not solicit opinions in large forums; use small groups or written anonymous collection instead. In a hiya culture, public silence is not the absence of opinion — it is unwillingness to bear the consequences of one in public.

The same logic governs deadlines and follow-ups, covered in what "mamaya" really means when someone commits to a time.

Why Promoting One Person Blows Up the Whole Team

Because without published criteria, a promotion is not one person rising — it is a public ruling that everyone else fell short. What detonates is hiya, not envy. Once you see that, the handling changes completely.

The standard blow-up runs like this. The decision is made privately. It is announced the same day. The next morning the new lead has to assign work to colleagues who have been there twice as long. Those colleagues experience the assignment as a public demotion. They begin, passively, to demonstrate that he cannot handle it. He cannot hold the line. Management concludes: classic crab mentality. The appointment is reversed or quietly abandoned. And the whole team learns one durable lesson — people who get promoted here do not survive it. Nobody volunteers next time.

Three specific errors make this near-certain:

• Treating the passed-over senior as a non-issue. Tenure carries more weight here than many foreign managers expect. Skipping a long-serving employee without placing them somewhere creates both an opponent and a compelling victim narrative.
• Announcing the title before granting the authority. If nobody states what the new lead can now decide, the resulting vacuum is exactly where everyone tests the boundary.
• Expecting the new lead to earn authority on their own. In a hierarchy-conscious environment, authority is publicly conferred from above. If you do not confer it, it does not exist.

About to promote someone and worried about triggering exactly this reaction? Have Yixing help structure the announcement →

How to Promote Someone Without Blowing Up the Team: Six Steps

Break the single announcement into four movements — criteria first, leadership visible before it is formal, authority granted in public, seniority placed — so that the outcome is already expected before it is announced. No surprise means no humiliation.

1. Publish criteria at least a quarter ahead. Write down what the role requires: which capabilities, which results, over what period. Doing this one step makes the other five dramatically easier.
2. Make the leadership visible first. Let the candidate run a small project or act as interim coordinator so the team is already used to taking coordination from them. De facto leadership before the de jure title.
3. Brief affected seniors one by one, beforehand. Especially anyone being passed over: privately, with reasons, and with their own next path named. This is the most time-consuming step and by far the most effective.
4. Confer authority publicly. At the announcement, you — the most senior person — state exactly what the new lead now decides and what still comes to you. A stated boundary leaves no room to test.
5. Separate title from pay. Announce the title; never the number. See the next section.
6. Place the passed-over senior. Give them a non-competing track: technical specialist, trainer, key-account owner. Someone with no place left has only disruption available to prove they still matter.

For the pay band that should accompany a promotion see how much salary to offer in the Philippines, and for what happens afterwards, retention and turnover.

Should Promotions and Raises Be Announced?

Titles and responsibilities: always public. Individual salary figures: never — and assume that once two people know a number, the company knows it. That is the local information reality, not anyone's failing.

Titles must be public because otherwise the delegated authority does not function and the new lead never stands up. Numbers must not be, because the moment a figure circulates the conversation shifts from "why does he deserve it" to "why is he getting that much more than me" — the most reliable fuel for peer drag there is.

• Publish the structure, not the figures. How many bands exist, what each band is responsible for, what moves someone up. People need to see that a path exists; they do not need each other's numbers.
• Concentrate adjustments in fixed windows. Handling raises once or twice a year after review is far safer than ad hoc private adjustments, which turn every single one into an event.
• Do not rely on confidentiality as the only defense. Pay information moves locally regardless. Build a structure that survives being discussed: equal pay for equal work at the same band, and differences that have a stateable reason. A gap that can be explained does not detonate. A gap that cannot, always does.

Statutory entitlements are the opposite case — everyone should know exactly how they work, with no per-person versions. See how 13th month pay is computed.

Four Forms of Team Infighting, and How to Break Each

Infighting does not show up as argument. It shows up as escalation over the manager's head, collective silence, resignation used as leverage, and cliques hoarding information. Each has a specific counter.

• Going over the new lead's head. The intent is to rebuild a direct line to you and bypass them. The counter is to route the issue firmly back to the direct manager and to let the person know you did. Accept it once and half the new lead's authority is gone.
• Silent non-compliance. Common right after an appointment. Counter it with short verifiable checkpoints every week or two, so execution becomes an observable fact rather than a judgment about atmosphere.
• Threatened mass resignation. Sometimes real, sometimes one or two people speaking for a "team" that has not been consulted. Counter with individual conversations that verify specifics, and by documenting knowledge in key roles so the leverage shrinks.
• Cliques controlling information. Shared hometown, school or church groups are ordinary here and neutral in themselves; the problem is information circulating only inside them. Counter by fixing important announcements to open channels — written notices, a standing meeting — so exclusivity stops being valuable.

When something has to be handled formally, follow the proper process rather than an informal chat: see handling employee grievances in the Philippines.

Three Things Never to Do, and a Ninety-Day Sequence

Never criticize in public, never promote purely for compliance, and never let "they just have crab mentality" end the analysis. Each of these costs months to repair.

Public criticism is consistently underestimated by foreign managers. Someone criticized in front of peers once will never again volunteer for anything carrying risk. Criticize privately, praise publicly, no exceptions. Promoting the most agreeable person is the cheapest short-term move and it hollows out the team within a few years, because the capable people leave. Ending the analysis at crab mentality is the most dangerous of the three: it stops you asking whether criteria were published, whether pay is defensible, whether authority was actually granted.

A workable first ninety days for a new foreign manager:

• Days 1-30: observe and hold one-on-ones. Change nothing structural and promote nobody. Identify the real opinion leaders, who are frequently not the most senior by title.
• Days 31-60: publish promotion and pay-review criteria and the timing of the windows, so rules arrive before people do. Start giving candidates small projects to lead.
• Days 61-90: brief affected seniors individually, announce, confer authority publicly, and place anyone passed over. In the two weeks after the appointment, follow the new lead's first decisions closely and back one of them visibly.

Once a team is large enough to need formal structure, building the handbook, bands and review cycle in one pass costs far less than patching. To have that built against Philippine labor law, talk to the Yixing visa and HR team.