How to manage asynchronous communication
GitLab defines asynchronous communication as communicating and moving projects forward without requiring other stakeholders to be available at the moment a message is sent. The company makes starting communication asynchronously its standard practice. It uses public issues, merge requests, and Slack channels to work as openly as possible. It also asks for the outcomes of offline conversations to be documented. GitLab Communication
Starting with written discussion
In GitLab's approach, status updates, announcements, decisions with clear context, and proposals are starting points for asynchronous communication. Topics that would be useful to search for later also fall into this category. When preparing an issue or written discussion, the assumption is that the reader does not have existing context on the topic. GitLab Sync vs. Async Culture
GitLab separates communication channels according to the nature of the work. It uses written text for content that requires a narrative, such as a proposal or short report. Work with a lifecycle is handled in GitLab issues, while short-term coordination takes place through Slack. The company states that channels such as Slack and GitLab issues allow people to work without waiting for one another.
A conversation in an issue does not require participants to be available at the same time. According to GitLab, the conversation can start or stop when there is interest in the topic. Even if everyone involved is not known from the outset, people can be added to the discussion in the issue later. Participants can contribute at a time that suits them.
GitLab states that conversations in issues are searchable. An asynchronous conversation that starts in an issue can also move to a video call when needed. In the company's approach to meetings, before a meeting is scheduled, it asks whether the desired outcome can be achieved effectively through asynchronous methods. GitLab All-Remote Meetings
Writing expectations and the decision process clearly
GitLab's approach to asynchronous communication calls for decision-makers to be explicitly tagged and for the deadline for responses to be stated. Once a decision is made, the outcome is shared in writing. This applies even if the decision was made in a meeting.
For a long text, GitLab asks for a short summary and a clear request. It also expects respondents to read the entire content rather than looking only at the subject line. The company states that artificial intelligence tools can be used to simplify and summarize content.
In GitLab's approach to transparent communication, the rationale for a proposal on which a decision has not yet been made is explained in detail. The explanation covers the problem to be solved and the options. Data is added to the rationale when possible. The contribution expected from others is also based on areas they can influence.
A link to an issue or a similar place where feedback can be provided is shared with the proposal. The deadline for collecting feedback and developments in the decision process are also shared. If the decision has already been made, GitLab calls for explaining the reason for the decision and what led to it. A link for feedback is still provided, but it is stated that the decision may not change soon.
Working in issues and merge requests
GitLab prefers to start a discussion with a merge request when possible. A merge request is associated with a specific proposed change, and everyone can review and openly discuss that proposal. When a change is proposed, the company asks for a merge request containing the minimum valuable change instead of opening an issue that does not contain a specific change.
An issue can be used when no specific code change is proposed. GitLab asks for a single, specific discussion topic and the desired outcome that will bring the issue to resolution to be defined in the issue. It also says that the issue title should state the desired outcome rather than describe the current behavior.
When someone starts working on an issue, GitLab asks for the issue to be assigned to that person. If the next step passes to someone else after part of the work is completed, the issue is reassigned to that person. If someone is asked for a review, the person is referenced with an @-mention in an issue comment instead of being assigned. According to GitLab, an assignment indicates that the assignee is working on or intends to work on the task.
GitLab asks for the expectation to be stated clearly if a specific action is expected from someone. Merely mentioning a person with CC may result in that person reading the issue and taking no further action. It also says to use a comment to inform someone about an issue or assign them a task, rather than only adding their name to the description.
When related issues and merge requests are linked, GitLab asks for a short description of the linked content to be added as well. It says to update the issue description with current information and status, especially when important decisions are made during the discussion. It also asks for a comment explaining why the issue is being closed and whether the outcome of the discussion has been implemented when closing it.
Responsibility for shared content
GitLab states that the person sharing content is responsible for its accuracy, suitability, and content, including when it is prepared with generative artificial intelligence. It asks people to read, understand, and edit comments, code, or other outputs before asking others to review them.
According to GitLab, artificial intelligence can produce false information that appears plausible. The company asks for facts, code functionality, and technical details to be verified before sharing. For announcements to many people, it says to edit long and repetitive content for brevity and clarity.
When confidential information is involved, GitLab asks people to follow the classification rules applicable to the data and the artificial intelligence tools used. It says to use only approved internal tools for sensitive content. Reviewing shared text for inclusive language and potential biases is also part of this approach. Stating that artificial intelligence was used does not remove responsibility for the content.
Contributing without attending a meeting
In GitLab's approach to meetings, the agenda gives participants access to the topic before the meeting. The agenda includes a title relevant to the meeting, materials that need to be known or reviewed to participate, and the desired outcome. It also includes a space where participants can add their thoughts and questions synchronously or asynchronously.
According to GitLab, preparing the agenda in advance gives people time to conduct the necessary review and contribute to the agenda asynchronously. People can also decide whether to prioritize attending the meeting synchronously. The agenda link in the meeting invitation makes it possible to see the topic and preparation materials in advance.
GitLab asks for a single live agenda to be used for a business meeting. If it becomes clear that there is more than one agenda for a meeting, it says to stop the meeting, clarify with participants which agenda will be used, and retire the other agenda. A link to the agenda in use is added to the retired agenda.
Agenda items can also be updated during the meeting. GitLab asks for participants' views and feedback to be added to the relevant items. When a team member is named in the agenda, it says to write their first and last name or use the tagging feature. If the meeting was recorded, the recording link is also added to the agenda.
In GitLab's DRI approach, the meeting DRI or facilitator takes responsibility for the meeting. People whose input is sought are usually subject matter experts, and communication with them is two-way. Most people who only need to be informed are not invited to the meeting if there is a more efficient way to convey the information. When these people are invited because of a need to reach consensus immediately or constraints on conveying the information asynchronously, the company asks that they not be added as recurring participants in the meeting series.
Tracking work after a meeting
GitLab states that meeting notes support asynchronous participation. Team members can add their thoughts to the agenda before the meeting; if they cannot attend, they can learn what was discussed from the notes. The notes also create a written record of the discussion.
GitLab asks for written notes even if a recording is made. According to the company, reading written notes is more efficient than watching meeting recordings, and notes offer more opportunities for asynchronous participation. It asks for issues or merge requests to be used for work arising from the meeting and for the relevant link to be added to the agenda.
People whose attendance is not required or who cannot attend the meeting live can be tagged in the resulting GitLab issues. According to GitLab, these people can follow the topic and contribute at a time that suits their working arrangements. In an ongoing meeting series, work can also be tracked with “TODO” and “DONE” labels in the notes.
According to GitLab, when the agenda is followed, people who choose not to attend the meeting can trust that their thoughts will be addressed and their questions answered. Team members can look at the meeting notes and recording later. GitLab states that the recording helps people follow what happened in the meeting and gain additional context for the written notes.
The limits of asynchronous communication
GitLab says that asynchronous communication should not be used to avoid a difficult conversation that requires a real exchange. According to the company, simply sending messages does not mean that the parties have reached a shared understanding.
Making decisions under uncertainty, resolving disagreements, and building trust with new people are situations GitLab identifies for synchronous discussion. Brainstorming ideas that have not yet formed enough to be written down also falls into this category. The company treats conveying context to new team members through conversation and answering their questions as part of synchronous work.
According to GitLab, in decision processes that proceed only asynchronously, discussions can diverge, context can shift, and it can become unclear who is making the decision. For synchronous discussions, it also asks for the agenda and pre-reading materials to be shared in advance and for the intended decision or outcome to be stated clearly. The decision made in the meeting and the decision-makers are then recorded in the relevant issue or written text.