Filipino Workplace Culture: A Manager's Guide

Filipino Workplace Culture

One characteristic people promoting the Philippines (like me) list is Western cultural affinity. The colonial dividend of American English, decades of movement between the US (and most English-speaking countries, for that matter), US educational standards, and a bias toward American popular culture all contribute to the notion of “cultural affinity”. 

When I first arrived in 2002, ubiquitous English and Americana markers like recognizable fast food chains and the use of U.S. customary measurements (about half the time) gave me the impression that the Philippines was, if not American, American adjacent. Based on this impression, I made assumptions about how to communicate and operate here. 

As it turns out, this was pretty naive. Peel back the veneer of "300 years in a convent and 50 years in Hollywood", as writer and journalist Carmen Guerrero Nakpil put it, and you’ll find a complex high-context culture that can be hard to crack for us low-context types. 

This guide is for anyone who works with people in the Philippines, or is about to, and wants the working relationship to run well.

Everything below is painted in broad strokes shaped by language, family, and faith. Manila, Cebu, and Davao differ. So do a 24-year-old content producer in Makati and a 40-year-old operations lead in Iloilo. Use those traits as a starting point for curiosity, then learn your team's nuances.

What Filipino values shape the workplace?

Nine values do most of the work in a Filipino team: kapwa, pakikisama, hiya, amor propio, utang na loob, respect for hierarchy, bayanihan, bahala na, and the centrality of family. Each one shows up in daily work.

Most of this framework comes from Sikolohiyang Pilipino (Filipino psychology), the school founded by psychologist Virgilio Enriquez at the University of the Philippines in the 1970s. Enriquez argued that Filipino behavior should be read through Filipino concepts rather than translated Western ones. That matters for managers, because several of these values look like problems through a Western lens and like strengths through a Filipino one.

Kapwa: the self in the other

Kapwa means shared identity: the sense that you and the person next to you are not separate. Enriquez put it at the center of the whole Filipino value system.

At work, kapwa looks like a team that eats together, celebrates birthdays together, and solves problems in a group chat before anyone escalates. Friction between peers stays low.

If you built your company by going against the grain, this "we" default can take some getting used to. Founder culture rewards the individual call: back yourself, move first, explain later. Hofstede's data shows how far apart the starting points are. The Philippines scores 32 on individualism. The United States scores 91.

To a maverick founder, a team that checks in before acting can look like hesitation. It's measure twice, cut once. The checking happens up front, and once the team moves, it moves as one.

Remote work changes where the "we" lives. In an office, kapwa has a home: the desk next to you, the shared lunch, the senior colleague down the hall who'll tell you how the boss likes things done. In a remote seat, the "we" often shrinks to two people, the hire and the client. One professional working directly for one founder has no team around them to check in with, so the founder becomes the team. That puts a lot of weight on one relationship, especially when the founder works alone, on instinct.

Clients need to make room for that. Be reachable for the quick check-in. Keep the one-to-one even when nothing is urgent. Treat a question as part of the work, not a sign the hire is struggling. Where you can, give the hire a peer group too: other staff in your company, a co-working seat, or a cohort through your staffing partner.

For the Filipino professional in the seat, the adjustment runs the other way. A founder who goes quiet for two days, makes a decision alone, and expects you to do the same isn't being cold. That's how many founders work. Ask for your decision rights in writing, then use them.

Work with it by setting team-level goals alongside individual ones, and by recognizing the team when it ships. When you need one person to own a call, say so by name: "Mara, this decision is yours." Introduce every new hire properly. A newcomer who's welcomed into the "we" contributes faster.

Pakikisama: getting along

Pakikisama is the value of keeping relationships smooth. In a meeting, it often means not contradicting a colleague, or the boss, in front of others.

The upside is a team that collaborates with little drama. Goodwill builds across departments.

To get disagreement without costing harmony, collect input before the meeting, in writing, and frame critique as improving the work rather than winning a point.

Hiya: propriety

Hiya is usually translated as "shame," and Enriquez argued that translation misses most of it. A closer reading is propriety: a strong sense of what's fitting in a given relationship.

At work, hiya can mean a question goes unasked because asking might seem improper, or a problem surfaces late because raising it early felt out of place. The same value drives people to do the work properly and be seen to.

Make asking the fitting thing to do. Put a "questions and assumptions" step into every brief, and ask your own questions out loud so the team sees it's normal.

Amor propio: self-esteem

Amor propio, a term carried over from Spanish, is personal dignity, or face. Public criticism lands hard, even when it's mild by Western standards.

The flip side is deep pride in craft. When good work is recognized, ownership follows.

Correct in private, about the work and not the person. Credit in public, by name.

Utang na loob: a debt of the inner self

Utang na loob translates literally as "debt of the inner self." It's a lasting sense of gratitude toward people who helped you when it counted.

In employment, it shows up as long tenure with employers who invest in their people: the manager who paid for a course, wrote a reference, or gave someone a stretch role.

It also answers a question managers ask often: what motivates Filipino employees beyond pay? Growth, stability, and belonging. Training, wider scope, a clear path to regularisation, and credit for good work by name all count. Earn it by investing visibly, and treat it as reciprocity to honor, never as something to call in.

