Reach out to the EBA to the CEO in #eba-team with the required details to book a meeting with the CEO.
All meetings on Sid's calendar should be scheduled and vetted by the EBA to the CEO. Please do not directly schedule a meeting onto Sid's calendar without confirming with the EBA to the CEO in advance. The CEO requires meetings to originate from his calendar and on his Zoom account.
disable shushin advance of the next meeting.
For all external parties meeting with CEO (both video call and in-person), the EBA should include the following verbiage and links in the calendar invite:
GitLab is a very transparent company and materials that are normally confidential can be found online, please consider looking at the following Handbook links prior to your meeting with GitLab: Company strategy including planned going public date: https://about.gitlab.com/company/strategy/ Our Objectives and Key Results per quarter: https://about.gitlab.com/company/okrs/ All team members and numbers per department: https://about.gitlab.com/company/team/ Handbook with all our processes in: /handbook/ Pricing plans: https://about.gitlab.com/pricing/ Pricing strategy: /company/pricing/ History: https://about.gitlab.com/company/history/ About: https://about.gitlab.com/company/ All Remote: https://about.gitlab.com/company/culture/all-remote/ GitLab Unfiltered on YouTube https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A/videos
Contact details for external meetings should be collected in advance by the EBA to the CEO and listed in the calendar invite as:
ceo-evangelismand assigned to the Sr. Corporate Communications Manager, Executive Communications and EBA to the CEO.
As a rule of thumb, there should be 1 slide per minute of expected speech delivery.
The initial content review for the CEO should be in bullet points only. Then the CEO can talk through the slides and a team member can capture the CEO's tone of voice as he talks through the talk. This helps ensure the talk track is in the CEO's voice.
The Chief of Staff to the CEO is responsible for making sure that all of the CEO's Evangelism engagements are on our events page by updating the events.yml file.
If people want advice on open source, remote work, or other things related to GitLab we'll consider that. If Sid approves of the request we suggest the following since we want to make sure the content is radiated as widely as possible. To start, we send an email as shown below.
Thanks for being interested in GitLab. If we schedule a meeting it will follow GitLab's Pick Your Brain format. Are you able to submit a draft post with us within 48 hours of interview?
GitLab is a very transparent company and many things that are normally confidential can be found in our handbook, available online. Please consider looking at the following pages prior to our meeting.
Reply to emails: Thanks for wanting to chat. I propose we meet in the format proposed in GitLab's Handbook so that other people benefit from our conversation too. If you're up for that please work with my EBA, XYZ (cc:) to schedule.
Please note, requests for meeting about remote work, all-remote efforts, distributed workforces, etc should be scheduled with the Head of Remote versus Sid when possible.
/chief of staff,
/investor relations to handle,
Current preferences for flights are:
The EBA to the CEO will coordinate all meetings at Mission Control. If a group would like to visit GitLab's offices, please ping the EBA to the CEO in slack to discuss the opportunity. Due to limitations in size, we cannot host large groups but are willing to meet remotely and publicly. GitLab is an all-remote and distributed organization and we do not have a head office.
Access to Mission Control: In case of a meeting in San Francisco at Mission Control please copy-paste building access instructions into the calendar invite from the "GitLab Mission Control Access Instructions" Google Doc.