"Update Fri: Done: checked 12 of 15 supplier quotes. Next: finish the last 3 by Tue. Blocked: need the budget limit from Ana by Mon 3 p.m. ET."
Async first, live when it helps
Some questions are like leaving a note on the fridge: whoever comes by next can read it and answer. Others are like a fire alarm and need people to talk right now. Good remote teams choose the note most of the time.
- Before this course: Remote Work Skills (course 8.6). You should already have a workspace, a daily plan with focus blocks, clear messages (bottom line up front, who does what by when), safe accounts and a basic knowledge of your local rules on disconnecting from work (in Ontario, a written policy about disconnecting from work). We build on that and do not repeat it.
- Synchronous (live): people communicate at the same moment, such as a call. Asynchronous (async): the sender does not expect an immediate reply, such as a document comment, email or recorded update.
- Async works well for updates, feedback on a draft, routine questions and decisions that need thinking time. Live works better for sensitive topics, a tangled disagreement, brainstorming or building trust in the first weeks.
- A simple rule: start in writing. If it takes more than two back-and-forth messages without progress, switch to a short call, then write the result down.
- Agree response times by channel with your team. Example: chat within 4 working hours, email within 1 working day, a task comment within 2 working days. Mark real emergencies with a separate, agreed route.
- A good async update answers three things: what is done, what is next, and what is blocked or needs a decision (with who and by when).
- A good decision post has: the question, the options, the recommendation, who decides and the deadline. People who cannot attend can still take part.
- Write "Before this course: Remote Work Skills, course 8.6" at the top of a page and tick what you can already do.
- List five recurring things you do with your team: a weekly update, asking a quick question, feedback on a draft, a decision, and a disagreement.
- For each, write Async or Live and one reason.
- Write a team response-time table with 3 channels and a time for each.
- Write one async update in the done, next, blocked format, with one named person and one deadline.
- Write one decision post with question, options, recommendation, decider and deadline.
- Check: someone who was offline all day could read your update and know what to do next.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
Read the video script
[Host] "Not every question needs a meeting."
[Text on screen: Async = no instant reply expected] "Async means you don't expect an instant reply. That gives people time to think and room to work across time zones."
[Screen: update with Done, Next, Blocked] "Write updates in three parts: done, next, blocked."
[Host] "And agree on response times. Then silence doesn't feel like being ignored."
Write your team's response-time table and send one async update and one decision post this week. Note what questions people still asked, and improve the next one.
ClaudeStuck? Copy a ready-made prompt for Claude
Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.
For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.
I'm learning "Remote Collaboration: tools and async habits" on The Future Market. Lesson 1: "Async first, live when it helps". What the lesson teaches: - Before this course: Remote Work Skills (course 8.6). You should already have a workspace, a daily plan with focus blocks, clear messages (bottom line up front, who does what by when), safe accounts and a basic knowledge of your local rules on disconnecting from work (in Ontario, a written policy about disconnecting from work). We build on that and do not repeat it. - Synchronous (live): people communicate at the same moment, such as a call. Asynchronous (async): the sender does not expect an immediate reply, such as a document comment, email or recorded update. - Async works well for updates, feedback on a draft, routine questions and decisions that need thinking time. Live works better for sensitive topics, a tangled disagreement, brainstorming or building trust in the first weeks. - A simple rule: start in writing. If it takes more than two back-and-forth messages without progress, switch to a short call, then write the result down. - Agree response times by channel with your team. Example: chat within 4 working hours, email within 1 working day, a task comment within 2 working days. Mark real emergencies with a separate, agreed route. - A good async update answers three things: what is done, what is next, and what is blocked or needs a decision (with who and by when). - A good decision post has: the question, the options, the recommendation, who decides and the deadline. People who cannot attend can still take part. The exercise I'm working on: Write your team's response-time table and send one async update and one decision post this week. Note what questions people still asked, and improve the next one. --- I'm stuck. Please: 1. Explain the main idea in plain, simple words with one everyday example. 2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step. 3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "Async first, live when it helps" from the course "Remote Collaboration: tools and async habits". Here's what the lesson says: Some questions are like leaving a note on the fridge: whoever comes by next can read it and answer. Others are like a fire alarm and need people to talk right now. Good remote teams choose the note most of the time. The activity: Write your team's response-time table and send one async update and one decision post this week. Note what questions people still asked, and improve the next one. --- Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words. Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Time zones and overlap
This lesson is part of full access: every course and every level for one payment.
Shared documents that stay clear
This lesson is part of full access: every course and every level for one payment.
Meetings that earn their time
This lesson is part of full access: every course and every level for one payment.
Task boards and clean handoffs
This lesson is part of full access: every course and every level for one payment.
Trust, tone and fixing problems
This lesson is part of full access: every course and every level for one payment.
Your team working agreement
This lesson is part of full access: every course and every level for one payment.
Final project
This lesson is part of full access: every course and every level for one payment.
Quiz
What does async mean?
The sender does not expect an immediate reply.
What three parts does a good async update have?
Done, next, blocked or needs a decision.
Why do teams across countries need to name time zones?
The same clock time means different times in different places (Canada alone has six time zones).
What is an overlap window?
The hours when everyone is in normal working hours.
Why check your local labour rules about rest between workdays?
They differ by country (most Ontario employees get at least 11 consecutive hours under the ESA guide).
Why check your local overtime rules?
Thresholds and rates differ by country (in Ontario, overtime starts after 44 hours at 1.5 times the regular rate).
What permission level should you give a reviewer in a shared document?
Comment (the lowest level that lets them do the job).
What should every meeting end with?
Action items with an owner and a due date.
What goes in a handoff note?
Where the work is, what is done, what is left, known problems, who to ask and the next deadline.
What are the three parts of a feedback message?
Fact, impact and request.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.