"Internal communication" is the connective tissue that keeps everything and everyone in the company moving forward in the same direction. It's a broad term and is an aspect of our culture that every team contributes to in some form.
The People Communications & Engagement team aims to keep team members informed and engaged through compelling internal storytelling and timely information sharing to empower team members to become GitLab ambassadors.
This page defines how our People Communications & Engagement team operates to support GitLab team members and various cross-functional teams within GitLab.
GitLab team members can better understand how communication and engagement work together by reviewing our Engagement Strategy presentation.
Given the amount of information we need to communicate with GitLab team members around the world it's important that we have a structured approach to communication & engagement.
It's equally important that we provide team members with a well-rounded view of things happening across GitLab.
In preparing key messages to be shared with all team members, we ask all departments to follow the process below:
We use a variety of channels to communicate with various audiences within GitLab. The top channels we use, the purpose of each of these channels, and how everyone can contribute to each is as follows.
@kaylagolden. Things to note when sending over content:
GitLab Handbook: For permanent and non-confidential updates, we consider how information should live in the GitLab Handbook.
GitLab Assembly is our quarterly all-company meeting and is an opportunity for team members to hear from leaders and teams across the company. Assembly provides a holistic view of top priorities, customer stories and data, cross-collaboration, department deep dives, and other team member stories to bolster team member engagement, shared visibility, and company connectedness. Assembly is a 50-minute meeting consisting of ~35 minutes of content and ~15 minutes of Q&A and is scheduled to take place late in the second month or early in the third month of each quarter (January, April, June, October). To give global team members an opportunity to join live, there will be two live-hosted Assembly events each quarter, with the first event at 5pm PT (12am UTC) and the second event the next day at 8am PT (3pm UTC).
To produce each quarterly Assembly, the People Communications & Engagement DRI:
On the day of Assembly:
After the second Assembly event:
We operate an internal communications editorial calendar (confidential to a small internal group) with key company-wide announcements, campaigns, and events. To get added to this list, please review the Internal Comms Tiered System to determine if your message falls into Tier 1a/1b which would signal a #company-fyi or #company-fyi-private message. If that’s the case, create a copy of and complete the request for internal communications support template and share on Slack using the #internal-communications-requests channel, or if confidentiality is a concern, please connect directly with @kaylagolden.
Timing of various messages and internal campaigns, and having a solid plan is a key to successful communication. As a company that's in growth mode, change is constant and we have a lot that needs to be shared with team members.
We operate as a lean team and due to limited bandwidth, we are unable to service all communications fully. Please review the Internal Comms Tiered System to understand how and what type of communications we can assist with.
|Content topic||Percentage of Internal Share of Voice|
|Team member total rewards and program updates (Primarily Finance & People Group)||~30% share of voice|
|Values, culture, and team-building content||~20% share of voice|
|Leadership updates about key projects and functional changes||~20% share of voice|
|Business outlook / Product updates||~20% share of voice|
|Reactive, unplanned messaging (we know it happens!)||~10% share of voice|
Everyone plays a role in keeping GitLab team members engaged and informed. If you're partnering with the People Communications & Engagement team, please keep these best practices in mind:
It's important that we consider how information will be received by various sub-groups within GitLab before sharing a piece of information with all team members. A typical cascade of information may end up crossing through various channels in cases where a significant change is being introduced.
For example, if we were announcing a big, exciting new program we might cascade information as follows:
It's important to note that information cascading could be seen as lacking transparency. That's not the case, rather it allows for managers and leaders to keep people more informed as they will have a chance to understand key changes with enough time to then answer questions to their teams.
As we continue to grow our People Communications & Engagement function, we'll continue to add more detailed information to this page. Please offer feedback by suggesting edits to this page or reaching out in the #talent-brand-engagement channel on slack.