Skip to content
Snippets Groups Projects
Commit c5dcb534 authored by Cynthia "Arty" Ng's avatar Cynthia "Arty" Ng :speech_balloon:
Browse files

Update CEO references

parent b49f75cb
No related branches found
No related tags found
1 merge request!10589Update CEO references
Showing
with 30 additions and 117 deletions
---
title: "GitLab.tv All-Remote Channel Playbook"
description: All Remote Channel Playbook
twitter_image: "/images/opengraph/all-remote.jpg"
twitter_image_alt: "GitLab remote team graphic"
twitter_site: "@gitlab"
twitter_creator: "@gitlab"
---
{{% alert title="Note" color="warning" %}}
The GitLab.tv initiative is on-hold indefinitely, and not accepting submissions.
The content continues to be available publicly as a useful resource on remote work.
{{% /alert %}}
## Introduction
![GitLab collaboration illustration](/images/all-remote/gitlab-collaboration.jpg)
The [GitLab.tv All-Remote Channel](https://www.youtube.com/playlist?list=PLFGfElNsQthY6t1i0UXYr0wFW3DuvWww6) 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. For additional context, visit the GitLab [All-Remote Marketing Handbook](/handbook/ceo/office-of-the-ceo/workplace/).
Ultimately, the GitLab.tv 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.
The GitLab.tv All-Remote Channel can help enable viewers to create a remote strategy and establish basic remote management processes. They can 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.
## GitLab.tv Playlist on YouTube
The GitLab.tv playlist is listed on GitLab's [official YouTube channel](https://www.youtube.com/playlist?list=PLFGfElNsQthY6t1i0UXYr0wFW3DuvWww6).
## Success Metrics
- Increase traffic from YouTube to key `/all-remote/` web pages to 200 monthly visits
- Increase overall views of All-Remote Channel videos 20% monthly
- One or more cross-promoted videos per month (e.g. a video created in collaboration with another organization which they share to their audience)
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
1. GitLab's All-Remote team
1. GitLab Team Members
## Audience
![GitLab customer illustration](/images/all-remote/gitlab-customer-path.jpg)
......@@ -44,71 +29,6 @@ The [GitLab.tv All-Remote Channel](https://www.youtube.com/playlist?list=PLFGfEl
1. **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.
1. **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
![GitLab values illustration](/images/all-remote/gitlab-values-tanukis.jpg)
To keep the All-Remote Channel focused on its intended [audience](/handbook/ceo/office-of-the-ceo/workplace/#our-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 and processes.
1. Remote culture stories from GitLab team members and external remote advocates.
1. GitLab CEO Sid Sijbrandji as a thought leader in the remote work space.
1. GitLab, the product, as a [key enabler of remote work](/handbook/company/culture/all-remote/gitlab-for-remote/).
1. 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 `remote@gitlab.com`. **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](https://drive.google.com/drive/folders/0B6i7Xg1yiB8tZWhKbzlsOFpfVDg?usp=sharing).
### 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:
- **Title:** Unless the interviewee(s) are very well known, don't lead with their names. Lead with the title of the discussion. For example, "Common stumbling blocks to going remote: A panel discussion." This will help the audience find your video based on their interests and let them know what style of video to expect.
- **Description:** Repeat the title of the video followed by the names and titles of the interviewee or panel members and 3-5 sentences explaining the key points of the discussion. Include timestamps if the video is over 10 minutes long.
- **Call to action (CTA):** Interview/panel style videos should include a link to `https://about.gitlab.com/company/culture/all-remote/` in the video description. Creators may choose to include the verbal CTA to **"Download GitLab's complete Remote Playbook"** at the end of their video.
- **UTM codes:** Please be sure to add a UTM code to your CTA in the video description when uploading your videos to YouTube. This **required** action is needed to track your video's performance. For videos related to All-Remote, the UTM code should follow this sequence: `?&utm_medium=social&utm_source=youtube&utm_campaign=allremote&utm_content={{video}}`
1. Right before the question mark at the start of the UTM code, please put the URL to the campaign/landing page to which your CTA is driving, i,e. if this is a video that drives to the top-level All-Remote page, the URL added before the question mark should take you to the All-Remote landing page. For example: `https://about.gitlab.com/company/culture/all-remote/?&utm_medium=social&utm_source=youtube&utm_campaign=allremote&utm_content={{video}}`
2. Please use a URL shortener, like [bit.ly](https://bitly.com/), once you add the campaign URL to the top of the UTM code sequence in order to avoid posting a clunky web address for your CTA.
- **Meta Tags:** Tag your video with the appropriate meta tags, including the keyword of the video. There may be multiple keywords associated with this style of video, depending on the topics covered. Tag the video with all relevant keywords. Other tags you might include on an interview/panel discussion video are: remote, all remote, GitLab, culture.
### How-To Videos
![GitLab journey illustration](/images/all-remote/gitlab-journey-and-navigation.jpg)
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](/handbook/ceo/office-of-the-ceo/workplace/#our-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:
- **Title:** The title of your video should describe exactly what you are showing in the video. For example, "How to submit a merge request on gitlab.com."
- **Description:** Repeat the title of the video followed by 3-5 sentences explaining what the viewer is going to learn from the video. If the video is longer than 10 minutes, include timestamps. If the video is referencing a contribution, link to the merge request.
- **Call to action (CTA):** How-to videos should include a link to `https://about.gitlab.com/company/culture/all-remote/` in the video description. Creators may choose to include the verbal CTA to **Download GitLab's complete Remote Playbook** at the end of their video.
- **UTM codes:** Please be sure to add a UTM code to your CTA in the video description when uploading your videos to YouTube. This **required** action is needed to track your video's performance. For All Remote-related videos, the UTM code should follow this sequence: `?&utm_medium=social&utm_source=youtube&utm_campaign=allremote&utm_content={{video}}`
1. Right before the question mark at the start of the UTM code, please put the URL to the campaign/landing page to which your CTA is driving, i,e. if this is a video that drives to the top-level All Remote page, the URL added before the question mark should take you to the All Remote landing page. For example: `https://about.gitlab.com/company/culture/all-remote/?&utm_medium=social&utm_source=youtube&utm_campaign=allremote&utm_content={{video}}`
2. Please use a URL shortener, like [bit.ly](https://bitly.com/), once you add the campaign URL to the top of the UTM code sequence in order to avoid posting a clunky web address for your CTA.
- **Meta Tags:** Tag your video with the appropriate meta tags, including the keyword of the video. Other tags you might include on a how-to video are: remote, all remote, GitLab, culture.
## Distribution
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 `allremote.info` web pages.
## Promotion
1. Submit to [GitLab social team](/handbook/marketing/integrated-marketing/digital-strategy/social-marketing/) for consideration ([DRI](/handbook/people-group/directly-responsible-individuals/) must create issue to enable this step)
1. Submit to GitLab editorial team for consideration on the blog and/or bi-weekly newsletter (DRI must create issue to enable this step)
1. Third-party content platforms (e.g. like ITPro.tv, industry blogs, etc.)
1. Highlighted on GitLab's weekly "This Week at GitLab" video series
1. Consideration for featuring in GitLab All-Remote video band
1. Featured in GitLab event follow up email/s (DRI must create issue to enable this step)
## Related links and material
1. [GitLab All-Remote Marketing Handbook](/handbook/ceo/office-of-the-ceo/workplace/)
......
......@@ -2,7 +2,7 @@
title: "Product and Solution Marketing Metrics"
---
## North Star Metrics (CEO (Sid) ask on North Star Metrics)
## North Star Metrics (CEO ask on North Star Metrics)
Every marketing function should have at least one north star metric that they aspire to improve over time to help GitLab's business growth.
Below is a list of metrics by different marketing functions in Product and Solution Marketing.
......
......@@ -44,7 +44,6 @@ When new posts or comments about GitLab are added to Hacker News, team members c
### Response workflow
1. When alerted by the "Hacker News Front Page Bot" that an article referencing GitLab is on the Front Page of Hacker News, the Developer Advocates should coordinate to ensure a DRI is assigned to the post to review, monitor the comments, and respond accordingly.
1. If the post is a result of a [Zap](/handbook/marketing/developer-relations/workflows-tools/zapier/#current-zaps) for which Sid is not tagged by the bot, verify that the post is relevant and, if so, ping @Sid in the thread on Slack.
1. Posts that reach the front page should be shared in Slack channels relative to the topic of the post for greater visibility among team members who may wish to respond. For example, a remote work blog should be shared in the [#remote](https://gitlab.slack.com/messages/remote) channel and a post related to trackers on our marketing site should be shared in [#marketing](https://gitlab.slack.com/messages/marketing). Whenever posts are shared outside of [#dev-advocacy-team](https://gitlab.slack.com/messages/dev-advocacy-team), the Slack comment should be cross-linked in the alert thread in `#dev-advocacy-team` for visibility and to create a single source of truth.
1. Developer Advocates should also review the [#hn-mentions](https://gitlab.slack.com/messages/hn-mentions) Slack channel 1-2 times per day for mentions that require a response. If you are able to provide a quick response/resource, reply on [news.ycombinator.com](https://news.ycombinator.com) using your personal Hacker News account and indicate that you replied by leaving a :white_check_mark: on the Slack comment. _Note that [the window to edit a comment is 2 hours](https://github.com/minimaxir/hacker-news-undocumented#editdelete-time-limits), afterwards you cannot edit or delete a Hacker News comment._
1. If necessary, you may also wish to share comments with relevant experts who may be able to provide more detailed or insightful comments. This can be done by sharing relevant posts or comments in an appropriate Slack channel if you judge additional input is required.
......
......@@ -26,7 +26,7 @@ We would much rather foster a culture where DRIs are willing to put their ideas
{{< youtube "jdN5mj5ieLk?start=1775" >}}
As part of a Harvard Business School case study [interview](https://youtu.be/jdN5mj5ieLk) (shown above), GitLab co-founder and CEO Sid Sijbrandij spoke with Professor Prithwiraj Choudhury on various elements of GitLab's all-remote structure, including a question on DRIs.
As part of a Harvard Business School case study [interview](https://youtu.be/jdN5mj5ieLk) (shown above), GitLab co-founder Sid Sijbrandij spoke with Professor Prithwiraj Choudhury on various elements of GitLab's all-remote structure, including a question on DRIs.
> How do we get the best of consensus organizations? When we're about to make a decision, we [tell everyone]({{< ref "communication" >}}). Everyone can give input.
>
......
......@@ -232,7 +232,7 @@ We're hiring across the company. Check out our opportunities: https://about.gitl
**HackerNews Notes:**
- Sid's HackerNews credentials should not to be used for the "Who's Hiring" post. The team member posting the comment should use their own account.
- The team member posting the comment should use their own account.
- When posting on HackerNews, remember that it is our most important social channel. Please follow the [best practices](/handbook/marketing/developer-relations/developer-advocacy/hacker-news/#best-practices-when-responding-on-hacker-news) and [social media guidelines](/handbook/marketing/developer-relations/developer-advocacy/hacker-news/#social-media-guidelines).
## Employer awards and recognition
......
......@@ -38,7 +38,7 @@ Feedback conversations are core to personal and professional growth. According t
## Guidance on Giving and Receiving Feedback
Sid (GitLab CEO and Co-founder) and the Learning & Development team discussed guidance on giving and reciving feedback during a [CEO Handbook Learning Session](https://docs.google.com/presentation/d/1u6k4ILLBjLOaGk1ZyuNa2U2qr-XiGZL0AhUjOQRtvVI/edit#slide=id.p1). The covered topics like:
Sid (GitLab co-founder) and the Learning & Development team [discussed guidance on giving and receiving feedback](https://docs.google.com/presentation/d/1u6k4ILLBjLOaGk1ZyuNa2U2qr-XiGZL0AhUjOQRtvVI/edit#slide=id.p1). The covered topics like:
1. How do you create an environment where team members can approach each other with feedback?
1. Why it is important to give regular feedback?
......
......@@ -131,17 +131,19 @@ After the Call:
### List of CEO Handbook Learning Sessions
[Playlist](https://www.youtube.com/playlist?list=PL05JrBw4t0KosJ72e_9DFZRFSKxlTm9DA)
1. [Common misperceptions about Iteration](https://www.youtube.com/watch?v=nXfKtnVUhvQ)
1. [No Matrix Organization](https://www.youtube.com/watch?v=E_wegGRv4mA)
1. [Making Decisions](https://www.youtube.com/watch?v=-by6ohMIi_M&feature=emb_title)
1. [Individual Contributor Leadership](https://www.youtube.com/watch?v=d0x-JH3aolM)
1. [Bias Towards Asynchronous Communication](https://www.youtube.com/watch?v=_okcPC9YucA&feature=emb_title)
1. [High Output Management](/handbook/leadership/high-output-management/#applying-high-output-management)
1. [High Output Management](https://www.youtube.com/playlist?list=PL05JrBw4t0Kp_xR7vrRiGu7URKiUmN8m3)
1. [Giving and Receiving Feedback](https://www.youtube.com/watch?v=vL864Zg2sm4&t=731s)
1. [Managing Underperformance](https://www.youtube.com/watch?v=-mLpytnQtlY&t=637s)
1. [Transitioning from IC to Manager - Engineering](https://www.youtube.com/watch?v=Zeull-tdy6o)
1. [Manager Mention Merge Requests](https://www.youtube.com/watch?v=e1sTOtveNOk)
1. [Working Groups](/handbook/company/working-groups/#ceo-handbook-learning-discussion-on-working-groups)
1. [Working Groups](https://www.youtube.com/live/tE3d8WUSL30)
1. [Skip Level Meetings](https://www.youtube.com/watch?v=kAxp0Mam-Rw)
1. [Product Strategy](https://www.youtube.com/watch?v=yI29xFAgKoA)
1. [Mental Wellness Discussion](https://www.youtube.com/watch?v=od_KdZqc69k)
......
......@@ -72,7 +72,7 @@ Note: this doesn't mean you can't get travel approval without booking meetings.
#### Trip Notes
The ultimate purpose of attending any GitLab field event is to gain insight and add value. Sid Sijbrandij, our CEO, talks about the importance of conferences and events [here](https://www.youtube.com/watch?v=qQ0CL3J08lI). He believes the main goal of GitLab team participation should always be to connect with our customers and prospects and not to solely attend presentations. Trip notes are our internal process for tracking and capturing this data.
The ultimate purpose of attending any GitLab field event is to gain insight and add value. Sid Sijbrandij, our co-founder, talks about the importance of conferences and events [here](https://www.youtube.com/watch?v=qQ0CL3J08lI). He believes the main goal of GitLab team participation should always be to connect with our customers and prospects and not to solely attend presentations. Trip notes are our internal process for tracking and capturing this data.
#### Why and When?
......
......@@ -174,7 +174,7 @@ description: "Core curriculum for GitLab's Sales & Customer Success onboarding"
### 7. Our Competition
- **The Industry In Which GitLab Competes (Material - Video - 11 Minutes)**
- Sid Sijbrandij, CEO of GitLab, discusses the overall industry where GitLab competes.
- Sid Sijbrandij, co-founder of GitLab, discusses the overall industry where GitLab competes.
- [You Tube - The Industry GitLab Competes In](https://www.youtube.com/watch?v=qQ0CL3J08lI)
- **ACTIVITY: Review & Subscribe: Industry Insights (Assignment - 1 Point - Pre Work)**
- Review and subscribe to the following blogs recommended by Sid to get the latest industry insights.
......
......@@ -35,7 +35,7 @@ As the account lead, your role centers on successfully orchestrating all of the
|[Channel Account Manager (CAM)](https://partners.gitlab.com/English/directory/):| Understand and map the partner landscape: opportunities and collaborations, suggest partners for onboarding and recruiting, incorporate System Integrators into your plan, view current partners in the [Partner Directory](https://partners.gitlab.com/English/directory/) |
|[Professional services](/handbook/customer-success/professional-services-engineering/working-with/):| Match the needs of your solution or customer to training, education, and adoption or deployment support provided by this team. Or bring them in to help you pitch services to your prospects or customers.|
|[Field marketing](/handbook/marketing/field-marketing/#whats-currently-scheduled-in-my-region) and account-based marketing:| Include this team during strategic planning for your territory, accounts, and pipe generation. And when planning to run & host events or webinars, attend relevant third-party events. Learn what's scheduled: [GitLab event site](https://about.gitlab.com/events/) , [All marketing activities (internal)](https://docs.google.com/spreadsheets/d/1ni6gKeWhjtrNppMdYvPESsCRjDbfVdYjTNtUtcNBFGg/edit#gid=571560493). Nominate priority accounts for [Account-based marketing (ABM) support](/handbook/marketing/account-based-marketing/abm-campaign-approach/). Slack: #abmteam, #emea_marketing (EMEA), #fieldmarketing (Global)|
| Sales leaders and executives | You may need to [provide executive sponsorship of an account](/handbook/sales/field-operations/gtm-resources/#executive-sponsorship-program), [request an e-group member in a meeting](/handbook/eba/#customer-prospect-and-partner-meetings-with-an-e-group-member), or [request that Sid join a meeting](/handbook/eba/ceo-scheduling/#how-to-request-a-meeting-with-ceo) |
| Sales leaders and executives | You may need to [provide executive sponsorship of an account](/handbook/sales/field-operations/gtm-resources/#executive-sponsorship-program), [request an e-group member in a meeting](/handbook/eba/#customer-prospect-and-partner-meetings-with-an-e-group-member), or [request that the CEO join a meeting](/handbook/eba/ceo-scheduling/#how-to-request-a-meeting-with-ceo) |
|[Sales operations and deal desk:](/handbook/sales/field-operations/sales-operations/deal-desk/) |For structuring and closing deals, you'll often work with Deal Desk, especially for non-standard quotes. #sales-support is also the go-to channel for any urgent questions around progressing a deal through our processes. |
| [GitLab Support](/handbook/support/): | The Support Team serves our customers at different levels depending on what they've purchased.|
|[Product team](/handbook/product/categories/): | For strategic deals, it often makes sense to bring in an expert from Product to speak to your customer about the benefits or maturity of features they care about the most. Often times, if something is not yet possible in GitLab, Product has a plan and roadmap for when it will be available. |
......
......@@ -138,7 +138,7 @@ The below channels are owned by teams outside of the field organization but migh
| #company-fyi | public (read-only) | Official company announcements channel |
| #company-fyi-private | private (read-only) | Official & confidential company announcements channel |
| #whats-happening-at-gitlab | public | Team-wide communication and announcements (reminders, events, project updates, etc.) |
| #ceo | public | Questions and requests for Sid |
| #ceo | public | Questions and requests for the CEO |
| #competition | public | Used to share competitive insight/information from the market in real time and to ask the competitive intelligence team questions about how they might handle certain situations |
| #support_ops-announcements | public (read-only) | Sharing updates on Support-related changes |
| #legal | public | General legal questions that are not confidential or seeking legal advice |
......
......@@ -28,14 +28,14 @@ and they are made actionable below.
<a href="#collaboration"><img style="height: 78px; padding-right: 20px; padding-bottom: 20px" src="/images/all-remote/gitlab-value-tanukis_collaberation.svg" alt="Collaboration" title="Collaboration" height="78"></a> <a href="#results"><img style="height: 78px; padding-right: 20px; padding-bottom: 20px" src="/images/all-remote/gitlab-value-tanukis_results.svg" alt="Results" title="Results" height="78"></a> <a href="#efficiency"><img style="height: 78px; padding-right: 20px; padding-bottom: 20px" src="/images/all-remote/gitlab-value-tanukis_efficiency.svg" alt="Efficiency" title="Efficiency" height="78"></a> <a href="#diversity-inclusion"><img style="height: 78px; padding-right: 20px; padding-bottom: 20px" src="/images/all-remote/gitlab-value-tanukis_diversity.svg" alt="Diversity, Inclusion &amp; Belonging" title="Diversity, Inclusion &amp; Belonging" height="78"></a> <a href="#iteration"><img style="height: 78px; padding-right: 20px; padding-bottom: 20px" src="/images/all-remote/gitlab-value-tanukis_iteration.svg" alt="Iteration" title="Iteration" height="78"></a> <a href="#transparency"><img style="height: 78px; padding-bottom: 20px" src="/images/all-remote/gitlab-value-tanukis_transparency.svg" alt="Transparency" title="Transparency" height="78"></a>
</p>
We take inspiration from other companies, and we always go for the [boring solutions](#boring-solutions). Our CEO, Sid Sijbrandij, has [shared the origin](/handbook/company/history/#value-origin-stories) of each of the CREDIT values, but
We take inspiration from other companies, and we always go for the [boring solutions](#boring-solutions). Our co-founder, Sid Sijbrandij, has [shared the origin](/handbook/company/history/#value-origin-stories) of each of the CREDIT values, but
just like the rest of our work, we continually adjust our values and strive to make them better.
GitLab values are a living document.
In many instances, they have been documented, refined, and revised based on lessons learned (and scars earned) in the course of doing business.
We used to have more values, but it was difficult to remember them all. In response, we condensed them, created an acronym (CREDIT), and listed operating principles to guide behavior.
Everyone is welcome to suggest improvements. Please assign MRs to update these values to our CEO Sid and @mention him in Slack if you work at GitLab Inc. or [on Twitter](https://twitter.com/sytses) if you don't.
Everyone is welcome to suggest improvements. Please assign MRs to update these values to our [Chief People Officer](https://about.gitlab.com/company/team/?department=people-group) and if you work at GitLab, also @mention them in the [`#values` Slack channel](https://gitlab.enterprise.slack.com/archives/C9VJYTVDE).
<div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/899882089?h=fceb9c5e64" style="position:absolute;top:0;left:0;width:100%;height:100%;" frameborder="0" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen></iframe></div><script src="https://player.vimeo.com/api/player.js"></script>
<p><a href="https://vimeo.com/899882089">Driving Results with CREDIT</a> from <a href="https://vimeo.com/gitlab">GitLab</a> on <a href="https://vimeo.com">Vimeo</a>.</p>
......@@ -74,13 +74,13 @@ One-on-one video calls are preferred.
Negative *feedback* is distinct from negativity and disagreement. If there is no direct feedback involved, strive to discuss disagreement [in a public channel](/handbook/communication/#use-public-channels), respectfully and [transparently](#transparency).
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder and CEO Sid Sijbrandij offers the following context.
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder Sid Sijbrandij offers the following context.
> We deal with negative all the time at GitLab. If it's not a problem, then why are we discussing it? We deal with negativity a lot, and that's also part of our ambition.
>
> If you want to get better, you talk about what you can improve. We're allowed to publicly discuss negative things; we're not allowed to give negative feedback in a large setting if it could be feasibly administered in a smaller setting.
Negative feedback can be given in a group setting if it's to someone higher in the management chain. This shows that no one is above feedback. GitLab co-founder and CEO Sid Sijbrandij and former CTO Eric Johnson discuss this in this [GitLab Unfiltered video](https://www.youtube.com/watch?v=BCpmFWL5Us8).
Negative feedback can be given in a group setting if it's to someone higher in the management chain. This shows that no one is above feedback.
##### Provide feedback in a timely manner
......@@ -853,7 +853,7 @@ Iteration enables [results](#results) and [efficiency](#efficiency).
{{< youtube id="2r0UeZ5p57Y" >}}
*In the [GitLab Unfiltered video](https://youtu.be/2r0UeZ5p57Y) embedded above, GitLab CEO and co-founder Sid Sijbrandij shares key operating principles to reinforce iteration in an organization.*
*In the [GitLab Unfiltered video](https://youtu.be/2r0UeZ5p57Y) embedded above, GitLab co-founder Sid Sijbrandij shares key operating principles to reinforce iteration in an organization.*
##### Start with a long-term vision
......@@ -933,7 +933,7 @@ If you need to decide something as a team, make a concrete proposal instead of c
By making a proposal you also provide better visibility into the work and the context surrounding it.
In this [GitLab Unfiltered video](https://youtu.be/tPTweQlBS54), GitLab CEO and co-founder Sid Sijbrandij converses about iteration in engineering, leveraging proposals to break work into smaller components.
In this [GitLab Unfiltered video](https://youtu.be/tPTweQlBS54), GitLab co-founder Sid Sijbrandij converses about iteration in engineering, leveraging proposals to break work into smaller components.
##### Everything is in draft
......@@ -1022,7 +1022,7 @@ Iteration is often counterintuitive and difficult to do. To clarify what an iter
1. Imposing long hours
1. Expecting others to fix your work
In this [GitLab Unfiltered video](https://www.youtube.com/watch?v=BW6TWwNZzIQ), GitLab co-founder and CEO Sid Sijbrandij elaborates on each of these 12 things that are not iteration.
In this [GitLab Unfiltered video](https://www.youtube.com/watch?v=BW6TWwNZzIQ), GitLab co-founder Sid Sijbrandij elaborates on each of these 12 things that are not iteration.
##### Iteration Competency
......@@ -1301,7 +1301,7 @@ We make our values public for the same [reasons](/handbook/company/culture/all-r
Not everyone will see our values and feel aligned with them, and that's OK. By making values public, it shows respect for the time of job seekers who conduct due diligence on prospective employers. When people who *are* aligned with GitLab's values apply for an [open vacancy](https://about.gitlab.com/jobs/), this allows our hiring teams to more efficiently move candidates through the [interview process](/handbook/hiring/interviewing/).
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder and CEO Sid Sijbrandij offers the following context.
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder Sid Sijbrandij offers the following context.
> Companies may ask you to write a blank check. They'll say, 'Come join our organization, and when you're here, you need to subscribe to our values, our way of working, and our strategy. It's very essential, and it's part of our identity!'
>
......@@ -1318,7 +1318,7 @@ Think of the hierarchy as a weighting system. Values higher in the hierarchy do
![Values](images/values.svg)
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder and CEO Sid Sijbrandij offers the following context.
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder Sid Sijbrandij offers the following context.
> It's an attempt to relieve at least some of the tension. It's not absolute. If you think of values as binary, that's not going to work. There will always be interpretation, and there's always magnitude to consider.
>
......@@ -1364,7 +1364,7 @@ In negative feedback, we should be specific about what the problem is. For examp
> Your values are what you hire for, what you praise people for, and what you promote them for. By definition, what you do in those instances *are* your values. It's not what you say they are. Values should be explicitly part of our [hiring](/handbook/hiring/) process, our job profiles, and our [review process](/handbook/people-group/360-feedback/).
>
> When we give [bonuses](/handbook/total-rewards/incentives/#discretionary-bonuses) and [promotions](/handbook/people-group/promotions-transfers/), they are always linked to values. That's the crucial thing. If you reinforce them there, that's the most powerful thing you can do. — *Sid Sijbrandij, GitLab co-founder and CEO*
> When we give [bonuses](/handbook/total-rewards/incentives/#discretionary-bonuses) and [promotions](/handbook/people-group/promotions-transfers/), they are always linked to values. That's the crucial thing. If you reinforce them there, that's the most powerful thing you can do. — *Sid Sijbrandij, GitLab co-founder*
## What to do if values aren't being lived out
......@@ -1372,7 +1372,7 @@ Value erosion can occur when indifference and apathy are tolerated. It can also
If you feel that values are not being lived out in a given scenario, speak up and ask for context in a respectful manner. Navigating value conflicts starts with [assuming positive intent](#assume-positive-intent) from other team members. Offer links to relevant values and/or operating principles when discussing the issue. If there is confusion or disagreement about the interpretation of a value, please surface the discussion in GitLab's `#values` Slack channel (for GitLab team members) or @-mentioning [@gitlab](https://twitter.com/gitlab) on Twitter (for those who do not work at GitLab).
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder and CEO Sid Sijbrandij offers the following context.
In a [GitLab Unfiltered interview on values](https://youtu.be/7kMQj4O4ZGU), GitLab co-founder Sid Sijbrandij offers the following context.
> Almost every time we face a hard decision at GitLab, it's because values are in conflict. It's not binary logic. It requires conversation, and sometimes there is no obvious answer. We can only achieve resolution by respectfully talking with each other and trusting the DRI to make the ultimate decision.
......
......@@ -155,7 +155,7 @@ To optimize the efficacy of delivered feedback, consider how other TeamOps tenet
{{% details summary="Examples and resources for transparent feedback" %}}
**Example:** [A member of GitLab's L&D Team Giving Feedback to the CEO](/handbook/people-group/guidance-on-feedback/#guidance-on-giving-and-receiving-feedback)
At GitLab, our mission that [everyone can contribute] even influences our feedback guidelines—suggesting that any team member, at any level, can give feedback to any other team member, at any level. In this video about [Guidance on Giving and Receiving Feedback](/handbook/people-group/guidance-on-feedback/#guidance-on-giving-and-receiving-feedback), the CEO of GitLab, Sid Sijbrandij, discusses this challenge in more detail, and asks for performance feedback from a member of the Learning & Development team.
At GitLab, our mission that [everyone can contribute](/handbook/company/mission/) even influences our feedback guidelines—suggesting that any team member, at any level, can give feedback to any other team member, at any level.
**Resource:** [Guide to Giving Remote Feedback](https://www.workplaceless.com/blog/guide-to-remote-feedback) (playbook)
{{% /details %}}
......
......@@ -69,14 +69,6 @@ In practice, a TeamOps organization uses a knowledge management system that allo
This type of system scales with much less effort, and scalable leadership is effective leadership. By writing guidance down transparently — in a way that others can modify, validate, or contribute to — leadership scales beyond an individual or team, and even beyond the organization.
{{% details summary="Examples and resources for public by default" %}}
**Example:** [Livestreaming company meetings on a branded YouTube channel](https://youtu.be/XcqloQezOUg)
Shortly after GitLab Chief Revenue Officer Michael McBride joined the company in 2018, he [livestreamed a 1-to-1 meeting](https://youtu.be/XcqloQezOUg) with GitLab co-founder and CEO Sid Sijbrandij. As part of McBride's onboarding, Sid was asked to provide an impromptu pitch of GitLab.
In a conventional organization, this interaction would likely be private and not recorded. By recording it and streaming it to the public on a branded YouTube channel, everyone is more informed — the two individuals on the call; GitLab team members past, present, and future; the wider community; customers and partners; candidates; et al.
{{% /details %}}
{{% details summary="Change management support for public by default" %}}
**Quick Start Tips:**
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment