diff --git a/handbook/people/README.md b/handbook/people/README.md index 2b6f443659..6219d31514 100644 --- a/handbook/people/README.md +++ b/handbook/people/README.md @@ -415,7 +415,7 @@ During their onboarding at Fleet, new team members are asked to schedule a sight - The walkie talkies (DMs). - The watering hole (#oooh-, #random, #news, #help-). -## Onboarding a new advisor +### Onboarding a new advisor Advisor agreements are sent through [DocuSign](https://www.docusign.com/), using the "Advisor Agreement" template. To send a new advisor agreement, you'll need the new advisor's name and the number of shares they @@ -427,7 +427,7 @@ Once you send the agreement, add a new row to the [advisory board spreadsheet](h When you complete the agreement, make sure it is in the correct Google Drive folder, update the [advisory board spreadsheet](https://docs.google.com/spreadsheets/d/15knBE2-PrQ1Ad-QcIk0mxCN-xFsATKK9hcifqrm0qFQ/edit#gid=1803674483) to show that the agreement has been signed, and ask the new advisor to add us on [Linkedin](https://www.linkedin.com/company/71111416), [Crunchbase](https://www.crunchbase.com/organization/fleet-device-management), and [Angellist](https://angel.co/company/fleetdm). -## Onboarding a new consultant +### Onboarding a new consultant Consultant agreements are sent through [DocuSign](https://www.docusign.com/), using the "Consulting Agreement" template. To send a new consulting agreement, you'll need the new consultant's name, the term of the service, a summary of the services provided, and the consultant's fee. There are some defaults that we use for these agreements: @@ -439,7 +439,7 @@ There are some defaults that we use for these agreements: Then hit send! After all of the signatures are there, the completed document will automatically be uploaded to the appropriate Google Drive folder, and a Slack message will appear in the `#g-people` channel. -## Updating a consultant's fee +### Updating a consultant's fee - Direct message Charlie with rate change information. - Charlie will post the information to `#g-people` and tag the CEO for approval. @@ -467,7 +467,7 @@ The steps for doing this are highlighted in this loom, TODO. 5. Sync hours 6. Run contractor payroll -## Zapier and DocuSign +### Zapier and DocuSign We use Zapier to automate how completed DocuSign envelopes are formatted and stored. This process ensures we store signed documents in the correct folder and that filenames are formatted consistently. @@ -490,7 +490,7 @@ When the final signature is added to an envelope in DocuSign, it is marked as co [email subject] link: drive.google.com/[destinationFolderID] ``` -## Adding Salesforce licenses +### Adding Salesforce licenses We consider Salesforce to be our Rolodex for customer information. During the onboarding process, you may need to add a license for the new hire. Here are the steps we take: @@ -500,6 +500,14 @@ We consider Salesforce to be our Rolodex for customer information. During the on 4. Sign DocuSign sent to the email. 5. The order will be processed in ~30m. +## Communicating departures + +Although it's sad to see you go, Fleet understands that not everything is meant to be forever like open-source is. There are a few steps that we'll need to take to communicate to the team of your departure. + +1. Direct team: The CEO will reach out to the departing teammember's direct reports in 1:1 calls. +2. Key stakeholders: The CEO will reach out to his direct reports about the departing teammember's departure. +3. Announcement: Charlie will make an announcement during the "🌈 Weekly Update" post on Friday in the `#general` channel on Slack. + ## PeopleOps ### CEO handbook