Group Conversations are recurring 25 minute meetings providing regular updates across all GitLab teams on a rotating schedule. Functions with a Key Meeting will also be scheduled for a Group Conversation with the exception of Legal. Team member attendance is optional for Group Conversations.
The Executive Business Administrator Team, also known as EBA Team are responsible for scheduling these events which should automatically appear within the GitLab Team Meetings Calendar from 08:00am to 08:25am Pacific Standard Time (PST) from Monday to Thursday. Some days might not have a Group Conversation. These are listed in the schedule as Available. If you would like to be added to the GC rotation, please submit a merge request to this page.
All Team Members are invited to participate Group Conversations by adding questions and comments in the Group Conversation Agenda, a Google Doc linked in the respective calendar invite.
Non-confidential Group Conversations are streamed live and shared publicly to our GitLab Unfiltered YouTube channel. Confidential Group Conversations which are not streamed live or shared publicly to YouTube include Finance; Sales; Security and Partnerships.
Group Conversations at GitLab were previously known as Functional Group Updates (FGU) and were renamed because they're not presentations or updates but rather conversations - the term Functional Groups is now encompassed by the use of Departments.
In this video our CEO, Sid gives team members tips and tricks for hosting a FGU which are still relevant and applicable to Group Conversations.
Below is a guide to ensure evenryone gets the most out of Group Conversations. If you have suggestions for improving the Attendee or Meeting Leader experience please create a Merge Request (MR) to update this page — everyone can contribute!
It's common to wonder what the difference is between these two meetings. Generally, they cover the same or similar content, but for different audiences.
|Key Meeting||Group Conversation|
|Audience||Management||General GitLab Team|
The Key Meeting is intended for updating management on progress, while the Group Conversation is open to the entire GitLab team and is a good place for sharing news and explaining initiatives. Here's a brief discussion of why we have both meetings, and how they can operate effectively:
The Host of a Zoom call is the person leading the conversation, usually the DRI, subject matter expert and overseer of the slides created for a call (another term for the role is Presenter).
Questions will generally be directed to the Host, and they will usually answer them unless they feel that another team member has more information or expertise to offer. The Host/Presenter makes sure that questions are asked in the order they are listed in the agenda document.
The "Host" term can be confusing as Zoom has a specific definition for Host pertaining mainly to a permission level, which in practice GitLab does not assign to the term. More information on Zoom's definition of "host" is explained in the Moderator section below.
Before you host your first Group Conversation, please be sure complete this Group Conversation Training Issue which will support you in your preparations.
The Moderator of a Zoom call is the person that has Zoom's Host level permission. Host level permission in Zoom permits streaming a call to YouTube, starting or ending a recording and giving co-hosting permissions to others.
The Moderator of a Zoom call is the person who is in charge of starting the call i.e. initiating the streaming to YouTube; updating the stream from public to private if a sensitive topic is mentioned, and keeping the meeting running efficiently and on time so that it does not go over the Quick Meeting time frame.
Attendance of Group Conversations is optional - if you are unable to attend a Group Conversation at its scheduled time, don't let that hold you back! Watch the latest Group Conversation on the GitLab Unfiltered YouTube Channel. Alternatively Public Group Conversations can also be found in the GitLab Unfiltered Podcast.
If you have questions around an upcoming Group Conversation or would like to start a discussion, please be sure to bring it to the
#group-conversations Slack channel and @tag the presenter!
Calls are scheduled by the EBA Team. If you need to reschedule, please switch your presenting day with another Group Conversation leader, by asking another leader in the #group-conversations channel publicly. The Executive Business Administrator team is not responsible for finding a replacement for your day. If you've agreed to switch, please do the following:
If you will be out of office on the day of your Group Conversation, or need a person other than the DRI listed in the Schedule & DRI table to Host:
If your Group Conversation falls on a day when you feel that a large percentage of the company may be OOO (for example, a Public Holiday observed by a number of countries). In such instances:
@exec-admins) in Slack in your thread and ask them to move your regularly scheduled GC to the open slot you have found. This will be a one-time move and all other instances of your GC will stay as scheduled.
All Zoom meetings now require passwords. If a Group Conversation event was created in Zoom (in the EBA Zoom account) prior to this rule, please update the GC event in Zoom and in the GitLab Team Meetings calendar.
A little bit of preparation can go a long way in making the call worthwhile for everyone involved. People tend to spend at least an hour to prepare their updates.
Use presentations to document everything people should know about your group. These presentations are for attendees to review and generate questions from for the call. You can also record and upload a YouTube video if there is additional context that would be beneficial to supplement with the slides. Functions with Key Meetings should not create a new deck for a Group Conversation but should use their Key Meeting deck for the Group Conversation.
Please remember that you should NOT present during a Group Conversation. Synchronous calls are for conversation and discussion. It is the responsibility of the attendees to prepare questions before the call to maximize value of time spent synchronously. If someone does start to present the slides in the group conversation everyone is encouraged to say: 'At GitLab we use meetings for conversation and not presentation, but please do consider recording a video for next time.' Expect to be interrupted if presenting more than a 15 second welcome statement.
There are three layers of content in a presentation:
We try not to cancel a GC. We prefer to have half-prepared GCs over delaying them, but occasionally there may be a last-minute cancellation. If a Group Conversation is cancelled, the EBA Team should ask a member of the E-Group to host a Pop-up AMA. These should be called Pop-up AMAs so it's clear to team members that the AMA was added to the calendars solely as a function of a GC cancellation.
Groups that also have Key Meetings should repurpose material created for their last Key Meeting in the Group Conversation immediately following the Key Meeting. This is to give the broader team exposure to progress against key metrics and objectives that are key to the business and to reduce content duplication. Groups with Key Meetings will have a monthly GC.
Cheri Holmeswhen posting
EBA team are responsible for moderating the following calls on a rotational basis:
The teams will assist with moderating calls where the audience is applicable to all GitLab team members. In the event that a separate meeting needs to be scheduled on the team calendar with only a specified invitee list, the host or the EBA for the host's organization will be responsible for moderating the call.
All Group Conversations (Public and Private) will be streamed to YouTube within the GitLab Unfiltered channel. Guidelines around streaming including initiating the livestream and troubleshooting should you hit a snag can be found on the YouTube Uses and Access page.
Additional links which may be useful when preparing to moderate a call include:
#group-conversationsSlack channel at least 24 hours prior to confirm whether they will be hosting or have nominated another team member to do so.
Group Conversation Agendato ensure there are 15 numbered lines below the Date; Topic; Host Name; and Slide Deck Link - this is where team members will be able to insert any questions they may have for the host.
5-minutes priorto the start of the Group Conversation using `EBA Zoom Account' if you are successfully logged into Zoom as the GitLab Moderator the Tanuki Logo will be visible in the upper right hand corner of your Zoom screen.
manage participants featureif necessary.
System Preferences, opening
Date and Timepreferences, and selecting
Display the Time with Seconds.
Please grant necessary Privilege for Livestreamingpops up, click on the option that appears beside the GitLab Unfiltered account in the middle of the page reading
Not Me- you will then be prompted to sign in again, please do so and click
Go Liveafterwhich Zoom should indicate
Live on YouTubein the upper left hand orner.
End Meetingand then
End Meeting for Allwithin Zoom - making this selection should end both the call and the stream - should this not be the case it is more than likely because an outdated version of Zoom is being used and the moderator will need to log directly into YouTube Studio and manually end the stream.
Speaker Viewsetting on Zoom.
There is a rotating schedule with each Department having a conversation on a regular interval. We usually do not have Group Conversations or Company calls between December 23rd and January 2nd. We also tend to cancel these during Contribute.
In FY21 Q4, we'll move our Group Conversations to an eight week cycle. Functions with key meetings will have monthly Group Conversations during this period. They are expected to largely leverage their Key Meeting material. Other groups will have one meeting in the eight week cycle. The schedule, with directly responsible individuals (DRI), is as follows starting FY21 Q4:
|One||Wed||Revenue Marketing||Evan Welchel|
|One||Fri||Do Not Schedule||Do Not Schedule|
|Two||Tues||Learning and Development||Josh Zimmerman|
|Two||Thur||CRO Group Conversation||Michael McBride|
|Two||Fri||Do Not Schedule||Do Not Schedule|
|Three||Fri||Do Not Schedule||Do Not Schedule|
|Four||Fri||Do Not Schedule||Do Not Schedule|
|Five||Tue||Strategic Marketing||Ashish Kuthiala|
|Five||Fri||Do Not Schedule||Do Not Schedule|
|Six||Mon||Inbound Marketing||Danielle Morrill|
|Six||Tue||UX Research||Sarah Jones/Adam Smolinski|
|Six||Wed||CRO Group Conversation||Michael McBride|
|Six||Thur||Community Relations||David Planella|
|Six||Fri||Do Not Schedule||Do Not Schedule|
|Seven||Fri||Do Not Schedule||Do Not Schedule|
|Eight||Fri||Do Not Schedule||Do Not Schedule|
We suggest each person attend via their own device to avoid hybrid meetings. We encourage you to follow up with your guest after to debrief and share call impressions. For this it might be good to be in the same room but only if you are sure not to get echo's.
email@example.com the meeting.
If an agenda document becomes longer than 10 pages, the People Experience or People Specialist team member assigned to moderate a meeting will archive the content that is over the first 10 pages. All agenda docs should be checked and archived as needed before the meeting date and time.
Archiveat the end.
DOC NAME Archiveand link to the Archive doc.
A possible agenda for the call is: