CEO shadow outside timezone options
In the past, we discussed various possible options for team members wanting to participate in CEO shadow, when their timezone location is a blocker. gitlab-com/www-gitlab-com!103046. This captures some of the options that we have considered. It is also a place to suggest alternative options.
Option 1: Travel to San Francisco for rotation
Shadows would travel to San Francisco/Bay Area for the 2 week rotation. The shadowing would still be remote. Shadows would work out of a co-working space while shadowing.
Pros
- This would allow the Teach 1 and See 1 to have overlap for 1 week in a PT friendly timezone in person.
- No timezone issues.
- Can attend in-person meetings
Cons
- Requires travel for shadows
- Not the most cost effective
Expenses GitLab could pay for:
- Travel
- Accommodations
- Co-working space
- Meals during travel and 2-week rotation
Option 2: Travel to AMER within 2 hours of PT
Shadows choose a location in Pacific, Mountain, or Central time zone.
Pros
- Shadows can visit family and friends
- Generally cost effective
- No timezone issues
Cons
- Requires travel
Expenses GitLab could pay for:
- Travel within a budgeted amount (to be determined, comparable to travel of option 1?)
- Meals during travel and 2-week rotation
Option 3: Allow 1 of 2 shadows to do short-days (6 hour minimum?)
Note: This is an available option after merging gitlab-com/content-sites/handbook!1701 (merged) .
Shadows do a rotation with shorter days with a minimum of X hours per day. 1 short-day shadow would be allowed at a time (must be paired with full-day shadow on both weeks).
Pros
- No travel required
- Cost effective
Cons
- Will miss some meetings
- Burden on the other full-day shadow for unavailable hours
- Incoming shadow would not have anyone their first half day if the outgoing shadow is in APAC
Expenses GitLab could pay for:
- Childcare, if applicable.
Option 4: Shift working hours in current timezone
Note: This is an option that is available to team members.
Shadows do a full rotation from their current timezone.
Pros
- No travel required
- Cost effective
Cons
- Irregular hours for shadow
Expenses GitLab could pay for:
- Childcare, if applicable.
Current status
This issue has been opened for transparency, and to allow team members to suggest further options if there's something we haven't considered.
However, especially with travel options, it requires budgeting, approvals, and time to work out details. Current target for reviewing and implementing these options is FY25H2 (2nd half of FY25).