Respect for hierarchy

Filipinos show respect to seniors through language, through titles ("Sir," "Ma'am"), and through deference. The Philippines scores 94 on Hofstede's power distance index, one of the highest in the world, against 40 for the United States and 35 for Great Britain.

The language is where most foreign managers first notice it. "Po" is a Tagalog particle of respect, used with elders, seniors, and clients, and "opo" is the respectful "yes." You aren't expected to use it, and nobody will mind if you don't. Using it now and then with older colleagues reads as warm. 

In practice, people wait for clear instruction and rarely challenge a manager directly. Give that same team clear direction and it follows through reliably.

Be explicit about decision rights. Write down which calls are the team member's to make, and say it out loud: "This one's yours. You don't need to check with me."

Bayanihan: communal effort

Bayanihan comes from the image of neighbours lifting a whole bahay kubo (a bamboo house) on poles and carrying it to a new spot. It means pitching in together.

When a deadline tightens, Filipino teams cover for each other without being asked. That's resilience you can count on in a crunch.

Thank it when you see it. Then make the cover visible in your planning, so a one-off rescue doesn't quietly become one person's permanent extra workload.

Bahala na: courage, not fatalism

Bahala na is the value most outsourcing blogs get wrong. It's usually translated as "whatever happens" or "leave it to God," and read as a shrug.

Filipino psychologists read it differently. The phrase likely traces to Bathala, the pre-colonial supreme deity, and scholars in the Sikolohiyang Pilipino tradition, notably Alfredo Lagmay, interpret it as determination: the nerve to act when the outcome isn't guaranteed. It's what lets someone take on an unfamiliar task, or keep working through a brownout, without freezing.

At work, bahala na shows up as composure. Plans change, a client moves a deadline, the power goes out in Quezon City, and the team adjusts. Pair it with clear checkpoints and it becomes adaptability you can plan around.

Give the team room to adapt, and agree in advance which kinds of change need a heads-up before anyone improvises.

Family

Family sits at the centre of Filipino life. Many employees are the main earner for parents or siblings, and family events — a baptism, a wake, a fiesta back in the province — come first.

That responsibility is also why a good job matters so much, and why Filipino staff tend to stay with employers who respect it.

Make leave easy to ask for, plan the calendar around family seasons, and don't make anyone choose between the job and a family obligation.

How do Filipino teams communicate at work?

Filipino professionals communicate in strong business English, but often indirectly, and more candidly in writing and one-to-one than on group settings.

Why do Filipino employees say "yes" when they don't understand?

In Filipino workplaces, "yes" often means "I heard you," not "I understand and agree." Saying "I don't understand" to a superior can cost face for both people, especially in a group. Open questions fix this. Ask the person to walk you through their plan, and any gaps surface without anyone having to admit them.

Is English widely spoken in Philippine workplaces?

Yes. English is an official language of the Philippines alongside Filipino, and it's the main language of higher education, law, and business. Most professionals write and speak business English fluently. Among themselves, colleagues often switch between English and Tagalog, known as Taglish. That's normal register-switching, not a gap in English ability.

Four more patterns worth knowing

• Indirectness. Bad news tends to arrive softened, late, or through a peer.

• Silence in meetings. In a group, silence usually signals deference, not agreement.

• Written vs. spoken. Many people are more candid in Slack, email, or a one-to-one than on a group call.

• Sir and ma'am. Titles carry into chat and email, even with a manager who's asked to be called by first name.

How does Filipino work culture play out in remote and hybrid teams?

Remote work removes the office cues Filipino teamwork runs on: the shared lunch, the quick question at a colleague's desk, the senior person you can see and approach. 

The managers who do well with remote Filipino teams rebuild those cues on purpose, and they lean on writing, which suits how many Filipino professionals prefer to raise things.

Before 2020, most Philippine outsourcing work happened in offices and on-site BPO floors. The pandemic moved much of it home almost overnight, and a large share never fully went back. Hybrid setups, co-working seats, and fully remote roles are now normal, and hiring has moved beyond Metro Manila across the Philippines.

That shift changes how values manifest.

Kapwa moves into the group chat. The pantry and the merienda break don't exist on Zoom. Filipino teams rebuild them in group chats on Viber, Messenger, or a social Slack channel. Keep a channel that has no work in it, and leave it to the team. For a single seat with no colleagues, the peer group has to come from somewhere else (see kapwa above).

Hierarchy gets harder to read. In an office, a junior team member can watch how a senior colleague handles the boss. Remotely, there's no one to watch. That makes the written brief and the named escalation path (techniques 4 and 5 below) more important at a distance than in person.

Writing becomes the candid channel. Async tools play to a strength. Many Filipino professionals raise concerns more freely in a written message or a recorded video than live on a group call. Make written updates a standard part of the week, and read them for what they hint at as well as what they say.

Rapport needs a routine. With a team you've never met, trust builds through consistency and small personal gestures. Keep cameras on in one-to-ones. Ask about family and weekends. Remember names and milestones. Join the occasional call with no agenda. Send something for the Christmas party. Over a few months, these habits build the trust that makes candour possible.

