EBA Handbook Updates Round 1
Why is this change being made?
Round 1 of EBA Handbook Overhaul - the EBA page is largely outdated and needs to reflect our current standing team
Updated Item | Reason |
---|---|
1. Cleaned Alignment of entire page | self explanatory |
2. Updated the Contact section to include the E-Group EBA Slack Group |
item was missing and is needed so all who need to contact the team know how to do so |
3. Simplified and updated the meeting request requirements | prior list was not as clear |
4. Updated the GitLab agenda link in 2 locations | doc has been updated recently and links were outdated |
5. Cleaned the title of Customer, Prospect, or Partner Meetings with an E-Group Member so they are 3 distinct items |
just makes messaging crisper |
6. Changed the response time limit of 24hours to CES -> minimal delay ensuring a seamless candidate experience | we are all aware of the urgency and this wording speaks to the why |
7. Removed the instructions around EBAs providing availability to CES vs going in and booking their own meetings | no longer relevant |
8. Included a line around EBAs scheduling confidential interviews directly | this has been a recent occurrence and should be included |
9. Merged and edited the 2 categories under EBA Team Best Practices to now live under one category called EBA Team Tips & Best Practices
|
many of the items on this list were a matter of preference vs best practice and only work for some, but certainly not for most. Any item that can be helpful to others or includes a useful link remains on the list |
10. Reorganized Travel & Navan sections to a Travel & Expense section which includes info about Navan, and removed outdated information |
this is an important section that needs to align with the policy |
11. Removed the virtual team building, events, and gifting sections | this is very random, outdated, and goes largely unused. Although we sometimes plan events, it doesn't make sense to include on the EBA page. I will work with the EBA team to come up with another place that makes sense for this |
12. Removed any mention of "Mission Control" | no longer exists |
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.