THE FUTURE MARKETACADEMY
Your classroomRoom 08 · Career Center
School of Careers

Remote Collaboration: tools and async habits

Education only. Canadian and Ontario rules in this course are examples: the Ontario facts come from ontario.ca and the time zone facts from Government of Canada pages. Rules differ by country, and can differ for your job, your province or state, or a federally regulated workplace, and they change. Other countries: see the In your country box in Lesson 2. This is not legal advice: check the official page and ask your employer, a union or the Ministry of Labour about your own case.

What you'll be able to do
  • Choose between async and live work for a given task, and agree response times with a team.
  • Write async updates and decision posts that people can act on without a call.
  • Plan work across time zones and find a fair overlap window.
  • Use shared documents with comments, suggestions and the right permissions.
  • Run short, useful meetings with an agenda, roles, notes and action items.
  • Hand work over cleanly and write a team working agreement.
  • Know the main hours-of-work rules in your country that affect remote schedules (with Ontario examples).
Words in this course 45Open the Vocabulary Hall
01

Async first, live when it helps

In simple words

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.

Key facts
  • 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.
Example (async update)

"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."

Step by step
  1. Write "Before this course: Remote Work Skills, course 8.6" at the top of a page and tick what you can already do.
  2. 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.
  3. For each, write Async or Live and one reason.
  4. Write a team response-time table with 3 channels and a time for each.
  5. Write one async update in the done, next, blocked format, with one named person and one deadline.
  6. Write one decision post with question, options, recommendation, decider and deadline.
  7. Check: someone who was offline all day could read your update and know what to do next.
Watch on YouTube
How to manage remote teams with asynchronous strategiesRunning Remote · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01Async first, live when it helps
LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00
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."
Try it now

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.
Open Claude
My notes
02

Time zones and overlap

This lesson is part of full access: every course and every level for one payment.

03

Shared documents that stay clear

This lesson is part of full access: every course and every level for one payment.

04

Meetings that earn their time

This lesson is part of full access: every course and every level for one payment.

05

Task boards and clean handoffs

This lesson is part of full access: every course and every level for one payment.

06

Trust, tone and fixing problems

This lesson is part of full access: every course and every level for one payment.

07

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

  1. What does async mean?

  2. What three parts does a good async update have?

  3. Why do teams across countries need to name time zones?

  4. What is an overlap window?

  5. Why check your local labour rules about rest between workdays?

  6. Why check your local overtime rules?

  7. What permission level should you give a reviewer in a shared document?

  8. What should every meeting end with?

  9. What goes in a handoff note?

  10. What are the three parts of a feedback message?

EX

Final exam

This lesson is part of full access: every course and every level for one payment.

CE

Certificate

This lesson is part of full access: every course and every level for one payment.