This page is intended to be helpful, feel free to deviate from it and update this page if you think it makes sense. If there are things that might seem pretentious or overbearing please raise them so we can remove or adapt them. Many items further down this page are a guideline for our Executive Assistants (EAs).
Transparency and directness are part of our values and I want to live them by sharing the flaws I know I have. I'm fully responsible for improving the things below, listing them is no excuse. They are listed here for two reasons. The fist one is so that people know it is not them but my fault. The second one is so I can improve, I hope that listing them lets people know I appreciate when people speak up about them.
I look serious all the time, it is OK to say 'maybe you can smile more'.
I love debating, it is OK to say 'please stop debating and start collaborating' or 'we should have a dialectic instead of a debate'.
My English pronunciation, choice of words, and grammar are not great. I'm taking lessons but I welcome corrections when we're having a 1:1 conversation and/or when it might confuse people.
When in a rush I will jump to conclusions, it is OK to ask 'can we take more time to discuss this'.
I sometimes make reports feel like I'm scolding them, as in being angry for a percieved fault. It is OK to say, I don't mind you making that point but your tone doesn't make me feel respected.
In my feedback I sometimes sound more like I'm giving an order instead of offering a suggestion, even when I mean the latter. It is OK to say 'that sounds like an order, I would have appreciated it more in the form of a suggestion'.
If you speak up about them I should thank you for it, it is OK to say 'this was on your list of flaws so I kinda expected a thank you'. I'm sure I have more flaws that affect my professional life. Feel free to send a merge request to add them or communicate them anonymously to People Operations so they can send a merge request.
Thanks to Mårten Mickos for the inspiration for this section. All good idea's are his, all bad ones mine.
I am a visual person much more than auditory, and I am a top-down person much more than bottom-up. This means that I love written communication: issues, email, Google Docs, and chat. Feel free to send me as many emails and chat messages as you like, and about whatever topics you like.
If you have a great new idea or suggestion for me, I appreciate if you can convey it in a picture or in written words, because I learn by seeing more than I learn by hearing. I don't mind if you send me or point me to plans that are in draft mode or not ready. I am happy if I can give useful feedback early. It doesn’t have to be perfect and polished when presented to me.
In written communication, I appreciate the top-down approach. Set the subject header to something descriptive. Start the email by telling me what the email is about. Only then go into details. Don't mix separate topics in the same email, it is perfectly fine to send two emails at almost the same time. Try to have a concrete proposal so I can just reply with OK if that is possible.
I get many email on which I am only cc'd on, I would very much appreciate if you started emails intended specifically for me with "Sid," or some other salutation that makes it clear that the message is for me.
I have accounts on LinkedIn and Facebook. I will not send invites to team members on those networks since as the CEO I don't want to impose myself on anyone. But I would love to connect and I will happily accept your LinkedIn and Facebook friend request. You can also find me on Twitter as @sytses.
Pick your brain meetings
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 send the following email:
We would love to help but we want to make sure the content is radiated as wide as possible. Can we do the following?
We schedule a 50 minute Zoom video call or visit to our office that is recorded by us, uploaded to Youtube as a private video, and shared with you.
You write up a draft post within 48 hours after the interview in a Google Doc and share that with us with suggestion or edit rights for anyone that knows the url.
You can redact anything you don't want to publish.
Our marketing department will work with you to publish the post.
The EA will create an issue once it's scheduled with the label ceo-interview on GitLab.com should follow up to make sure the draft post is submitted.
Reply to emails: Thanks for wanting to chat. I propose we meet in the format proposed on https://about.gitlab.com/handbook/people-operations/ceo-preferences/#pick-your-brain-meetings so that other people benefit from our conversation too. If you're up for that please work with Kirsten (cc:) to schedule a time and location.
Alternatively we can also make it a YouTube live event, people can ask us questions in the chat during the event, and we can share the recording later.
Labels: /archive, /respond or /urgent-important
Prepare draft responses
Standard reply for recruiters: “We do not accept solicitations by recruiters, recruiting agencies, headhunters, and outsourcing organizations. Please find all info on our jobs page”
You can add other calendars on the left, to see when GitLab team members are free to schedule a meeting with
The agenda of items to be handled by the EA for the CEO
Use for example a tool like Skyscanner to find different flight options with most airlines when needing to book travel
Keep 1 hour open in calendar per day for email
Schedule calls in European timezones in the morning (am) Pacific (Daylight) Time and US time zones in the afternoon (pm) Pacific (Daylight) Time
After each meeting with a potential investor, make sure to update the sheet with the information on these meetings (to be found in the agenda doc for EAs)
Formats for invites
MTG for meetings in person, either at the "office" or another location. Example: MTG | Bruce Armstrong (Khosla) & Sid Sijbrandij (GitLab) @ [office/location]” or “Dinner/Lunch @ Bar Agricole - Kirsten Abma & Sid Sijbrandij”
INTERVIEW for interviews (looping in our PR partner) Example: “INTERVIEW | Kirsten Abma (TechCrunch)” Make sure to block 10 min before for preparations and 10 min after for notes for Sid
PHONECALL for phone calls
VIDEOCALL for video conference calls using Zoom. Using the Zoom plugin for Google Calendar you can easily get the info you need in the invite. Example: “(VIDEO)CALL | Kirsten Abma for Executive Assistant”
Make sure to include in the description
(Video)calls Please read our primer as preparation for this meeting: https://about.gitlab.com/primer (Calls in the hiring process also have: and please fill out this form a day in advance, to discuss during the call: https://docs.google.com/a/gitlab.com/forms/d/e/1FAIpQLScXUW07w36Ob2Y2XQuESBaYqU5_c1SoweGS1BzGHnbesISGXw/viewform to discuss during the call”) Phone number participant: By using the Zoom extention mentioned in our handbook it will add the details how to join the Zoom call automatically. Make sure to remove the Hangout link first and then use the Zoom extention.
Meetings at the office: Please read our primer as preparation for the meeting: https://about.gitlab.com/primer Phone number CEO: Phone number other participant(s): Accessing the GitLab office building Enter the building through the double doors between the two Mike's Bikes locations. On the intercom press the call button then press '206' (for GitLab) to have us buzz you in. Proceed to the elevator at the rear of the foyer and go to the 2nd floor (strangely the elevator will show 3 when you stop at 2). Exit the elevator and proceed to the right. The unit is the last door on the right at the end of the hall (2F). More details are on our visiting page: https://about.gitlab.com/visiting/
For internal meetings such as 1:1 calls with the team, add "If you need to cancel/reschedule please ping the EA on Slack"
For all external meetings include visiting info (for in-person meetings) and our primer page. Make sure to add both a Zoom link and physical phone numbers.
For meetings or lunch/dinner appointments, always make sure to add the address in the invite of the location where it’s scheduled and make sure to plan travel time (in a separate calendar item, just for Sid) before and after the meeting in case another meeting or call should follow.
If Sid has a ride or walks to an appointment, make sure to add 5 minutes extra to find the address and sign in at reception.
If Sid is driving himself, make sure to add 15 minutes for random occurances such as travic, stopping for gas or parking.
If Sid is driving to a meeting, he likes to plan phonecalls to catch up with the team. Check with him who he'd like to talk with during his commute and schedule accordingly.
Sales meetings are important, in case the CEO can help the process, feel free to include him in the meeting
Make sure to include background info what the call will be about to the invite. For example adding the relevant email thread in the notes of the invite
Due to a busy schedule the CEO has a preference of meeting setup: First try for a video call or a meeting at the GitLab office. If the other party presses to meet at their location, confirm if that is OK before accepting.
There are 2 types of calls with the CEO. First an introductory call which needs the GitLab primer and second a final interview which needs the form mentioned below.
PeopleOps makes sure that every candidate that the CEO talks with has a profile in our ATS with background info e.g. a resume or LinkedIn profile link
Managers will tag EA to schedule a call for the applicant with Sid
Template email with wording to schedule “Kirsten schedule Sid”
Add date/time and make sure to include timezones
For calls with candidates for a role of Director level or higher, make sure to plan 90 minutes for a call
Add responses of the form you sent out with the invite to our ATS; Workable
EA does research for the best option for a flight and propose this to the CEO before booking. Make sure to add a calendar item for 2 hours before take off for check in and add a separate one for travel time before that in the CEO's calendar If a flight was changed or not taken due to delays or other circumstances, make sure to check with the airline for the persons flight status Current preferences for flights are:
Check a bag for all trips longer than one night
Frequent Flyer details of all (previously flown) airlines are in EA vault of 1Password as well as important passport/visa info
Check all incoming (physical) mail at 1233 Howard st and sort the urgent and important letters.
Inform AP if invoices came in
Inform other people/departments if mail is addressed for them and include a scan of the document
When you’re logged in, you can find wingman account access for other team members in the top right corner menu.
Check their email (if you have access), using the search bar in the top, to find any receipts for the postings in the current expense report.
And/or write down what receipts are missing and email to request them if needed
I love to talk to users or potential users of GitLab anytime.
Traveling is not efficient because it can take 2 to 10 times the time of the meeting itself.
Some general guidelines of what travel is appropriate, these guidelines are not fixed, feel free to ask for exceptions:
Check my availability with the EA, reschedule with the EA, cancel with the EA, not me.
I'll take any meeting via video conference or at our office.
I'll take a meeting in the Bay Area as long as it is not an SMB organization.
I'll take a meeting outside the Bay Area but in the US with large or strategic organizations
I'll take a meeting outside the US with strategic organizations.
Consider the following to increase efficiency:
Combine meetings with multiple organizations in the same location.
Get meetings with multiple stakeholders in the same company.
Apart from the formal meetings try to organize a meal with stakeholders.
Record the meeting so you can distribute it to others in the organization.
Please check with the EA to look at my calendar to leverage my existing travel plans.
Make sure to let the EA know what you expect from me. E.g. arrive an hour before, do a pitch etc.
Please plan audio only meetings only when the customer explicitly declines a video call.
Any meeting that requires travel should be properly prepared and any lessons relayed to the marketing team.
If you are a GitLab team member you can use our house in Utrecht, the Netherlands for free with up to 5 guests. You can find more information on AirBnB. When it is not reserved on the AirBnB calendar you can reserve it, message Karen Sijbrandij in the #valley chat channel to do so. Our host Justus will check you in and out and will take care of the cleaning. Enjoy your stay!