No ?
please don't message at 3 AM expecting an immediate reply
Imagine waking up to 14 messages sent at 3 AM, each one more desperate than the last, all because someone forgot time zones exist... 🤦♀️
❌ Don't do this
T.J Miller needed something urgently: this can't wait, let me ping them now. But sending a flurry of messages at 3 AM doesn't speed things up — it just guarantees the other person wakes up to stress and resentment.
Most people who do this don't mean to be inconsiderate. It's a blind spot: "It's afternoon for me, so I forget it's the middle of the night for them."
But in distributed teams, ignoring time zones erodes trust. It creates pressure to be always-on, anxiety about missing messages, and makes people dread opening their chat app in the morning.
The same goes for:
- Follow-up messages when someone hasn't replied in minutes (at night)
- Marking everything as urgent regardless of the hour
- Expecting instant replies from people in different continents
- Sending "hello???" at 4 AM because you didn't get a response
- Scheduling calls without checking the other person's timezone
Their 3 AM is not your 3 PM!
✅ Instead, try this
One clear message with no urgency pressure lets the other person respond on their own schedule — and they'll actually want to help instead of feeling ambushed.
When messaging across time zones, try:
- Send one message with full context, then wait
- Add "no rush" or "whenever you're online" to set expectations
- Use scheduled messages to deliver during their working hours
- Check a world clock before following up
Async means trust, not silence. A well-written message at 3 AM that says "no rush" is respectful. Three follow-ups demanding a reply is not.
When done right, everyone sleeps in peace. 🎉