Update low context communication link

 - pattern: '^/videos/'

 - pattern: '^/images/'

# Custom anchors

 - pattern: '^/handbook/communication/#low-context'

 # Pages using the `{{% performance-indicators %}}` shortcode.

 - pattern: '^/handbook/engineering/development/performance-indicators/?#'

 - pattern: '^/handbook/engineering/infrastructure/performance-indicators/?#'

   1. They don't have a subject, so everyone has to remember the topic of each private group based on the participants, or open the group again to read the content.

   1. History is lost when leaving the group or [after 90 days](/handbook/communication/#slack).

1. It is perfectly fine to create a channel, even for a single customer meeting. These channels should be named "a\_<customer-name>-internal" to indicate their "internal" nature (not shared with customers).

1. Use [low-context communications](https://en.wikipedia.org/wiki/High-context_and_low-context_cultures) by being explicit in your communications. We are a remote-only company, located all over the world. Provide as much context as possible to avoid confusion. Relatedly, we use [ubiquitous language](#ubiquitous-language) for communication efficiency.

1. {{% a "low-context" %}} Use [low-context communications](https://en.wikipedia.org/wiki/High-context_and_low-context_cultures) by being explicit in your communications. We are a remote-only company, located all over the world. Provide as much context as possible to avoid confusion. Relatedly, we use [ubiquitous language](#ubiquitous-language) for communication efficiency.

1. When discussing concepts, be careful not to lean too much into hypotheticals. There is a tipping point in which it decreases value and no longer becomes constructive at helping everyone come into a unified decision.

1. Consult our [tips for better writing](/handbook/company/culture/all-remote/).

1. If a user suggests an enhancement, try and find an existing issue that addresses their concern, or create a new one. Ask if they'd like to elaborate on their idea in an issue to help define the first MVC via a subsequent MR.

1. **Cross link** issues or MRs with related conversations. Another example is to add "Report: " lines to the issue description with links to relevant issues and feature requests. When done, add a comment to relevant issues (and close them if you are responsible for reporting back, or reassign if you are not). This prevents internal confusion and us failing to report back to the reporters.

1. When cross-linking issues or MRs, include a preview of the content you are linking, to facilitate [low-context communication](/handbook/company/culture/all-remote/):

1. When cross-linking issues or MRs, include a preview of the content you are linking, to facilitate [low-context communication](/handbook/communication/#low-context):

   1. Good: `this would cause performance issue similar to #123456`. The reader has full information on first read and can refer to the link for more.

   1. Avoid: `this would cause issue similar to #123456`. The reader needs to click the link and find the relevant information among other discussion threads, before switching back to the original discussion.

1. When providing links to specific lines of code relevant to the issue, **always use a permalink** (a link to a specific commit for the file). This ensures that the reference is still valid if the file changes. For more information, see [Link to specific lines of code](https://docs.gitlab.com/ee/development/documentation/styleguide/#link-to-specific-lines-of-code).

### 6. Asynchronous work bridges the knowledge gap

Asynchronous companies should implement a [low-context culture](/handbook/company/culture/all-remote/). This means that communication is precise and direct. Team members forecast what questions may be asked about a communique and add in as much context as possible in its delivery. By assuming that the recipient is asleep, or perhaps doesn't even work at the company yet, this added context removes ambiguity and decreases the likelihood of misinterpretation.

Asynchronous companies should implement a [low-context culture](/handbook/communication/#low-context). This means that communication is precise and direct. Team members forecast what questions may be asked about a communique and add in as much context as possible in its delivery. By assuming that the recipient is asleep, or perhaps doesn't even work at the company yet, this added context removes ambiguity and decreases the likelihood of misinterpretation.

This may feel inefficient, as crafting a message may take longer to compose and edit. However, the long-term benefits are remarkable. At GitLab, we have years of documented decisions — such as [this example of availability over velocity](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/30046) — loaded with context. This enables new hires to [self-learn](/handbook/company/culture/all-remote/) as they sift through archives to discover the context that influenced a given decision.

1. Multiple people can write at the same time, allowing purer trains of thought to reach canvas versus waiting your turn

1. Can see what people are looking at in real-time via cursor indicators

1. Can make suggestions

1. Can make [low-context comments](/handbook/company/culture/all-remote/) that are time-stamped

1. Can make [low-context comments](/handbook/communication/#low-context) that are time-stamped

1. Can change hierarchy with indentation

1. Can copy and paste

1. Doesn't run out of space

1. Link the agenda in the meeting invite.

1. Establish the agenda as far in advance of the meeting as possible.

1. Agendas should use [numbered lists](/handbook/communication/#writing-style-guidelines), not bulleted lists.

1. `Context` section includes: The goal(s) of the meeting; clear pre-work or pre-watch/read instructions; intent and expected outcomes using [low-context communication](/handbook/company/culture/all-remote/).

1. `Context` section includes: The goal(s) of the meeting; clear pre-work or pre-watch/read instructions; intent and expected outcomes using [low-context communication](/handbook/communication/#low-context).

### Pre-work and meeting kick-off