CEO Shadow Program
Was this helpful?
Was this helpful?
You are here:
CEO Shadow Program
At GitLab, being a CEO shadow is not a job title, but a temporary assignment to shadow the CEO. The shadows will be present at during their rotation. GitLab is an company, but the CEO has in-person meetings with external organizations. Unless you're joining the program during one of our , you will stay in San Francisco during the entire and travel with the CEO.
The goal of the CEO Shadow Program is to give current and future at GitLab an overview of all aspects of the . This should enable leadership to better perform . You'll gain this context through the and while short-term from across the company. The program also creates opportunities for the CEO to build relationships with team members across the company and to identify challenges and opportunities earlier. The shadows will also often connect with one another, developing new cross-functional relationships.
The CEO Shadow Program is not a performance evaluation or the next step to a promotion. Being a CEO shadow is not needed to get a promotion or a raise, and should not be a consideration factor for a promotion or raise, as diverse applicants have different eligibilities.
Apart from creating leadership opportunities, the CEO Shadow Program:
Leaves a great impression on both investors and customers
Gives feedback immediately to the CEO
Enables the CEO to create immediate change
Other names considered:
Considering joining the program? Hear from past shadows about their experience:
This is feedback received from some Alumni shadows and their managers
Hear what our CEO has to say about the CEO shadow program.
You are eligible to apply for the program if you have been with GitLab for at least 1 month (recommended more than 3 months) and you are a:
Considerations are cumulative and can be:
You are a recipient of GitLab’s Value Award of Transparency, Collaboration, Iteration, Efficiency, Results, or Diversity at previous GitLab Contribute events.
There is last minute availability. Last minute means the first day of a rotation is less than a month out.
You are based in APAC.
You're also eligible if you work(ed) at an investment firm and while there helped to lead a private round in GitLab.
Exceptions to eligibility:
COVID-19 Note: During this time, all shadow rotations are fully remote. Given the CEO generally works from 8 a.m. to 6 p.m. Pacific, it's best for remote shadows to be in Pacific, Mountain, or Central time zones. Other time zones will be considered on a case-by-case basis.
Shadows with scheduled rotations always have the option to delay to later in the year if they'd prefer to do their rotation in person. Shadows who have chosen to delay their rotations until another time include:
Jarka Kosanova
James Ramsey
Liam McNally
Bartek Marnane
Assign your manager and ask them to approve (but not to merge) the merge request. Managers, please ensure the candidate meets the eligibility criteria.
Please keep in mind when selecting dates that the CEO's schedule is fluid and subject to constant change, which also means that the CEO shadow rotation is subject to constant change. The posted dates are not guaranteed. We will work with you to reschedule your rotation if a conflict arises.
We understand that participation in the CEO Shadow Program is optional and can cause hardships at home. To help overcome these challenges and to allow flexibility for parents to participate, there will be some rotations identified as "parent-friendly" weeks. These are weeks where Sid doesn't need a shadow for the full 5 workdays or where the program is split so the weeks are not consecutive.
We want many people to be able to benefit from this program, therefore we rotate often. It is important that an incoming person is trained so that the management overhead can be light. Currently, a rotation is two weeks:
See one, you are trained by the outgoing person.
Teach one, you train the incoming person.
The shadow should be available for the full two weeks.
Start date
End date
See one
Teach one
2020-11-09
2020-11-13
2020-11-16
2020-11-20
2020-11-23
2020-11-27
NO CEO SHADOWS - Thanksgiving
NO CEO SHADOWS - Thanksgiving
2020-11-30
2020-12-04
2020-12-07
2020-12-11
2021-01-04
2021-01-08
2021-01-11
2021-01-15
2021-01-18
2021-01-22
AVAILABLE - REMOTE
2021-01-18
2021-01-22
AVAILABLE - REMOTE
AVAILABLE - REMOTE
2021-01-25
2021-01-29
AVAILABLE - REMOTE
AVAILABLE - REMOTE
2021-02-01
2021-02-05
AVAILABLE - REMOTE
AVAILABLE - REMOTE
2021-02-08
2021-02-11
AVAILABLE - REMOTE (Sales Kickoff)
AVAILABLE - REMOTE (Sales Kickoff)
2021-02-16
2021-02-19
AVAILABLE - REMOTE
AVAILABLE - REMOTE
2021-02-22
2021-02-26
AVAILABLE - REMOTE
AVAILABLE - REMOTE
The week of 2020-12-07 will be the last CEO Shadow Rotation of 2020 to allow our team members to focus on the holiday season and put family and friends first.
If you have questions regarding the planned rotation schedule, please ping the Staff Executive Business Admin to the CEO. The EBA to the CEO manages the rotation schedule, please do not add new dates to the schedule when adding in your rotation. The CEO's schedule is subject to constant change and your rotation may need to be rescheduled.
This is not a performance evaluation
Plan to observe and ask questions.
Don't plan to do any of your usual work. Prepare your team as if you were on vacation.
Participating in the shadow program is a privilege where you will be exposed to confidential information. This is underpinned by trust in the shadows to honor the confidentiality of topics being discussed and information shared. The continuation of this program is entirely dependent on shadows past, present, and future honoring this trust placed in them.
You do not need to dress formally; business casual clothes are appropriate. For example, Sid wears a button-up with jeans most days. GitLab shirts are acceptable when there aren't any external meetings. Review Sid's calendar to check if there are formal occasions - this may require different clothing. If unsure, please ask the Executive Business Administrator (EBA) in the #ceo-shadow Slack channel Make sure to bring comfortable shoes with you to Mission Control any time there are meetings in the city. Wear whatever you are comfortable in, keeping in mind that Sid prefers to walk, even if his calendar says Uber.
Before your scheduled rotation, try to schedule coffee chats with your co-shadows before you start the program. This gives you the opportunity to get to know them and help set expectations for the rotation.
Since your rotation is over a short period of time, there are no long-term tasks you can take on. However, there are many short-term administrative tasks you'll be asked to perform as shadow. Here are some examples:
Iterate and complete small tasks as they come up. Clear them out immediately to allow for rapid iteration on more crucial tasks. Communicate updates on those tasks in the #ceo-shadow channel.
Solve urgent issues. For example, help solve a complaint from a customer or coordinate the response to a technical issue.
Compile a report on a subject.
Ensure visual aids and presentations are visible to guests during in-person meetings.
Prepare for and receive guests at Mission Control.
Offer GitLab swag to guests at Mission Control before they leave.
Answer the phone and door at Mission control.
Provide training to the incoming CEO Shadow(s).
At the start of the week, review the CEO's calendar. The CEO's calendar is the single source of truth. Shadows should check the CEO's calendar for updates often. You will not be invited to each meeting. Meetings that the shadows may not attend will have a separate calendar entry on the CEO's schedule that states "No CEO Shadows". When in doubt, reach out to CEO Executive Business Admin to confirm if you should attend or not. There will be some meetings and events the shadows do not attend. Do not feel obligated to attend every meeting — all meetings are considered optional.
Add the CEO's calendar to your Google Calendar by clicking the + next to "Other Calendars". Then click Subscribe to Calendar, search for the CEO's name, and click enter.
Because candidate interviews are marked as "private" (busy) for confidentiality reasons, the Executive Business Admin will invite the shadows to those events directly. As a result, you will get an email from Greenhouse asking for candidate feedback, which is not necessary.
Meetings with those outside of GitLab may not be on Zoom. Prior to the call, check the CEO's calendar and load any other conferencing programs that may be needed. It may be necessary to dial in via phone for audio-conferences. If you have any problems confirming the link, reach out to the #ceo-shadow slack channel
There are three types of meetings one the CEO's calendar: GitLab meetings, Valley meetings, and personal meetings. Please note, the program's continued success depends on the participants respecting confidentiality during the program, after the program, and after they leave GitLab.
GitLab Meetings
You will attend all GitLab meetings of the CEO, including but not limited to:
Interviews with candidates.
Conversations with board members.
Like all meetings at GitLab, meetings will begin promptly, regardless of the shadows' attendance. You will travel with the CEO to meetings, team off-sites, and conferences outside of San Francisco per the CEO's schedule. Executive Business Admin to the CEO will assist you with conference registration and travel accommodations during these time frames.
The CEO's Executive Business Admin will ask external people if they are comfortable with the shadows joining prior to the scheduled meeting, and will share a link to the CEO shadow page to provide context.
Meeting agendas should be shared with ceo-shadow@gitlab.com, as shadows will be added to this email alias prior to the rotation, and removed at the conclusion of it. For agendas that contain sensitive information, the sensitive information should be removed and the document shared with "View only" access to restrict access to the document's history. Not all agendas will be shared, though, and the CEO Shadows should feel empowered to ask for access if that is the case. Sometimes, the answer will be "no" for sensitive reasons.
These meetings can have different formats:
Video calls.
In-person meetings.
Dinners that are business related.
Customer visits.
Conferences.
You will not attend a meeting when:
Someone wants to discuss a complaint and wants to stay anonymous.
If any participant in the meeting is uncomfortable.
If the CEO wants more privacy.
Social calls
Media Briefings
CEO Shadows may be the point of contact for helping coordinate (not schedule) media briefings. Take initiative, for example finding a quiet space for the CEO to take the call, if it is done while traveling. When participating in media briefings, CEO Shadows are to act as silent participants, except when directly asked a question.
Candidate Interviews
If the candidate is comfortable with it, CEO shadows will attend interviews performed by the CEO. When scheduling an interview with the CEO, the EBA to the CEO will create a shared Google Doc for notes between the shadows and the CEO. The doc template can be found by searching "Notes Doc for Candidate Interviews" in Google Drive. If you have any questions, please @ mention the EBA to CEO in #ceo-shadow in Slack. This notes document is then added to the scorecard for the candidate in Greenhouse.
Shadows should ensure they mark comments they provide with their full name.
Please do not complete the automated Greenhouse report that follows the interview, entitled REMINDER: Please fill out your scorecard for [NAME]. CEO shadows are asked to simply delete this email.
Valley Meetings
The CEO may occasionally invite you to optional meetings that may not be explicitly GitLab related, but can help provide insight into his day-to-day activities. In these meetings, it is asked that you not take notes because we don't want you to do work that isn't for GitLab. Additionally if the agenda document is not shared with you most likely it is because it is owned outside of the GitLab domain therefore request access is not advised. However, keeping time can still be very helpful so you are encouraged to do so if you are in attendance. These meetings are optional and you can leave at any time.
Personal Meetings
Personal meetings will be marked as "busy" on the calendar. Shadows do not attend personal calls.
For certain meetings, such as Valley Meetings, a CEO Shadow may be added to an agenda document that is accessible to people outside of the GitLab organization.
At the conclusion of the call, the CEO Shadows should remove themselves from document(s) they were added to via the following steps.
Click the Share button atop the Google Doc
On the resulting pop-up, click into Advanced
Click the X by your name to remove yourself
Click Save changes
On the resulting Are you sure? dialog box, click Yes
You should see a dialog appear noting that Your access has expired
Meetings come in many different formats, as listed above. Your responsibilities will change based on the kind of meeting. Here are the responsibilities shadows have during meetings:
Taking notes
Tips:
It's helpful if shadow one takes notes as the first speaker is talking, then shadow two starts when the next speaker continues the conversation. Shadow one can pick up note taking again when the next speaker contributes. By alternating this way, the shadows are better able to keep up with all the participants in the conversation.
Add extra blank lines after a bulleted or numbered line to make it easier for multiple notetakers to type notes. In the agenda provided, press enter to add a numbered line, followed by a space and press enter again to create a blank line (as Google documents will not allow a numbered line to be empty).
Consider clicking somewhere in the document where people are not actively reading or writing so that your name next to the cursor doesn't hide that text.
Showing up one to two minutes early to a meeting may give you an opportunity to network with GitLab team members who you do not know.
Put Zoom in "gallery mode" so you can see all participants (rather than only the person currently speaking). This allows everyone to see the entire audience which creates a more inclusive environment and fosters better communication.
If you aren't sure where meeting attendees are in a Google document, click on their face or initials in the upper-right side of the window. Doing this will cause your cursor to jump to wherever their cursor is in the document.
It can be challenging to coordinate with the other shadow on who is taking notes at any point in time. Consider agreeing with the other shadow to "show your hands" in Zoom to indicate that you are not currently taking notes.
Keeping time
Shadows should also notify meeting participants if a meeting is running over the allocated time by saying "we're in overtime".
If you see something, say something
Shadows need to speak up in video calls, and speak up when the CEO's camera isn't working or when the green screen isn't working correctly because of the sun angle.
At the start of meetings, CEO shadows will introduce themselves. There is no set order for which shadow introduces themselves first. Sometimes one shadow will arrive to the meeting first, and make their introduction as the first shadow to speak. The terms first and second shadow define the order of who has decided to speak in any relevant meeting.
When introducing yourself in a meeting as the first shadow, say:
I'm NAME.
I normally am a/the TITLE.
This is my first/last week in the two-week CEO shadow program.
The goal of the program is to give participants an overview of the functions at GitLab.*
*For Valley meetings: The goal of the program is to give participants an introduction to Silicon Valley discussions.
When introducing yourself in a meeting as the second shadow, say:
I'm NAME.
I normally am a/the TITLE.
This is my first/last week in the two-week CEO shadow program.
Remember, do not say that your role is to "follow the CEO around". It's about getting an overview of the functions at GitLab.
When attending events with the CEO, keep the following in mind:
Remind the CEO to bring extra business cards before leaving. And bring a few for yourself.
When traveling to events in the Bay Area by car, the CEO will request the ride sharing service.
When traveling to events on foot, CEO shadows should take responsibility for navigating to the event.
After a talk or panel, be ready to help the CEO navigate the room, particularly if there is a time-sensitive obligation after the event.
The CEO often has work events that are also social events. In Silicon Valley, social and work are very intertwined. These mostly take the form of lunches or dinners. CEO shadows are invited unless otherwise specified, but there is no expectation or obligation to join.
Verbalize questions
Stop sharing their screens to encourage conversations
Provide full context for the benefit of new team members
In order to ensure continuity across CEO shadow participants. Always, cc ceo-shadow@gitlab.com on emails as part of the program. This ensures that even after you've left the program the response and follow-up can be tracked.
CEO shadows label the handbook MRs they create with the ceo-shadow label. It's a point of competition between CEO shadows to try to best the previous shadows number of merge requests.
Shadows are encouraged to follow the CEO's activity on various platforms to get a complete picture of his everyday activities and where he directs his attention.
Go to the Slack search bar and type "from:@sid" and it will populate the results.
Follow Sid's Slack activity to follow his everyday engagements
See what issues and MRs Sid is interacting with
Sign up for Twitter notifications (Twitter account required) to follow his everyday engagements.
An ongoing shadow program with a fast rotation is much more time consuming for the CEO than a temporary program or a rotation of a year or longer. That's why most organizations choose to either have a shadow for a couple of days, or have someone for a year or more. We want to give as many people as possible the opportunity to be a shadow, which is why we rotate quickly. To make this happen without having to invest a lot of time with training, we need great documentation around the program. A quick turnaround on documentation is crucial, and the documentation will have a level of detail that may not be necessary in other parts of the company.
When traveling with the CEO, keep the following in mind:
Book flights that will allow you to land before the CEO so there is no delay in transportation to the next event.
For airport pickup with the CEO, research the terminal the CEO arrives in and plan to be there to meet with the driver before the CEO.
Keep the EBA to the CEO and onsite EBA updated regularly and promptly on estimated arrival time in #ceo-shadow Slack channel to ensure the schedule is on time.
If travel plans change, please update the EBA(s) in Slack immediately so cancellations to prior transportation can be made promptly to not incur fees.
While remote shadows won't get to work from Mission Control or attend in-person meetings with the CEO, they will still get an immersive experience through the program. A remote rotation may also be an ideal opportunity for a team member who has been unable to travel for an in-person rotation in the past.
Communicate clearly with your co-shadow about shared tasks since you will not be working together in person.
Consider alternating who leads note-taking from one meeting to the next, which reduces confusion on who writes first and who follows from one event to the next.
You are welcome to work from Mission Control, but it is not required to be there in person unless there is an in-person meeting, event, or dinner. It's up to you to manage your schedule and get to places on time. If you are traveling somewhere, meet the CEO at Mission Control at the beginning of the allotted travel time listed on the calendar.
If there is a day during your rotation where all meetings are Zoom meetings, you can work from wherever you want, as you normally would. You can also work from Mission Control if you prefer. If you decide to split your day between remote work and working from Mission Control, make sure you give yourself enough time to get to Mission Control and set up for the guest. It's OK to join calls while mobile. In addition, feel free to coordinate or join a co-working day with team members in the Bay Area. To coordinate join the #loc_bayarea Slack channel.
Shadows are welcome at Mission Control 10 minutes prior to the first meeting until 6 p.m. Feel free to ask if you can stay later. Don't worry about overstaying your welcome, if Karen or Sid would like privacy they will ask you to leave explicitly. When you arrive and depart, please make sure the door to Mission Control closes fully.
One more thing: the cat feeder is automatic and goes off daily at 10:22am PT (as well as another time, it's a surprise!). No need to be alarmed by the metallic clanging sound.
Outside of Mission Control hours, shadows have the following options:
If not an in-person meeting, you are welcome to take the meeting from your lodging and then proceed to Mission Control during the Group Conversation.
There are coffee shops with early opening hours with Wifi access near Mission Control. This is a great venue to meet with your co-shadow if coordination is needed before heading in.
When entering the building, the doorperson may ask who you are there to see. Don't say "GitLab" since there is no GitLab office. The doorperson will direct you to the correct lobby.
While there are two sets of keys, it's worthwhile coordinating access to Mission Control with the outbound shadow on your first day. Meeting up on Sunday evening or at a specific time on Monday morning. This will enable the incoming shadow to be introduced into Mission Control without impacting Sid and/or Karen.
The list is administered by the ceo-shadow@ email address. Log in to Yelp with the credentials in the CEO Shadow 1Password vault to add restaurants, update notes, or remove items from the collection.
Tye Davis Favorite (AMAZING COFFEE) - long walk
Occasionally, food trucks or restaurants have loyalty rewards cards. It is not required but if you get one and want to leave it for future shadows to use, please add to this list and put the reward card in the CEO shadow drawer at Mission Control.
We have six monitors at Mission Control. They show the following content:
Configuring the Monitors
Turning all screens on or off might be challenging, since a single remote controls all of them. The easiest way to do that is by covering the tip of the remote with your hand and getting as close as possible to a single screen while turning it on or off.
To configure the sales dashboards:
Go To Pulse tab.
Open the left side bar.
Click on the funnel icon. Select “CRO”.
Click on the gear icon. Go to Forecasting. Select Net IACV.
How to use keyboard and mouse to update screens
The wireless mouse and keyboard are connected to the bottom left TV by default because that one is visible from both sides of the conference table. To update the view on another TV, you have to connect the wireless keyboard and mouse to the desired screen. Afterward, don't forget to return it to the bottom left position for use during meetings.
Find the USB jacks and Logitech receiver underneath the bottom, right TV (they're all labeled).
Connect the Logitech receiver to the USB receiver for the desired screen.
Troubleshooting the monitors
Turning all screens on or off might be challenging since a single remote controls all of them. The easiest way to do that is to make a cone with the foil (a piece of foil can be found on the white TV-remote tray) around the front edge of the remote, and getting as close as possible to a single screen while turning it on or off.
Updating the software on the monitors
To check that a Samsung TV is up to date:
Grab the remote labeled for the TV
Hit the home button
Go to "Settings"
Go to "Support"
Select "Software Update"
Select "Update Now"
To screencast from an iPad or MacBook to the top left screen, switch the "Source" on the top left screen to "Apple TV" (HDMI 2).
Using the larger remote (with the white buttons), you can press the white center button in the top row of buttons; this will bring up a list of sources. There is a direction pad on the remote towards the bottom that has < ^ > v buttons, as well as the selection button in the center.
When the TV is on the Apple TV source, you may need to change the Apple TV to AirPlay mode. The Apple TV remote is the small black one with only 5 buttons. You can click "MENU" until it says AirPlay.
To return to the normal configuration, choose "Source" then "HDMI 1".
The printer at Mission Control is called HP Officejet Pro 8610 and is available over AirPlay/Wifi. The printer is located in Sid's office.
Zoom Rooms is an application used for team members not in San Francisco to participate in meetings happening at Mission Control. There's a separate screen (the large one on wheels), a Mac Mini and, iPad at Mission Control for this purpose. The Mac Mini is connected to HDMI1 on the screen, and the iPad operates as a remote control for Zoom Rooms.
Setup
Turn on the big screen on wheels.
Turn on the Mac Mini.
Start the Zoom Rooms application on the Mac Mini.
Start the Zoom Rooms application on the iPad (you may need the passcode).
If there's any problem connecting to the service, log out and back in. If that fails, contact the Executive Admin to the CEO.
If you do not have the option to join a meeting on the iPad (It's in "Scheduling mode" - you don't have a "Meet Now" or "Join" button):
Make sure Zoom Rooms on the iPad is logged in.
Click the settings "gear" icon in the top right hand corner.
Disable the "lock settings" option (you'll need the passcode).
Tap on "Zoom Room Mission Control".
Tap "Switch to Controller".
If the Zoom Rooms app on the iPad is not connecting:
Log out of the Zoom Rooms app on the iPad.
If the EBA to the CEO is unavailable, the CEO shadow may be responsible for handling the technical details of coordinating Zoom meetings. If using a webinar, you will need to be a co-host in order to promote participants to panelists so that they can verbalize their own questions.
When joining a podcast in Zencaster, a microphone error can be avoided by leaving your microphone unmuted for the first 30 seconds / minute.
Zencaster checks that your mic is working by recording audio so, muting the mic causes the error.
The system check happens when you first load the page
If you get the microphone error, reload the page and wait for the checks to finish before muting.
The devices in Mission Control are configured to auto-update when new versions are available. As a precaution, shadows in their second week should confirm all software in Mission Control is up to date.
In preparation for guests (customers, investors, etc.) who will be meeting with the CEO or other team members at Mission Control, please note the following prior to the meeting start:
All GitLab team members sit on one side. This allows for easy communication with the guests.
Set the lighting mode to 'Evening' - lighting controls are located next to the kitchen entrance.
Have drinks from the fridge (on the tray) available on the table.
Get the glasses from the cupboard above the coffee machine and place them next to the drink tray.
Add the Brita water pitcher on the table.
Place the keyboard and the mouse (used for Mission Control screens) on the table.
Move the screen to the head of the table.
Click 'Join' in the Zoom Rooms menu and enter the meeting ID from the Google Calendar invite of the meeting in question.
Once the meeting is loaded, click on the participants list and make sure that the iPad is visible from the table.
The front desk will call the apartment when a visitor arrives.
A Shadow should meet guests at the elevator, greet them, and guide them to Mission Control.
Once the meeting is over, a Shadow should escort the guests back to the elevator.
Suzy likes attention and will invite you to pet her. If you're allergic to cats consider washing your hands after petting. If you don't want to wash your hands every time after petting Suzy you can gently paddle pet her using ping pong paddles available in Mission Control. Check out the videos linked below for techniques! Please note the white pillow on the sofa in Mission Control is the only place to paddle pet Suzy. She really enjoys it when you gently pat her sides with the ping pong paddles when she is on the white pillow, if she steps off the pillow stop petting her. When she gets back onto the pillow you can resume gently paddle petting her. Please don't pet her after/when she meows since that reinforces the meowing which can be annoying during calls and the night. You can pick her up but she doesn't like it much and will jump out after about 30 seconds. Lastly, Suzy sometimes tries to drink out of the toilet, please make sure to leave the toilet lid down.
Everything in the fridge that is liquid can be consumed including Soylent and alcohol.
The thermometer is located next to the kitchen entrance.
Lighting controls are located next to the kitchen entrance, select 'Evening'.
Swag (socks and stickers) is located on the bookshelf near the dashboards. (If the swag is running low, reach out to the Executive Admin to the CEO with a list for restocking)
Everything in the fridge that is liquid can be consumed including Soylent and alcohol. The coffee machine is located in the kitchen, coffee pods are in the drawer below the coffee machine.
If the beverages are running low, start by checking the top cupboard above the oven (next to the fridge). There's a step ladder in the laundry (last door on the left down the hallway) If items in the cupboard are also running low, reach out to the Executive Admin to the CEO list of items that need to be ordered in the #ceo-shadow slack channel tagging the EBA to the CEO so all items can be ordered at once. This should happen every Monday. Here is a list of items that may need to be restocked:
La Croix (usually there are 3 flavors)
Red Bull
Sugarfree Red Bull
Sprite Zero
Coca Cola
Diet Coke
Fiji water
Soylent Cacao
Snacks in the lockbox (try to keep enough so that the box is full) - Preferences of snacks for the incoming shadow and restocking any snack preferences from the outgoing shadow.
Lodging during the CEO shadow program is provided by the company. Executive Admin to the CEO books the accommodation based on availability and cost. You can express your preference (hotel or AirBnB) via email to the Executive Admin to the CEO in question. However, the final decision is made by the Executive Admin based on the distance from the CEO and costs. Executive Admin will provide the accommodation details no earlier than 1 month and no later than 2 weeks before the scheduled rotation.
Accommodation is provided only for the active shadowing period, it is not provided during the shadow program pause (cases when the CEO is unavailable). In case you are coming from a timezone that is more than 6 hours difference with Pacific Time, it is possible to book the weekend before the first shadow work day to adjust to the new timezone.
If your CEO shadow rotation is two consecutive weeks, it is expected you will be staying the weekend. Accommodation is provided during the weekend.
At San Francisco International airport (SFO), all rideshare apps (Uber, Lyft, etc) pick up on level 5 of the parking structure. When coordinating travel from SFO to Mission Control with other Shadows, GitLabbers or Sid arranging to meet on level 5 of the parking structure is most efficient as each terminal has its own baggage claim area.
Past Childcare facilities that have been accommodating:
CEO Shadow program alumni are welcome to join the #ceo-shadow-alumni Slack channel to stay in touch after the program.
Start date
End date
Name
Title
Takeaways
2019-03
2019-04
Manager, Content Marketing
2019-04
2019-05
Alliances Manager
2019-04
2019-05
Sr. Technical Marketing Manager
2019-05
2019-06
Evangelist Program Manager
2019-06
2019-06
Sr. Product Marketing Manager
2019-06
2019-06
MBA Candidate at Stanford University
2019-06
2019-06
PMM, Competitive Intelligence
2019-06
2019-07
Support Engineering Manager
2019-07
2019-07
Engineering Manager, Deliver
2019-07
2019-08
Danae Villarreal
Sales Development Representative, West
2019-08
2019-08
Engineering Manager, Package
2019-08
2019-08
Data Engineer, Analytics
2019-08
2019-08
Director of Product, Ops
2019-09
2019-09
Director of Product, Dev
2019-09
2019-10
General Manager, Meltano
2019-10
2019-10
Director of Quality
2019-10
2019-11
Mid Market Account Executive
2019-10
2019-11
Frontend Engineering Manager, Monitor:Health
2019-11
2019-11
Sr. Solutions Manager
2019-11
2019-11
Sr. Product Manager, Plan: Project Management
2019-11
2020-01
Technical Account Manager
2020-01
2020-01
Senior Product Manager, Monitor
2020-01
2020-01
Senior Product Manager, Plan : Portfolio Management
2020-01
2020-01
Staff Backend Engineer, Search
2020-01
2020-02
Manager, Compensation & Benefits
2020-01
2020-02
Senior Manager, People Operations
2020-02
2020-02
Senior Support Engineer
2020-02
2020-02
Technical Account Manager
2020-02
2020-02
Senior Product Manager - Monitor: Health
2020-02
2020-03
Support Engineering Manager
2020-03
2020-03
People Ops Fullstack Engineer
2020-03
2020-03
Technical Account Manager
2020-03
2020-04
Sr Product Manager
2020-04
2020-04
Frontend Engineer
2020-04
2020-04
Chief of Staff
2020-04
2020-04
Technical Account Manager
2020-04
2020-04
People Operations Specialist
2020-04-28
2020-05-08
Senior Talent Brand Manager
2020-05-04
2020-05-15
Head of Remote
2020-05-11
2020-05-22
Manager, Corporate Events
2020-05-11
2020-05-22
Diversity, Inclusion & Belonging Manager
2020-05-25
2020-06-05
Senior Technical Account Manager
2020-06-01
2020-06-19
Senior Product Manager, Release Management
2020-06-15
2020-06-26
Director Engineering, Defend
2020-06-22
2020-07-03
Area Sales Manager - Public Sector
2020-06-28
2020-07-17
Director of Product, Growth
2020-07-13
2020-07-31
Director of Product, Secure & Defend
2020-07-20
2020-08-10
Senior Product Manager, Package
2020-08-10
2020-08-21
Technology Alliances Manager
2020-08-17
2020-08-28
Senior Product Manager, Defend
2020-08-24
2020-09-04
Account Executive, SMB
2020-08-31
2020-09-11
Sr. Solution Architect
2020-09-07
2020-09-18
Acceleration SDR
2020-09-07
2020-09-24
Engineering Manager, Fulfillment
2020-09-21
2020-10-02
Distinguished Engineer, Secure & Defend
2020-09-28
2020-10-05
Area Sales Manager, SMB - US East
2020-10-05
2020-10-23
Strategic Content Lead
2020-10-19
2020-10-30
Sr. Solutions Architect
2020-10-26
2020-11-06
Acceleration SDR
This is why the program is worth the extra overhead for the CEO and .
For now, this role is called a to make it clear to external people why a shadow is in a meeting.
Technical assistant: This title could be mixed up with the role. .
Chief of Staff: This commonly is the which is not the case for this role since people rotate out of it frequently.
This is too long if only the CEO is shadowed.
, Distinguished engineer or up ( or ), or in the People Group
, Staff engineer ( or ), , , or , if there is 1 consideration.
, if there are 2 considerations. This includes TAM and SA roles.
You belong to a select under-represented group as defined in our . Multiple under-represented groups are cumulative.
You belong to a GitLab Team Member Resource Group ()
CEO Shadow rotations will be reserved for during the week of . An exception will be made if there is last minute availability as two All-Directs are not available to serve in this role during this window.
Learn more about what to expect from a .
Create a merge request to add yourself to the . Ensure the merge request description highlights how you meet the eligibility criteria (merge request examples: , , ).
Assign the merge request to the , link to the merge request in the #ceo-shadow channel, and @mention the Executive Business Admin supporting the CEO in the message.
When the CEO has a week or more of paid time off, or during , the program will pause, one shadow will "see one" before the break and "teach one" after the break. The rotations with breaks of one or more weeks without a shadow are great if you can't be away from home for more than one week at a time.
If you need childcare to be able to participate, GitLab will for it.
This program is not limited just to long-term GitLab team members. For new team members, this might even be the first thing they do after completing our . Exceptional community members may be able to participate, as well.
- Mid-Market Account Executive - Commercial
- Technical Marketing Manager - Secure and Defend
- Business Systems Analyst
- Mid-Market Account Executive - Commercial
- Group Product Manager, Release, Configure, Monitor
- Business Systems Analyst
- Sr. Backend Engineer, Plan
- Group Product Manager, Release, Configure, Monitor
- Quality Engineering Manager, Secure & Enablement
- Sr. Backend Engineer, Plan
- Senior Manager, Digital Experience
- Quality Engineering Manager, Secure & Enablement
- Senior Manager, Digital Experience
Be ready to add a number of updates during your shadow period.
Give feedback to and receive feedback from the CEO. Participants in the shadow program are encouraged to deliver . Examples of this are to the CEO and to the world about the company if they make a blog post or video. Shadows maintaining confidentiality during the program is separate from shadows being able to provide candid feedback.
You will get asked about yourself during the program, and it's important to describe it correctly. So stand in front of a mirror and practice 3 times. The main point is, do not say that your role is to "follow Sid around" or "follow the CEO around". The program is for exploring and learning about all the parts of GitLab, and there's where the emphasis should lie. See for specifics.
Feel free to schedule a coffee chat with any of the CEO Shadow Alumni. You can review the list of below. These chats can be helpful when deciding whether to apply to participate or if you're unable to participate but want to hear about the experience and what alumni have learned while shadowing.
Should it be useful or complementary to your time as a CEO Shadow, our hosts Monthly Shadow Chats on the 3rd Tuesday of every month at 08:30 PST. Please @ mention the CLO's in #ceo-shadow should you wish to be added to an instance or you would like to schedule a 1:1 coffee chat with the CLO. This option is available to all Shadows, past, present, and future.
Outgoing shadows are responsible for training incoming shadows. We currently track onboarding and offboarding in the project. The incoming shadow is responsible for creating their onboarding issue by the Friday before they start the program using the . Assign both incoming and outgoing shadows to the issue. Don't forget to prepare your offboarding on your second week by creating another issue using this time the .
CEO Shadows use the project to track issues and coordinate the requests that result from the . It is linked in the CEO Shadow channel description on Slack. Check out the ongoing CEO Shadow tasks on the .
Review the to get an idea of what your upcoming weeks will be like.
The CEO has a that details processes and workflows specific to him as well as his background, communication style, strengths, and flaws. Take time to invest in your relationship with him upfront by reviewing this part of the handbook. Here are some helpful sections:
The value of the CEO Shadow Program comes from the you'll gain and the interesting conversations you'll witness.
Make handbook updates (use the label). Post the MR links in the #ceo Slack channel and @-reference the CEO so the CEO knows they have been completed. It is not required to create issues for these tasks. Go directly to a merge request if it is more .
Prepare for, take notes during, and follow up on meetings. See more details below about your
Go through open merge requests and work towards merging or closing any that have .
Publicly advise when people are not following the (). For example, remind team members to stop screen sharing to encourage communication.
Share in the #thanks channel in Slack when it comes from a customer or wider community member in a meeting.
Write an unfiltered blog, a recorded reflection of your experience, or a CEO Interview on a topic of your choice. Please see for information about the publishing process, and be sure to read previous CEO shadows' blog posts before you start writing to ensure that your post has a new angle. Link this to the table in the section. These do not need to be approved by the CEO but he will happily review them if you'd like.
Speak up when the .
The CEO shadows maintain a project called . It is linked in the #ceo-shadow Slack channel description. Collect tasks using the first name of the shadow who captured it and the name of the person that will complete the task. Once an MR has been opened, post in the #ceo-shadow channel.
As a reminder, you should have your title updated within your last name on zoom. During the Shadow rotation update your title to "CEO Shadow". update your title as part of your last name to ensure it shows up on zoom.
with reports.
When it comes time for the , CEO shadows should attend on their own. You are encouraged to share your experience as a shadow with your call group while you are shadowing.
Assume that you are taking notes in a Google Doc affixed to the meeting invite unless it is a between the CEO and his direct reports, a board meeting, an internal meeting where the CEO is not the host, legal discussions in any meeting, or it is explicitly stated not to take notes. If you're unsure whether or not to take notes, default to take them or ask the CEO. The goal of the notes is to collect the main points and outcomes, not a full transcript of the conversation. In many cases, shadows may not understand fully what is being discussed. As you are taking notes, be mindful that the goal of the program is to absorb what is being said in the meetings you are in. When you do not understand what it is being said, pause to listen and avoid documenting incorrect information. It is critical that any legal discussions are not put in notes since notes are frequently not reviewed for errors but that status might not be clear to people outside the company. If a notes document is not already linked, see the .
Shadows are responsible for being aware of the current time and providing a verbal 5-minute warning to the meeting participants so that they can comfortably wrap up the meeting. Don't wait for a break in the conversation, just say 'we have 5 minutes left.' Please use the calendar invite as an indication of how long the meeting should last. We do . Note: Just like notes, timekeeping is not required for 1-1s between the CEO and direct reports.
You can use this (MacOS only) to run a timer for the desired number of minutes. The script will notify you 5 minutes before the end of the meeting, and will copy "We have five minutes left" to you clipboard, so you can paste the text directly in the Zoom chat. At time, the same will occur with "We are at time". To use the script, download it, and use source setalarm.sh in your MacOS terminal to load the setalarm function. Then simply type setalarm 50 to set a 50-minute timer (setalarm defaults to 25 minutes if not argument is provided).
Shadows should notify GitLab meeting participants if their are not mentioned on Zoom.
If you notice that someone does not have their picture set in Google when a Google document is being actively worked on, so their picture will show up in the document rather than their first initial. That makes it easier for everyone to find where they are in the document, especially when they are speaking. Let them know that this is 100% optional.
If Sid records a video to the cloud in a meeting it will eventually end up being uploaded to folder. Finding the video will require searching based on the calendar event name and checking the "last modified" date.
The CEO has outlined his .
Even in meetings where you are unfamiliar with the subject matter, there is opportunity to learn, document, and shape the evolution of . Re-read GitLab's values prior to your CEO Shadow rotation, and be mindful of new and inventive ways that is lived out during the meetings you attend. You can make a merge request to propose new , which substantiate top-level values.
It's important that everyone encourages others to follow the , not just the CEO. As shadows, in Group Conversations and other settings, you should remind team members to:
When someone starts a Group Conversation with a presentation it is the CEO Shadow responsibility to ask them to stop and Recommendation on how to approach this message "Apologies for the interruption, it is the responsibility for the CEO Shadow to remind team members that we do not present during Group Conversations. If we may move to the document for questions and in the future consider recording a video to promote asynchronous presentations".
This can be seen on the CEO's .
Check out .
When returning to San Francisco, if on a different airline, be sure to arrive before the CEO and communicate a together.
The CEO Shadow Program is temporarily fully remote because of COVID-19 . The shadows will participate in all meetings from their usual work environment.
For insights on maximizing a remote CEO Shadow rotation, view takeaway recap videos from (Talent Brand Manager) and (Head of Remote), as well as Darren's .
Be sure that you have an . You'll be taking lots of notes during meetings, and will want a comfortable setup.
Take breaks from your desk when there is a break in the CEO's schedule. Because you're not working from Mission Control or traveling to other meetings with the CEO, it's important to take time to
Depending on your time zone, working in Pacific Time may be an adjustment to your typical working hours. especially if you're balancing responsibilities with family, pets, roommates, etc.
Consider switching locations in your home or workspace during the CEO's 1:1 meetings. Since you in these calls, this is a good opportunity to change position or scenery intermittently throughout the day.
Particularly in a remote CEO Shadow rotation, life is more available to sidetrack you. It is OK if you need to drop from a meeting to handle tasks at home, from childcare to answering the door, or anything in between. GitLab puts . If feasible, communicate these instances in the #ceo-shadow Slack channel so your co-shadow can assist with ongoing note-taking/tasks.
, opens at 05:30am.
, opens at 05:30am.
, opens at 05:00am.
, opens at 04:00am.
There is a that contains recommendations from previous shadows, as well as the .
There are usually also food trucks in front of the Salesforce Tower and on the opposite side of Mission Street from the Salesforce Tower .
Food Truck
Go to .
To log into the chrome devices at Mission Control, use the login information in the "" in 1Password.
Each of the screens at Mission Control use an Asus Chromebit to display the preferred content and are connected to the HDMI1 port of each TV. If you turn on the TVs and one displays a blank screen while on the HDMI1 input, the Chromebit may need to be reset. You can do this by power cycling the Chromebit (they are located behind the bottom right TV and are labeled), connecting the Chromebit to the , and logging into it using the credentials in the "" via 1Password. Once you have logged into the Chromecast, you can quickly find the proper content as listed in via the browser's recent history.
There are two iPads at Mission Control (without password protection). You can use the as a second monitor if desired. Both iPads are linked to the EBA to the CEO's Apple ID. Please verify any purchases ahead of time with the EBA to the CEO.
If you have to log in or, provide a passcode, both are in the .
Check the credentials for the Zoom Room in the . If unable to log in, please contact the Executive Admin to the CEO on slack.
Log in using the PeopleOps Zoom account credentials in the .
Ensure that all 6 monitors are displaying the . If any of the screens are blank, follow the .
For investor or banker meetings, see the with more details on preparations. As a precaution, do not discuss anything related to company performance (i.e. bookings, pipeline, quota attainment, and pricing), the current quarter, or products in development, other than those announced. These restrictions are meant to enforce and avoid the accidental dissemination of material nonpublic information.
If someone is attending a meeting at Mission Control via :
Follow the setup steps for .
Please note that we have a cat named . It is a Russian Blue mix which is a .
Airfare can be booked according to our or policy. In case your shadow rotation includes time without shadowing, it is possible to expense airfare to fly home and back within the continental USA. If you are from outside of the USA, it is also possible to expense airfare during the time without shadow because of the possible high cost of lodging in San Francisco if you chose to stay at a different location.
Shadows are able to expense food and beverage during their rotation and should follow our policy. Previous shadows have created a of their favorite food places to help.
Childcare is provided during the active shadowing period and will be reimbursed via your expense report. You must book the childcare yourself and it is advised you reach out far in advance as childcare "drop-ins" can be limited depending on the week. Currently, GitLab doesn't have a program so you must tell the childcare it is for a "drop-in". Depending on your hotel accommodations, finding a nearby daycare is most convenient or a daycare nearby the . Some childcare facilities will require payment at end-of-day or end-of-week via cash/check only so request an invoice/receipt for expense submission purposes.
- This facility is nearest the .
Contact:
Our top priority is the health and safety of our team members, please refer to the current . The CEO Shadow program is classified as non-essential travel and travel to San Francisco will not be required during the time frame specified in the policy linked. CEO Shadows joining the program should plan on participating in the program remotely and matching the CEO's schedule which is primarily in the Pacific time zone unless the CEO is traveling to another time zone. If you have questions please use #ceo-shadow in slack and @ mention the
and : What is the GitLab CEO shadow program? Why should you apply to participate? How did I see the GitLab values in action?
,