Added 1:1 documentation to Rituals sections (#5094)

* Added 1:1 documentation to  Rituals sections

Added 1:1 documentation to  Rituals sections

* Team name edit

Changed Operations team to Digital Experience team.

* Update to wording of new ritual

Committing Eric's edit suggestions.

Co-authored-by: Eric <eashaw@sailsjs.com>

* Update people.md

Added new step for updating the All Hands link

Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
This commit is contained in:
Charlie Chance 2022-04-19 21:52:09 -06:00 committed by GitHub
parent c641161238
commit 4354a13a91
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -325,6 +325,17 @@ At the end of the quarter, and at key points throughout the quarter (every 3 wee
- OKRs they are finalized 1 week from when topdown OKRs were initially reviewed.
- Finalized OKRs are shared company-wide and at "all hands" and, at least to some degree, become public.
### 1:1 Mike:Sid Document Preparation
Every two weeks our CEO Mike has a 1:1 meeting with our Investor Sid and there are four parts our Digital Experience Team completes while constructing this document.
- After the 1:1 meeting has happened, Charlie makes a copy of the original document, labels it "yyyy-mm-dd Backup copy of Mike from Fleet & Sid," and moves it to a private folder.
- Charlie will change the permissions on the new copy to share it with Mike and Zach and set Mike to be the file's owner. If there are any agenda items labeled "TODO", Charlie will make a comment in the backup copy to assign them to Mike.
- Charlie prepares the original document by deleting the agenda items in the "Hallway" and "Feedback" sections, leaving only the "Vision" section.
- Charlie will update the monthly "All Hands" link and grant Sid viewing access.
- Charlie will send Mike links to the new document and the backup copy in a direct message in Slack.
- The day before the meeting, Nathan will prepare the "Vision" section of the original document. Nathan will collect and update information related to annual recurring revenue, new members in the `#fleet` channel in the osquery Slack, the number of new customers and opportunities from Salesforce, the total number of devices using Fleet, the company's current headcount, and banking information.
## Workiversaries
We're happy you've ventured a trip around the sun with Fleet. Let's celebrate!