Commit 612a4b66 authored by Ashton Herrmann's avatar Ashton Herrmann

Update URL for Group Conversations (formerly FGUs) and fix broken links

parent 79584578
Pipeline #33052343 passed with stages
in 26 minutes and 11 seconds
......@@ -311,7 +311,7 @@ responsibility, willingness of GitLabbers to teach new GitLabbers, transparency,
1. More face-to-face meetings and ability to meet up with GitLabbers close by.
* Please expense travel to visit GitLabbers as described in [Spending Company Money](/handbook/spending-company-money).
1. Adjust the team call format to include more regular functional group updates.
* The [team call](/handbook/communication/#team-call) now has weekend updates every two weeks, a separate call for APAC GitLabbers to give their weekend update, and [functional group updates](/handbook/people-operations/functional-group-updates/) are separate events.
* The [team call](/handbook/communication/#team-call) now has weekend updates every two weeks, a separate call for APAC GitLabbers to give their weekend update, and [functional group updates](/handbook/people-operations/group-conversations/) are separate events.
1. Have more employee agreements instead of contractor agreements.
* People Ops will be working to establish new entities/payrolls in more countries as we grow. Once this is completed we can transfer contractors to employees.
1. Hire in departments that need more GitLabbers.
......
......@@ -31,7 +31,7 @@ In on-site companies they take processes, camaraderie, and culture for granted a
We have had success bonding with our coworkers in real life through our [Summits](/culture/summits/) that are organized every 9 months and our [Visiting Grants](/handbook/incentives/#sts=Visiting grant).
We have a daily [team call](/handbook/communication/#team-call) to talk about what we did outside of work. There is also a daily [functional group update](/handbook/people-operations/functional-group-updates/) in which one department shares their progress and challenges.
We have a daily [team call](/handbook/communication/#team-call) to talk about what we did outside of work. There is also a daily [functional group update](/handbook/people-operations/group-conversations/) in which one department shares their progress and challenges.
Our [expense policy](/handbook/spending-company-money/) provides for equipment, internet service, office space if they want that, and a local holiday party.
......
......@@ -78,7 +78,7 @@ Pages. For more information, see the [functional group updates handbook page].
The source repository for these updates is [functional-group-updates]. The
README contains more information on how they are built.
[functional group updates handbook page]: /handbook/people-operations/functional-group-updates/
[functional group updates handbook page]: /handbook/people-operations/group-conversations/
[functional-group-updates]: https://gitlab.com/gitlab-org/functional-group-updates
### The due-22nd Label
......
......@@ -88,7 +88,7 @@ Any changes to the handbook as part of this review will be shared in the `#handb
## Screenshare the handbook instead of creating a presentation
Presentations are great for ephemeral content like [functional group updates](/handbook/people-operations/functional-group-updates/) and board presentations. [Evergreen content](https://www.thebalance.com/what-is-evergreen-content-definition-dos-and-don-ts-2316028) like a [leadership training](/handbook/leadership/#training) should be based on the handbook. Please screenshare the handbook instead of creating a presentation for evergreen content because:
Presentations are great for ephemeral content like [group conversations](/handbook/people-operations/group-conversations/) and board presentations. [Evergreen content](https://www.thebalance.com/what-is-evergreen-content-definition-dos-and-don-ts-2316028) like a [leadership training](/handbook/leadership/#training) should be based on the handbook. Please screenshare the handbook instead of creating a presentation for evergreen content because:
1. It saves you the effort of creating a presentation.
1. People can easily find the handbook section later on.
......
......@@ -11,7 +11,7 @@ title: "Group Conversations"
## Introduction
Over the years, GitLab has had Functional Group Updates, which are regular updates from a group at GitLab.
Over the years, GitLab has had Functional Group Updates, which are regular updates from a group at GitLab.
For examples please see recent dates in [a search for them](/blog/#stq=functional+group+updates&stp=1).
We are evolving FGUs to no longer be updates, but to be conversations. The slides and trainings included below are still relevant but should be considered the starting point for a great conversation with other team members around the work that your group is doing. All team members at GitLab should be feel comfortable and encouraged to join these conversations, not just as a listener to the content, but as a participant in the conversation.
......@@ -76,7 +76,7 @@ In this video our CEO, Sid gives our team tips and tricks for their FGU. This st
For instructions on how to create a blog post, please see our [Blog Handbook](/handbook/marketing/blog/#create-a-new-post).
Please copy the code block below and paste it into a blog post with the file name `yyyy-mm-dd-functional-group-updates.html.md`.
Please copy the code block below and paste it into a blog post with the file name `yyyy-mm-dd-group-conversation.html.md`.
```md
---
......@@ -91,7 +91,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Company call](/handbook/#company-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Company call](/handbook/#company-call), a different Group initiates a [conversation](/handbook/people-operations/group-conversations/) with our team.
The format of these calls is simple and short where attendees have access to the presentation content and presenters can either give a quick presentation or jump straight into the agenda and answering questions.
......
......@@ -24,7 +24,7 @@ Welcome to the People Operations handbook! You should be able to find answers to
- [Global Compensation](/handbook/people-operations/global-compensation/)
- [Incentives](/handbook/incentives)
- [Hiring process](/handbook/hiring/)
- [Functional Group Updates](/handbook/people-operations/functional-group-updates)
- [Group Conversations](/handbook/people-operations/group-conversations)
- [Leadership](/handbook/leadership/)
- [Learning & Development](/handbook/people-operations/learning-and-development/index.html)
- [Courses](/courses/)
......@@ -86,9 +86,9 @@ If an ex team member acted in a malicious way against GitLab we'll do a company
## Business Cards
If you need business cards, please [send a request via Google Forms](https://docs.google.com/forms/d/e/1FAIpQLSdstKb6nfh9SxxcGUlbxypLeIBPvncJDqQMuDMJwqPSvDjmmQ/viewform?usp=sf_link). Someone on the team will place the order and email you with confirmation.
If you need business cards, please [send a request via Google Forms](https://docs.google.com/forms/d/e/1FAIpQLSdstKb6nfh9SxxcGUlbxypLeIBPvncJDqQMuDMJwqPSvDjmmQ/viewform?usp=sf_link). Someone on the team will place the order and email you with confirmation.
- If you need them for an event, please also include the date by which you need them delivered.
- If you need them for an event, please also include the date by which you need them delivered.
- The default order is for 50 cards unless otherwise noted, so if you need more please add a note in the form.
## NPS Surveys
......
......@@ -9,7 +9,7 @@ This role reports to the Director of Recruiting and works daily to support the P
* Monitor the People Ops and Recruiting email aliases and Slack channels and assist team members and candidates with any questions or concerns they may have
* Monitor the [Team Call](/handbook/communication/#team-call) and agenda
* Monitor the [Functional Group Updates](/handbook/people-operations/functional-group-updates/) (FGUs)
* Monitor the [Functional Group Updates](/handbook/people-operations/group-conversations/) (FGUs)
* Consistently create GitLab blog posts with FGUs and upload FGU videos to Youtube
* Conduct direct sourcing efforts to assist the recruiting team in identifying qualified candidates.
* Assist with keeping BambooHR (HRIS) up to date; upload documents, log assets, etc.
......
......@@ -9,7 +9,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
## Functional Group updates
Every day from Monday to Thursday, right before our [GitLab team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
## Recordings
......
......@@ -7,7 +7,7 @@ categories: company
description: "The Functional Groups at GitLab give an update on what they've been working on"
---
Every day from Monday to Thursday, right before our [GitLab team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -8,7 +8,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -8,7 +8,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -8,7 +8,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -8,7 +8,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -8,7 +8,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -9,7 +9,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -9,7 +9,7 @@ description: "The Functional Groups at GitLab give an update on what they've bee
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -10,7 +10,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -10,7 +10,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -10,7 +10,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Thursday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -16,7 +16,7 @@ _On November 17, Mike Knoop and Noah Manger of Zapier [sat down with GitLab’s
We have a #working-on Slack channel but I’m working on killing it because I just don’t care what people in another part of the company are working on. I just don’t care. There are just too many people at 200 people.
What works really well for us are the [functional group updates](/handbook/people-operations/functional-group-updates/). Every day of the week there’s a presentation (for a maximum of 25 minutes) by a team lead with a slide deck of what they’re working on, and there's an opportunity to ask questions. So you get to stay updated about what all the development teams are doing, what sales is doing, what marketing is doing, what legal is doing, what partnerships is doing. It’s on a three-week rotation so 15 different functional areas and then we start over from the top.
What works really well for us are the [functional group updates](/handbook/people-operations/group-conversations/). Every day of the week there’s a presentation (for a maximum of 25 minutes) by a team lead with a slide deck of what they’re working on, and there's an opportunity to ask questions. So you get to stay updated about what all the development teams are doing, what sales is doing, what marketing is doing, what legal is doing, what partnerships is doing. It’s on a three-week rotation so 15 different functional areas and then we start over from the top.
**Do you measure how many people consume this content?**
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
......@@ -11,7 +11,7 @@ tags: inside GitLab, functional group updates
<!-- beginning of the intro - leave it as is -->
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/functional-group-updates/) to our team.
Every day from Monday to Friday, right before our [GitLab Team call](/handbook/#team-call), a different Functional Group gives an [update](/handbook/people-operations/group-conversations/) to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment