Pakikisama

How it works

Thin-source as a glossary object; real as a workplace force. People will not correct a founder in public. Ask privately. Reward the first person who flags a defect in the handoff. For a U.S. company hiring one Filipino teammate, write this into the brief, the employment contract, and the peso payroll file before the start date. Slack habits do not override the Labor Code, BIR, or NPC. If the local employer of record holds the paper, they run the statutory step; you still owe a clean operating definition so the seat does not fail in week three. Put a number on the example when you budget loaded cost, because a nameless allowance always returns as a December surprise or a missed SLA.

Example: three teammates know the SOP is wrong. Nobody says so on the call. Defect rate stays high until you ask each person alone.

How it differs

Hiya is embarrassment. Indirect no is the sentence shape. Karaoke culture is the social glue after hours.

Common errors

Forcing public call-outs as ‘radical candor’ imports.

In practice

Treat Pakikisama as a week-one operating object. Put the expected sentence in the brief: what they send, to whom, by when. Culture words do not replace a template. Write an owner - founder, local employer, or worker - and a date you will look at it again: first cutoff, first holiday, or first miss. If nobody can show a contract clause, a payslip line, a calendar block, or a checklist box, you do not have pakikisama yet. You have a conversation. Convert the conversation before the person starts, while changing the deal still costs a paragraph rather than a resignation. Re-read the worked example above against the actual hire in front of you. If the numbers in that example cannot be swapped for this seat’s pesos, hours, and start date, the brief is still unfinished.