AI tools shift the work toward judgment. As AI takes over first drafts, data pulls, and routine admin, offshore roles move from doing tasks to checking and deciding. That puts more weight on the values above. A team member who doesn't feel free to say "this AI output looks wrong" is the costliest gap in an AI-assisted workflow. Give explicit permission to use the tools, and explicit permission to flag what they get wrong.

Early-career staff miss learning by proximity. People who started their careers remotely haven't picked up the habits you absorb by sitting near a good senior. Pair them with a named mentor and a standing weekly session.

How do you manage a Filipino team well?

The managers who get the most from Filipino teams build structure that does the asking for them: open questions, written briefs, private feedback, regular one-to-ones, and a clear path for raising problems. They also explain the reason behind each task and plan around the Philippine calendar. These 12 techniques work across roles and seniority levels, in the office or remote.

1. Ask open questions, not yes/no ones. A yes/no question invites the polite "yes." An open one makes the gaps visible without anyone having to admit them. Try: "Walk me through how you'll approach this," instead of "Is that clear?"

2. Give explicit permission to disagree, and reward the first person who does. Thank the first person who pushes back, in front of the team, so everyone sees what happens next. To get people speaking up in meetings, ask for input before and after as well as during: send the agenda with one or two specific questions, invite people by name for low-stakes input, and follow up one-to-one. Within a few weeks, most teams treat open discussion as part of the job. Try: "If you think I'm wrong on this, I want to hear it. You'll usually know the details better than I do."

3. Give feedback privately and specifically. Correct in one-to-ones. Name what was delivered, what was expected, and what to change next time. Close by confirming you trust the person with the work. Praise in the group channel, by name. Try: "The structure of this report worked. The data section needs sources on every figure. Can you add those by Thursday?"

4. Use a written brief for every assignment. A brief states the scope, the deadline, what "done" looks like, and who decides. It removes the need to ask, which removes the hiya cost of asking. Try: A five-line brief template in your project tool, filled in before any task is assigned.

5. Build a separate escalation path. Give people a named channel for "I'm stuck" or "this looks wrong" that doesn't mean telling the boss they're failing. A team lead, an ops contact, or a dedicated Slack channel all work. Try: "If something's blocked for more than half a day, post it in #blockers. No explanation needed."

6. Hold one-to-ones before you need them. Weekly, 15 minutes, same time each week. Most concerns surface here first, because a one-to-one is private by design. It's the most reliable way to hear about problems before they become serious. Try: Open every one with "What's the riskiest part of what you're working on?"

7. Explain the why behind the task. Context turns compliance into judgment. When people know what the work is for, they make the small calls correctly without checking in. You're hiring judgment, not labour. Try: "We need this by Friday because the client presents to their board Monday. Accuracy matters more than polish."

8. Set measures people can see. Agree on a small number of KPIs up front, write them down, and review them on a schedule. Tie each one to an output the person controls, such as turnaround time, error rate, or pieces shipped. Review new hires at 15, 30, and 45 days, then monthly. Try: Three measures per role, written into the brief.

9. Invest visibly in development. Training, wider scope, and a clear path to regularisation build the loyalty described under utang na loob. Try: One paid course or certification per person per year, chosen with them.

10. Respect family and faith in the calendar. Plan around Holy Week, All Saints' and All Souls' Days, and the Christmas season, and make leave easy to request. Try: Publish the team's holiday calendar in January and plan deadlines around it.

11. Plan for weather and power. Typhoon season runs roughly June to November, and about 20 tropical cyclones enter Philippine waters in a typical year, according to PAGASA. Storms can cut power and internet for hours or days. Agree on backup connectivity and a "can't log on" protocol before the first storm. Try: A company-paid mobile data plan per seat, plus a rule: "If you're offline, text [name] and you're covered."

12. Meet in person when you can. One visit does more for rapport than a year of video calls. Share a meal, see where the team works, and leave room for conversation with no agenda. Build it around a team lunch or merienda, because food sits at the centre of Filipino hospitality. Many teams remember a manager's first visit for years.

How should you bring a new hire up to speed in the first 45 days?

Use a structured 45-day handover in three stages, each ending with a checkpoint at day 15, 30, and 45. Structured transfer suits a team that won't always ask, because the structure does the asking.

1. Weeks 1–2: observe and write back. The new hire shadows the work, then writes up what they learned: the process, the tools, and the open questions. Review it together at day 15.

2. Weeks 3–4: supervised execution. They do the work, and you review it closely. Checkpoint at day 30.

3. Weeks 5–6: own the work. They run it end to end, and you review outputs, not every step. Checkpoint at day 45.

Reviews in weeks 1–2 does most of the work. It turns "any questions?" into a document that shows you exactly what landed and what didn't. For remote hires, it also replaces the weeks of learning by watching that an office used to provide.

Hiring in the Philippines?

Most readers come to this page to understand a team they already have. If you're about to build one, we'll put together a free capability plan: the roles, the structure, and what each seat costs, before you commit to a hire.