Hiya

How it works

Thin-source cultural term, not a statute. You will still meet it. People delay bad news to spare you. Build a channel where bad news is a professional duty, not a shame event. Status-before-bad-news is a workaround, not a therapy session. 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: deploy failed at 1 a.m. PHT. They wait for morning to ‘not bother you.’ Queue burns. Protocol: bad news in the handoff even if it is ugly.

How it differs

Pakikisama is the belonging pressure. Indirect no is the speech pattern. Status-before-bad-news is the operating fix.

Common errors

Mocking hiya in a team call. That teaches more silence.

In practice

Treat Hiya 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 hiya 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.