You will be able to propose a short set of communication norms for a remote or hybrid team.
It's 9.40pm and your phone lights up. A Teams message from your team lead: "Can you check the numbers in the deck?" Is that for tonight, or for tomorrow morning? You don't know, so you check them, reply at 10.15pm, and feel resentful. Your team lead, meanwhile, sent it at night only because that's when she remembered, and assumed you'd look in the morning.
Nobody did anything wrong. The team simply never agreed what a late-night message means. In an office, many of these rules are absorbed by watching others. In a hybrid or remote team, where people work different days, different hours and sometimes different countries, they have to be written down. This lesson covers the five norms that cause most of the friction: channels, reply times, working hours, decisions and meetings.
Most teams use at least three channels: chat (Teams, Slack or WhatsApp), email, and calls or video. Trouble starts when people use them differently, so a decision ends up in a chat thread nobody can find, or a quick question arrives as a formal email.
A simple default that works for many teams:
Chat is for quick questions and things that can be answered in a line or two. Email is for decisions, anything that needs a record, and anyone outside the team. Calls are for anything sensitive, emotional or complicated, and for any chat thread that has gone back and forth three times without progress, as lesson 2.4, Know when to stop typing and talk, suggested.
Your team's version may differ. Some teams use email only for external contacts and keep everything internal in chat channels. What matters is that everyone uses the same rules, and that WhatsApp, if your team uses it, has a clear line between work groups and personal chats.
The biggest source of stress in remote work is uncertainty about how fast to reply. Agree expected reply times per channel. For example: chat within a few hours during working hours, email within one working day, and urgent issues by phone call, never by message.
Then agree working hours, and what a message outside them means. A common norm: "Messages outside working hours are fine to send, but nobody is expected to reply until their next working day. If it's genuinely urgent, call." Some teams also use scheduled send, so messages written at night arrive at 9am. Either approach removes the 9.40pm guesswork.
Time zones make this sharper. If your team spans Singapore, Sydney and London, there are only a few hours when everyone is working. Sydney is two or three hours ahead of Singapore depending on daylight saving, and London seven or eight hours behind. Agree which hours are the shared overlap, keep live meetings inside them, and rotate the inconvenient slot if one office always ends up dialling in at 10pm.
If your team is discussing flexible arrangements more broadly, such as which days are office days or who works from home when, note that Singapore has the Tripartite Guidelines on Flexible Work Arrangement Requests. They cover how employees make formal requests and how employers consider them. For what they require, check the Ministry of Manpower (MOM) or TAFEP websites, not a colleague's summary. Your team norms sit alongside any company policy and don't replace it.
In a hybrid team, decisions get made in many places: a meeting room, a corridor conversation, a call, a chat thread. People who weren't there are left out, and remote colleagues are left out most often.
Agree one shared place where decisions are recorded. It might be a decision log in a shared document, a pinned channel, or the notes format from lesson 6.4, Close with actions, owners and dates. The rule is simple: if it isn't written there, it hasn't been decided. That protects people who were on leave, in another time zone or simply not in the room when it happened.
Hafiz, a team lead at an e-commerce company with staff in Singapore and Kuala Lumpur, added a single line to his team's norms: "Any decision made in a call or in person gets posted in the #decisions channel within a day, by whoever made it." Within a month, the question "wait, when did we decide that?" had almost disappeared from team meetings.
The last norm is about defaults. In a team that's never all in one place, meetings are expensive to arrange and hard on people in other time zones. Default to written updates that people read in their own time. Keep live meetings for what needs real-time conversation: discussion, decisions, difficult conversations and building relationships.
In practice, that means weekly status updates in writing, like the template from lesson 3.4, Set up a weekly update you can send in ten minutes, instead of a status meeting. It means sharing proposals as a document for comments before a meeting, so the meeting can focus on the decision. And it means recording or summarising the meetings you do have, for people who couldn't attend.
This doesn't mean no meetings. Teams that work entirely in writing can drift apart, and a regular call where people actually see each other is part of how trust gets built.
Look at how your team currently communicates. Which messages arrive in the wrong channel, which replies take longer than people expect, and where do decisions go missing? The friction points you notice are where your norms should start, because a norm that solves a problem people already feel is one they'll actually follow.
Draft five communication norms for your team covering channels, reply times, working hours, decisions and meetings.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).