"Async-friendly" is one of those phrases that sounds great in a job ad and means almost nothing in practice. The version that actually saves your week as a working parent is operational: specific habits and tools that turn fragmented hours into productive work without drowning you in catch-up coordination. Here is the version we use ourselves.
The principle: write everything down once
The single biggest async habit is writing things down once and pointing people to them, instead of explaining them three times in three different chat threads. This sounds obvious. Almost no one does it. The reason it matters more for parents is that you're frequently absent during the time when your colleagues are having the conversation, and you'll waste hours of your day catching up on Slack threads if you don't have a written canonical source.
Practical version: every project of any size gets a short doc — one page, no more — with a clear title, a status, the next decision needed, and a list of open questions. Every status update is added to that doc instead of dropped into chat. Every meeting note links back to that doc. Every time someone DMs you about the project, you reply with a link to the doc and one line of update. After two weeks of this, you'll find that your DMs slow down and your meetings shrink.
The calendar: protect three windows
Most parents try to manage their calendars meeting-by-meeting and lose. The version that works is to protect three specific windows every week and treat them as inviolable.
Window one: deep work. Two-hour block, three days a week, in your highest-energy time of day. For most parents that's the morning after dropoff. Block it in your calendar with a specific project name. Decline meetings during it. Yes, decline. The calendar invite culture has trained us to accept everything; the cost of that habit is approximately your entire career trajectory.
Window two: communication. One 90-minute block in the afternoon for replying to messages, reviewing PRs, providing feedback on docs, and clearing your inbox. Done in batches, this is dramatically faster than the rolling-context-switch version where you respond to messages whenever they arrive.
Window three: planning. 30 minutes on Friday afternoon to set the next week. What's the one big thing you'll ship? What meetings can you decline? What's coming up that requires preparation? The Friday planning ritual is the single highest-leverage 30 minutes you can spend on your week.
The tools: optimize for write-once
You don't need fancy tools to work async. You need a small number of tools used consistently. The minimum viable stack:
One persistent place for project documentation (Notion, Confluence, Google Docs, even a shared GitHub repo of markdown files). The exact tool matters less than the consistency. The team should be able to find any project by going to one place.
One real-time channel for fast-twitch coordination (Slack, Teams, Discord). Use sparingly. Long discussions migrate into the documentation. Specifically: when a Slack thread crosses about ten messages, declare that "this should be a doc" and write it up. Your future self will thank you.
One asynchronous video tool (Loom, Tella, the recording feature in your meeting tool). Five-minute recorded walkthroughs replace a startling number of meetings. They also let your colleagues watch at 1.5x in their own quiet hour, which is a quality of life upgrade for everyone.
The habit: ship one written update per week
Every week, send one written update — to your manager, your team, or your stakeholder — that summarizes what you shipped, what you learned, what's blocked, and what you're working on next. This is the single highest-leverage async habit a working parent can build, because it accomplishes three things in one shot. It demonstrates your output without requiring synchronous facetime. It surfaces blockers early so you don't lose a week to them. And it builds a public record of your work that becomes invaluable at performance-review time, when you'll otherwise be relying on memory and selective examples.
The format doesn't matter. Bullet points are fine. The frequency matters: every week, without fail, even when there's not much to report. Especially when there's not much to report — that's exactly when your manager starts to wonder what you're doing all day.
The boundary: the off-hours messaging rule
Last operational habit: do not respond to non-emergency messages outside your stated working hours, ever, even when you're holding the phone in your hand at 9 PM. The cost of doing it is invisible to you and obvious to your colleagues — every late-night response shifts the cultural norm one click toward "they're always available." Within six months you will be expected to be always available, and you will burn out trying to maintain that pattern.
The rule we use: if it can wait until morning, it waits until morning. If it cannot, the person sending it knows to call you, not to message you. That distinction is enough. It removes 95% of the off-hours load and preserves the 5% that's actually urgent.
Ready to find a flexible role?
Browse our full job board or jump straight to categories that fit your background. Every listing has been filtered for remote-first, async-friendly companies that respect caregiving commitments.