Gitlab hero border pattern left svg Gitlab hero border pattern right svg

All Remote Channel Playbook

The All Remote Channel provides guidance and information to business owners, executives and managers on the ways in which they can transition to a remote workforce. Our audience of founders, CROs, CXOs, HR leaders, and managers work in all industries, particularly in tech and enterprise to midsize companies.

Ultimately, the All Remote Channel will help enable viewers to create a remote strategy and establish basic remote management processes. They will also find engaging, actionable information that will help them identify the priorities necessary to successfully go remote and get back to a normal flow of business with a hybrid remote or fully remote team.

Success Metrics

These goals are measured as traffic from YouTube to key All Remote pages, outlined below in the Content Types and Guidelines section.

Who Can Contribute?

Everyone can contribute content to the All Remote Channel provided it follows the playbook guidelines. Common contributor scenarios include:

  1. GitLab's Content team
  2. GitLab's All Remote team
  3. GitLab Team Members


The All Remote Channel informs business leaders and stakeholders about the various aspects of implementing and managing remote teams. For the purposes of this channel, we split the audience into two groups:

People interested in remote work: These viewers are looking for information on how to get started with remote work. This video content should aim to lower the barrier of entry to remote work by providing actionable guidelines and instructions. Case studies and anecdotal stories will also be of interest to these viewers. This audience is the most likely to binge on various types of content within the channel as they learn more about remote work. Experienced remote workers and leaders: These viewers are looking for innovative tips and stories as well as case studies around remote work. The channel is more of an informative and idea-inspiring outlet for this audience.

Content Types and Guidelines

To keep the All Remote Channel focused on its intended audience, please adhere to the following content guidelines and content types. Specifically, we are looking for content that spotlights:

  1. Remote work, with a focus on management & processes.
  2. Remote culture stories from GitLab team members and external remote advocates.
  3. GitLab CEO Sid Sijbrandji as a thought leader in the remote work space.
  4. GitLab, the product, as a key enabler of remote work.
  5. Opportunities at GitLab and attracts geographically diverse candidates that value our all-remote culture.

If you have a suggestion for a video type not listed, please contact We do not publish videos that include disparaging information about other brands and products or that infringes on intellectual property.

Video assets

Supplementary video assets, such as logos, bumpers, photos, graphics, animations, etc. can be found here.

Interviews & Panel Discussions

Interview videos can feature a 1-on-1 discussion or small group chat with GitLab executives, remote team, people managers, and external remote advocates and partners. Panel discussions can be done virtually or as part of a live event.

Uploading criteria:

How-To Videos

All remote how-to videos will provide viewers with quick, actionable tips on remote work. When creating a how-to video, remember to keep the video focused on a single action and outcome. The all remote audience tends to prefer presentation-style videos, so keep this in mind as you prepare your content. If you find yourself explaining how to do multiple things, consider breaking up the video down into smaller videos, with each video covering one aspect. As a general rule of thumb, try to keep how-to videos to under 10 minutes.

Uploading criteria:


Video contributions that meet the playbook criteria will be uploaded to the GitLab Brand Channel and added to the All Remote Channel Playlist. Selected videos will also be distributed on relevant /all-remote/ and web pages.


  1. Submit to GitLab social team for consideration (DRI must create issue to enable this step)
  2. Submit to GitLab editorial team for consideration on the blog and/or bi-weekly newsletter (DRI must create issue to enable this step)
  3. Third-party content platforms (e.g. like, industry blogs, etc.)
  4. Highlighted on GitLab’s weekly “This Week at GitLab” video series
  5. Consideration for featuring in GitLab All Remote video band
  6. Featured in GitLab event follow up email/s (DRI must create issue to enable this step)
GIT is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license