Working across time zones?

Let’s talk about time zones.

Some teams love the freedom: people work when they work best.

For others, syncing across time zones creates friction.

Work slows down while someone waits for a reply or sign-off.

But here’s the thing:

Time zones aren’t the problem.
Unclear systems are.

Whether your team has 4 hours of overlap or none at all, what matters most is how your workflows, decisions, and expectations are structured.

This week, we’re diving into how to reduce timezone friction, without relying on more meetings or burning through your overlap hours.

In 5 mins or less, you’ll learn👇

> What really causes time zone delays
> How to structure work for async and partial-overlap teams
> Practical changes to speed up decision-making
> A weekly habit that builds momentum across zones

ICYMI (if you’re new here 👋)
We recently shared:

• Why loneliness hits differently in remote teams

• Strategies to build clarity, trust, and better collaboration (ATR Deep Dive)

• Does your team feel comfortable speaking up?

If your systems are clear time zones won’t create delays

Here’s what tends to happen 👇️ 

In async-first teams:
Work moves overnight… until something gets blocked by a missing decision or unclear next step.

In overlap-heavy teams:
People default to live conversations, even when async would be faster and less disruptive.

The real issue in both cases?

Lack of workflow clarity.
If progress depends on chasing someone in Slack, your process needs an upgrade.

Things that can help - no matter the overlap requirement