Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 143

Update ceo-handbook.md (#9705)

Browse source
This commit is contained in:
Charlie Chance 2023-02-06 13:28:23 -07:00 committed by GitHub
parent 21428cb6a6
commit 7e68e6b167
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
handbook/business-operations/ceo-handbook.md
View file

@ -178,10 +178,10 @@ How to file videos from Gong recordings (**marking as "private" in gong is not a
- Include in the doc "link to transcript:"
# Participation in the CEO shadow program
## Participation in the CEO shadow program
This section explains more about the CEO shadow program.
## In this section
### In this section
- [Eligibility](#eligibility)
- [How to apply](#how-to-apply)
- [Parental participation](#parental-participation)
@ -197,34 +197,34 @@ This section explains more about the CEO shadow program.
- [Considerations for other companies starting CEO shadow programs](#considerations-for-other-companies-starting-ceo-shadow-programs)
- [Alumni](#alumni)
### Eligibility
#### Eligibility
All Fleet team members are eligibile to apply for the CEO Shadow Program. Eligibility starts after you've been at Fleet for at least 6 months.
### How to apply
#### How to apply
1. Create a pull request to add yourself to the [rotation schedule](https://github.com/fleetdm/fleet/edit/main/handbook/people/ceo-handbook.md#rotation-schedule).
2. Assign your manager and ask them to approve (but not merge) the pull request.
3. Once your manager approves the pull request, assign the pull request to `CharlotteChance`, link to the pull request in the #help-ceo-shadow channel, and tag `@Charlie`.
### Parental participation
#### Parental participation
To allow flexibility for parents to participate, there will be some rotations identified as "parent-friendly" weeks. These are weeks when Mike doesn't need a shadow for the full 5 workdays or where the program is split so the weeks are not consecutive.
### Rotation rhythm
#### Rotation rhythm
1. See one, you are trained by the outgoing person.
2. Teach one, you train the incoming person.
The shadow should be available for the full two weeks.
## Preparing for the program
### Important things to note
### Preparing for the program
#### Important things to note
1. This is not a performance evaluation.
2. Plan to observe and ask questions.
3. Don't plan to do any of your usual work.
4. Be ready to add a number of [handbook](https://fleetdm.com/handbook) updates during your shadow period.
5. Participating in the shadow program is a privilege that will expose you to confidential information.
### What to wear
#### What to wear
Casual. You do not need to dress formally; business casual clothes are also appropriate.
### Pre-program tasks
#### Pre-program tasks
1. Create an [onboarding issue](https://github.com/fleetdm/confidential/blob/main/ceo-shadow-onboarding.md). Outgoing shadows are responsible for training incoming shadows. We currently track onboarding and offboarding in the [ceo-shadow project](https://github.com/orgs/fleetdm/projects/49/views/1).
2. Consider creating goals. For inspiration, here is [an example](https://gitlab.com/nmccorrison/ceo-shadow/-/issues/1#my-goals) of a CEO Shadow who added goals to their onboarding issue.
3. Practice your introduction. See [CEO Shadow Introductions](https://about.gitlab.com/handbook/ceo/shadow/#ceo-shadow-introductions) for specifics.
@ -242,7 +242,7 @@ To allow flexibility for parents to participate, there will be some rotations id
```This list is not meant to be exhaustive and should not become a glossary. While we strive to be handbook first, you may find that we are using acronyms without a clear handbook definition. If you can't find it in the handbook or find a standard definition on Google, ask someone what the acronym means. Not being able to find it could be a sign that we need to do a better job with documentation.```
### What to expect during the program
#### What to expect during the program
The value of the CEO Shadow Program comes from the broader context you'll gain and the interesting conversations you'll witness.
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 a shadow.
@ -259,18 +259,18 @@ Here are some examples for meetings:
2. Share thanks in the #thanks channel in Slack when it comes from a customer or wider community member in a meeting.
## Preparing for meetings and events
### CEO's calendar
### Preparing for meetings and events
#### CEO's calendar
1. Review the [CEO's calendar](https://calendar.google.com/calendar/u/0/r/week).
2. 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".
3. 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.
4. Some meetings you will not be required to shadow, those are indicated with "[no shadows]" in the event title.
5. Meetings with those outside of Fleet 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.
### Zoom information
#### Zoom information
You'll have an opportunity to join many calls and meet new people along the way. Fleet asks that you change your Zoom name to reflect "[CEO shadow - your name]" so that everyone on the call knows who you are and why you are participating.
### Responsibilities
#### Responsibilities
Meetings come in many different formats. Your responsibilities may change slightly based on the kind of meeting.
Here are the responsibilities shadows have during meetings:
| Meeting type | Notes? | Timekeeping? |
@ -280,15 +280,15 @@ Here are the responsibilities shadows have during meetings:
| Customer Meeting | Yes, please use the externally-shared collaboration doc | Timekeeping |
| Anything else (unless specified) | Yes, take notes | Timekeeping |
## After the CEO shadow program
### Alumni
### After the CEO shadow program
#### Alumni
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 |
| ---------- | -------- | ---- | ----- | --------- |
| date | date | name | title | takeaways |
## Considerations for other companies starting CEO shadow programs
### Considerations for other companies starting CEO shadow programs
GitLab co-founder and CEO Sid Sijbrandij [answered questions in a YouTube livestream](https://youtu.be/ExG8_bnIAMI) from Sam Altman, as the two discussed considerations for implementing a CEO Shadow program in other organizations. Key takeaways are documented below.
1. CEOs should not optimize meetings for Shadows. They learn by being in the room, either in-person or virtual, and it's OK if the Shadow doesn't fully understand everything.
2. A well-designed CEO Shadow program shouldn't burden a CEO; in fact, Shadows should actively make a CEO's day easier by assisting with notes and changing relevant portions of the company handbook upon request.