In partnership with

Most remote teams have Slack, Notion, Loom, and a full async toolkit... and still somehow end up online all the time, responding the moment a message lands, and feeling more exhausted than they should be...

In today's send:
✅ What actually async looks like vs. what most teams are doing
✅ The habits that quietly turn async tools into always-on pressure
✅ How to build a real async culture without going off the grid

Top reads this week:

• If you're hiring into Q4, this one's worth bookmarking

• The Slack team have been doing async longer than most and their breakdown of what actually works is one of the better reads on the topic.

• Going remote-first from day one is different from going hybrid later, here’s what founders need to get right before the team starts scaling.

• Most remote management problems aren’t remote problems, they’re likely just unclear systems.

Your follow-ups are only as good as your meeting notes

When the notes get a client's name wrong or a number off by a zero, the follow-up goes out wrong too. Or someone hand-fixes it first. Mostly right is still wrong.

Wispr Flow Notetaker uses your dictionary and calendar, so names, numbers, product names, and acronyms come out spelled right. It pops up when your meeting starts and captures Zoom, Google Meet, Teams, and Slack huddles with one click, no bot joining the call.

Weeks later, ask one question across every meeting you've had and get the answer with citations. Try Notetaker free on Windows and Mac.

Try Notetaker Free

What async actually means (and what it doesn't)

Most people think async means no meetings or flexible hours, but what it really means is that work moves forward without everyone needing to be present at the same time.

That distinction matters more than it sounds, because a team can have all the async tools in the world and still run synchronously at heart, checking Slack every few minutes, responding within seconds, and treating every ping as something that needs an immediate answer.

The tool doesn't make the culture, the every day norms will.

The habits that make async exhausting

The most common pattern is treating async tools like a real-time chat, someone sends a message, someone else responds within minutes, and slowly the whole team learns that availability is expected even when nobody said it was.

Before long you have a flexible remote team that's somehow online more hours than anyone in an office.

A second one is skipping context in messages.

Can we chat? is a synchronous request wearing an async disguise, and any update on X? without background forces the other person to context-switch just to understand what's being asked.

Vague messages are one of the biggest sources of async friction, and they're almost always fixable with two more sentences.

What good async actually looks like

Good async has three things:

• clear norms about when people are expected to respond

• messages that include enough context that nobody needs to follow up just to understand what's being asked

• a shared sense of what's actually urgent vs. what can genuinely wait a few hours.

It also works best when it's paired with a small amount of intentional sync time, not meetings for everything, but a rhythm of moments where the team actually connects in real time, because async without any connection can make people feel like they're working alone rather than together.

ATR tip of the week

Next time you write a Slack message or async update, ask yourself: does this have enough context that someone can action it without asking me a follow-up? If not, add it before you send. It feels slower in the moment, but it speeds everything else up and your team will thank you for it.

Forward this to someone on your team who sends a lot of hey, got a sec? messages 👀

Other reads:

• Answering a question takes the right article. Doing the work (a refund, a plan change) takes permission. Running Agents in Customer Work, four weekly webinars. Register for All Four

• Not every remote team needs the same stack, but most founders are running too many tools with no clear rules for any of them. This breaks down what you actually need and what you can drop.

• Burnout in remote teams is a leadership problem, not a wellness problem. Practical strategies for founders who want to catch it before it becomes obvious.

• Performance reviews feel awkward in most offices. Remote makes them even harder to get right. Here’s what actually works for distributed teams.

• Your next enterprise deal dies in security review without a SOC 2 report. Sprinto gets you audit-ready in 14 days: three sessions, AI agents collect the evidence, you approve.

  Book a demo and and get $1,000 off.

Have a great week!

Thanks,
Sam