Key takeaways

  • Make the next action and its owner explicit.
  • Keep decisions accessible to colleagues who were absent.
  • Use a live conversation when written exchanges stop helping.

Choose what can progress without a meeting

Asynchronous work means people can contribute at different times without waiting for everyone to be present. A useful update gives its recipient enough context to take the next step. Moving a vague request from a meeting into a chat message does not achieve that.

Start with one recurring workflow: a project update, a document review or a handover between locations. Identify the result required, who needs to contribute and when a decision is needed. The checklist below is a proposed team practice, not a claim that every conversation should become written work. Sources were checked on 27 September 2026.

Give each request a clear next action

A group of people bringing their hands together
Hands joined in a group. Photo: Hannah Busing / Unsplash.

Instead of sending a document with any thoughts?, explain the question and the kind of response needed. Distinguish a request for information, a review and a final approval. Name the person responsible for the next step so that a group mention does not leave everyone assuming someone else will answer.

Use the smallest amount of context that makes the request understandable without a separate explanation. A suggested handover note contains:

  • The purpose of the work and the current version or source document.
  • What is finished, what is still uncertain and any known blocker.
  • The specific action requested and the person responsible.
  • The deadline, with time zone where relevant, and the next review point.
  • What can continue if the recipient is unavailable, and how to raise an urgent issue.

Keep the decision where people can find it

Choose an agreed home for the current task or decision record. Use chat to draw attention to it rather than maintaining competing instructions in several channels. Check that the recipient has access before the handover, and link to the current version instead of attaching another unexplained copy.

GitLab's communication guidance uses asynchronous communication as a starting point and asks people to record conclusions from offline conversations. That is a useful organisational example: colleagues who were absent need the outcome as well as the discussion. It is not a requirement to publish confidential work openly.

For a hybrid team, apply the same habit after a conversation at a desk. Record the decision, its owner and any unresolved question in the shared workspace used for the project. Avoid creating an information advantage that depends on being in the room.

A handover that keeps moving

  1. Prepare

    Context + current version + a precise question.

  2. Pass it on

    Name the next owner and the review deadline.

  3. Review

    Respond, flag a blocker or agree a different deadline.

  4. Record

    Write down the decision and next action in the shared record.

Suggested workflow. Agree response windows within working hours and switch to a call if a misunderstanding blocks progress.

Agree response expectations and a decision owner

Set response expectations around working hours and the actual urgency of the task. Separate acknowledging a request from completing the work. If the proposed deadline is unrealistic, the recipient should be able to say so and agree a new plan rather than silently missing it.

State who closes the decision and how late feedback will be handled. Silence should not automatically become approval for a consequential change. If a required reviewer is away, identify an authorised substitute or move the deadline. For cross-region work, make the handover early enough to allow a genuine review window.

Switch to a live conversation when it helps

A repeated misunderstanding, a sensitive conversation or a decision blocked by conflicting assumptions may benefit from a call. Explain what needs resolving and share the relevant material first. Include the people needed to make progress, then return the outcome to the written record.

GitLab's meeting guidance provides an example of using a shared agenda and capturing actions afterwards. Adapt those habits to your own team; a meeting earns its place through the problem it resolves, rather than through a rule that all work must be synchronous or asynchronous.

Review the workflow, not the number of messages

After a trial, ask whether recipients could act without chasing missing context. Review delays, reopened decisions and tasks left without an owner. More messages, longer documents and faster replies outside working hours are not useful goals in themselves. Keep the parts that reduce confusion and simplify the rest.

FLYDESK supports hybrid schedules and shared workspace coordination. It can help teams organise when to meet at the office, while the project record remains in the agreed document or task tool. Establish the handover practice alongside the workplace plan, so that work can continue between shared office days.

Continue reading