Is your setup slowing you down?

In partnership with

Hey remoter — Samantha here 👋

A lot of remote teams say they “work async.”

But when you zoom in?
It looks more like delayed real-time: Slack pings, waiting on feedback, half-finished tasks, and teammates unsure whether they should move or pause.

It’s not a workflow problem.
It’s a clarity problem.

Async isn’t what’s left after you cancel the meeting.
It’s a system for moving work forward without needing to be online at the same time.

When that’s missing?

Decisions stall.
People repeat work.
And the team starts drifting instead of delivering.

It’s time to get async right, so your team can move forward.

In 5 mins or less, you’ll learn👇

> What async actually means (and what it’s not)
> Signs your team is defaulting to real-time without realising
> How to shift toward async-first work (without slowing delivery)
> The hidden cost of poor async habits
> Simple leadership cues that build real async culture

ICYMI (if you’re new here 👋)
Here are the last 3 editions remote leaders like you found most useful:

• The cost of “everyone owns it” (aka no one does)

• The quiet warning signs of disengagement

• Why flexibility backfires without structure

Most remote teams don’t work async.

They just message async. 💬

Here’s what that looks like:

• Work gets stuck waiting for sign-off in Slack

• Updates are shared, but no one knows when to act

• Half the team misses decisions because they were asleep

• People “check Slack” to feel caught up but it’s mostly noise

Async isn’t about when you respond.
It’s about how the work is designed to move forward without needing a nudge

What poor async habits are really costing you 💸