Remote and async work

Why it matters

Many technical teams now work partly or fully remotely, and even office-based teams spread across sites, shifts and time zones. When you cannot tap someone on the shoulder, writing becomes the main way work moves forward. Two skills matter most: async status updates that keep people informed without a meeting, and handoffPassing work to someone else, for example at a shift change or before a holiday, with a note on its context and state. notes that let someone else pick up your work.

Sync and async

• SynchronousCommunication that happens at the same time, such as meetings, calls and live chat. (sync) communication happens at the same time: meetings, calls, live chat.
• AsynchronousCommunication people answer when it suits them, such as email, documents and tickets. (async) communication lets people respond when it suits them: email, documents, tickets, chat messages that do not need an instant reply.

Async work lets people focus for long stretches and works across time zones. Its weakness is delay: a vague message can cost a full day of back-and-forth when the reply comes from the other side of the world. So async messages must be complete enough to act on without a follow-up.

Use sync for sensitive conversations, complex disagreements and brainstorming. Use async for updates, questions that can wait and decisions that need time to think.

Writing for async

A good async message:

• Stands alone. Include links, versions, screenshots and error messages, so the reader does not need to ask "which one?".
• States what you need and by when, or says clearly that no action is needed.
• Asks complete questions. Not "Hi, are you there?" followed by a wait, but the whole question in one message.
• Uses the right channel: tickets for tasks, chat for quick questions, documents for decisions.

Async status updates

A common format is a short daily or weekly update with three parts:

1. Done: what you finished since the last update.
2. Next: what you plan to do next.
3. Blockers: anything stopping you, and who can help.

Add links so people can see details if they want. Example:

Status: Sam, Tue 2026-10-14

Done
- Finished the CSV import for supplier data (PR #318, merged).
- Fixed the date-parsing bug for DD/MM files (ticket INV-92).

Next
- Start the export screen (INV-95). Aim: draft PR by Thursday.

Blockers
- Need read access to the staging database to test imports with
  real-size files. @Priya, could you grant it today or tomorrow?

Notice the blockerAnything stopping your progress; a good one names a person, a specific request and a time. names a person, a specific request and a time. A blocker without an owner is just a complaint.

Handoff notes

A handoff happens when work passes to someone else: at the end of a shift, before a holiday, when you change projects or when a teammate in another time zone continues your task. Lab shifts, on-call rotations and site work depend on good handoffs; a missing detail can mean repeated work or a safety risk.

A handoff note covers:

• Context: what the task is and why it matters.
• Current state: what is done, what is in progress, what is not started.
• Next steps, in order.
• Watch out for: known risks, quirks, deadlines.
• Where things are: links to code, documents, samples, logs.
• Who to ask if something is unclear, and when you will be back.

Example:

Handoff: supplier import feature (Sam -> Alex), from Fri 10-17

Context: suppliers upload a CSV of prices; we import it nightly.
Client demo on Wed 10-22.

State
- Import: done and merged (PR #318).
- Export screen: about 60% done on branch export-screen. Table works;
  the download button is not wired up yet.

Next steps
1. Wire the download button to /api/export (see TODO in Export.tsx).
2. Add a test for an empty export.
3. Open the PR and ask Priya to review.

Watch out
- Files over 5 MB time out on staging; production is fine.
- The demo uses supplier "Acme Test". Don't delete it.

Links: board ticket INV-95, design doc, staging URL.
Questions: Priya (tech lead). I'm back Mon 10-27.

A good test: could your colleague continue the work without messaging you at all?

Remote habits that build trust

• Be visible. Post updates regularly, even short ones. Silence makes people wonder.
• Share your working hours and time zone, and respect other people's.
• Turn on your camera when it helps, for example in introductions and difficult conversations, if your team does that.
• Write down decisions made in calls and post them where the team can find them.
• Over-communicate early in a new team, then adjust.

Common mistakes

• "Hi" messages with the question coming later.
• Updates that list activity, not progress: "worked on the export" instead of "the table works; the button is left".
• Blockers with no owner or no request.
• Handoffs that assume context the other person does not have.
• Decisions made in a call and never written down.

Quick recap

• Async messages must stand alone: context, links, the ask and a deadline.
• Status updates: done, next, blockers (with an owner).
• Handoff notes: context, state, next steps, risks, links, contacts.
• Write decisions down and keep your teammates informed.

Try it

Open the Do tab. You will write an async status updateA short written update in three parts: done, next and blockers. and a handoff note for a real or practice task.