# Remote design collaboration: what goes live and what goes async

> Remote design collaboration mixes live and async communication. Learn what to do live, how to record decisions, and how to agree on team communication norms.

*Tags: ux, process, work, collaboration, async*

---


> [!info] Quick Definition
> **Remote design collaboration** is the set of practices that let people work together from different places and time zones. It combines **synchronous** communication (live, like a call) and **asynchronous** communication (when each person can, like a comment or a video), and it succeeds when the team knows which to use for each situation.


## What is remote design collaboration?

It is working with people who are not in the same office or time zone. For a design team, that means reviewing screens, making product decisions, and keeping the context of the work without depending on hallway conversations.

One distinction matters: having a remote team is not the same as having a team that uses remote tools. If decisions are made in meetings only some people attend, the rest of the team is left out even while working from home.

## Why does it matter to a designer?

Because much of the value of design lies in context: why an option was chosen, what was rejected, and what worries people. That context is easily lost on a distributed team. When a decision is not written down, the next designer who arrives reopens it, or applies it wrongly.

Remote work also forces you to be clearer when asking for feedback. A vague comment in a meeting gets fixed with a question; in a written comment, it can take a week of back and forth.

## What goes live and what goes async?

Contra does not ask you to pick a side: it says async is not always the answer and that the key is to be intentional. It lists five cases for going live: sensitive conversations (performance reviews, conflict resolution, difficult news), complex negotiations, team bonding, creative kickoffs, and true emergencies. Atlassian is blunt about status meetings: "synchronous is never the way to go".

| Situation | Better format | Why |
|---|---|---|
| Creative kickoff | Live | Contra: initial creative sessions benefit from real-time energy |
| Brainstorm afterward | Async | Atlassian: each person works at their own pace, has more time to reflect, and traditionally quieter voices can contribute without interruption |
| Sensitive conversation or conflict | Live | Contra lists it among the cases for live conversation |
| Status update | Async | Atlassian: status meetings should not be synchronous |
| Screen review | Async, with comments in the design tool | Bitovi lists commenting features in design tools as an async method |
| Small question about a file | In-file chat or a short audio call | Bitovi suggests Figma's cursor chat to avoid unnecessary calls, and an audio call when face time is not essential |
| Product decision | Async, with a written summary | Contra: record decisions and their reasoning |
| True emergency | Live | Contra: system outages or critical client issues |

This is not a fixed rule. What matters is choosing deliberately instead of out of habit.

## How are decisions documented?

Contra recommends "writing everything down": if a meeting happens, record the decisions, the action items, and the reasoning; and keep a decision log that says why something was decided, not only what. For long chat threads, it suggests summarizing them and moving the outcome into a decision document. As a practical rule, add to each entry the alternatives that were rejected and what remains open, so the reasoning stays attached to the decision.

This prevents a common problem: someone asks why the team chose an option, and nobody remembers the discussion. A design decision log, like the one described in the [design decision log](/en/wiki/artifacts/design-decision-log/) page, answers that question with little effort.

Another point: documentation needs a single source of truth. Bitovi puts it this way: documentation works best when it exists in one place, and that source can "rot" if it is left too long without updates. It also suggests keeping design decisions in one central, regularly updated resource, and attaching descriptions to components in tools like Figma or Zeplin so designs stay linked to their documentation.

## How do you agree on team norms?

Contra proposes a communication charter that defines three things: what each tool is for, how long people have to respond, and what counts as a true emergency. Its reference example is replying to email within about 24 hours and to urgent chat messages within about 4 hours during work hours. Without that charter, "urgent" becomes an excuse to talk in real time all the time.

Atlassian suggests a "working agreement" in the same spirit: make the implicit explicit, agree on message response times, and set blocks of time for answering chat and email so the rest of the day stays free for focused work. To start, it asks whether there is one meeting you could move to async. One concrete way: replace it with a written update and measure what happens.

## When should you NOT go async?

Not everything is solved with messages. Atlassian acknowledges that relationships struggle to develop in an asynchronous model and that it is hard to beat gathering in person. Contra includes team bonding among the cases for going live.

If a topic has stalled for weeks in writing, the problem is probably not the channel. A design that nobody understands from a document often needs a live conversation to become clear.

## Example

Illustrative example: a design team with people in three countries held a one-hour weekly status meeting. To replace it, the team started with a written update per person, with three sections: what changed, what is blocked, and what they need from others. They kept a short call only for decisions with conflict, and decisions moved to a shared log with their reasoning. The change did not remove the conversation; it moved it to the moments where it added the most. To know whether it worked, the team checks after a month whether fewer blockers go unattended and whether anyone still asks why an already logged decision was made.

## Common mistakes

- **Holding status meetings** that could be written.
- **Making decisions in meetings** without writing them down.
- **Using "urgent" as an excuse** to talk in real time without a protocol.
- **Having several sources of truth** and not knowing which one is current.
- **Long chat threads** with no summary that reach a conclusion.
- **Not defining response norms**, which creates anxiety for anyone waiting for an answer.

If remote work includes research with people in different countries, [remote research](/en/wiki/research/remote-research/) describes its particulars. To check whether the change works, [DesignOps metrics](/en/wiki/processes/designops-metrics/) offer efficiency and team health indicators. And to communicate findings to people who were not in the conversation, [[presenting-research-findings|presenting research findings]] has useful guidance.

## Sources

- [How to excel at asynchronous communication with your distributed team, Atlassian](https://www.atlassian.com/blog/teamwork/asynchronous-communication-for-distributed-teams)
- [Four Tips for Working with Remote Product Design Teams, Bitovi](https://bitovi.com/blog/four-tips-for-working-with-remote-product-design-teams)
- [Async Communication Guide for Remote Teams, Contra](https://contra.com/p/BFNMYRQ7-async-communication-guide-for-remote-teams)


---

Source: https://www.fernandoux.com/en/wiki/processes/remote-design-collaboration/
