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

Remove duplication (#11415)

Browse source
This commit is contained in:
Mike McNeil 2023-04-28 08:53:32 -07:00 committed by GitHub
parent 5ddfacaf45
commit 48c6f9bf53
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
handbook/business-operations/README.md
View file

@ -691,8 +691,8 @@ Then, send **the CEO** and **each manager** a direct message in Slack by copying
### Communicating departures
Although it's sad to see someone go, Fleet understands that not everything is meant to be forever [like open-source is](https://fleetdm.com/handbook/company/why-this-way#why-open-source). There are a few steps that the company needs to take to facilitate a departure.
1. **Departing team member's manager**: Create [offboarding issue](https://github.com/fleetdm/confidential/issues/new/choose) and update last day in ["Fleeties"](https://fleetdm.com/handbook/company#org-chart).
2. **Head of Business Operations**: After finding out at the next standup (or sooner), the Head of Business Operations will post in `#g-e` to inform the E-group of the team member's departure. E-group members will inform any other managers on their teams.
1. **Departing team member's manager**: Create and begin completing [offboarding issue](https://github.com/fleetdm/confidential/issues/new/choose).
2. **Head of Business Operations**: After finding out at the next standup (or sooner), the Head of Business Operations will post in `#g-e` to inform the E-group of the team member's departure and ask E-group members will inform any other managers on their teams.
3. **CEO**: The CEO will make an announcement during the "🌈 Weekly Update" post on Friday in the `#general` channel on Slack.