diff --git a/handbook/company/ceo.md b/handbook/company/ceo.md index 7c14636b91..e27b8c6dfd 100644 --- a/handbook/company/ceo.md +++ b/handbook/company/ceo.md @@ -86,7 +86,7 @@ Last-minute changes or cancellations must be communicated to Mike via [direct me (How to...) -### Process the CEO's email +### Process the CEO's inbox The Apprentice to the CEO is [responsible](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) for processing all email traffic prior to CEO review. The [AttC](#team) will reduce the scope of Mike's inbox to only include necessary and actionable communication. - Marking spam emails as read (same for emails Mike doesn't actually need to read). @@ -271,6 +271,22 @@ Marking as _"private"_ in Gong doesn't limit access, instead, use this process: - If appropriate, make this doc "¶¶," plus fleeties who were on the call. - Include in the doc "link to video:" - Include in the doc "link to transcript:" + + + +## Rituals +(Who will...) + + + +## Slack channels + +| Channel | Purpose | Standard Operating P | DRI | +| ------- | ------- | ---------------------------- | --- | +| [g-ceo](https://fleetdm.slack.com/archives/C05K87USYUV) | Open line of communication for Fleeties to make requests of the 🦿 [CEO support team](https://fleetdm.com/handbook/company/ceo#team) | Reach out to the AttC with requests or to add an item on the 🐈‍⬛🗣️ [CEO office minutes](https://docs.google.com/document/d/12cd0N8KvHkfJxYlo7ggdisrvqw4MCErDoIzLjmBIdj4/edit) | [@sampfluger]([https://github.com/sampfluger88](https://fleetdm.slack.com/archives/D05DW7BT2GY)) | +| [help-being-ceo](https://fleetdm.slack.com/archives/C03U703J0G5) | Private [hallway](https://about.gitlab.com/handbook/leadership/1-1/suggested-agenda-format/#hallway) for the CEO to drop tasks and personal scheduling information | - Mark items with 👀 (emoji reaction) to indicate that you are working on the task. - Mark requests with ✅ (emoji reaction) to indicate that you completed or filed away the task | [@sampfluger]([https://github.com/sampfluger88](https://fleetdm.slack.com/archives/D05DW7BT2GY)) | + + ### Why not mention the CEO in Slack threads? Everyone else who works at Fleet is expected to read and reply (or acknowledge with an emoji reaction) every time they're mentioned in Slack, even deep inside long threads. @@ -279,29 +295,41 @@ Everyone else who works at Fleet is expected to read and reply (or acknowledge w From Mike: -
Staying on top of your Slack mentions (including in threads!) is very important. Please use them. +
+ + Staying on top of your Slack mentions (including in threads!) is very important. Please use them. But now that the company has grown, in my role as CEO, I get mentioned in Slack very often. + I held on as long as I could. But due to volume, in late 2022, I made the decision to no longer read Slack threads where I am mentioned. + What do I still read? + - If you mention me in a top-level channel message, I'll see and read it in 1 business day. - If you send me a direct message, I'll see and read that ASAP. + Keep in mind I am often in meetings all day, and may not be able to reply promptly. -Thank you so much!" 🙇
+ +When in doubt, you can look at my calendar and join whatever meeting I'm in. If none of that works, and there is an emergency where you need my immediate attention, get help from Zach Wasserman. +Thank you so much!" 🙇 + +
+## Intake +To make a request of the business operations department, [create an issue using one of our issue templates](https://github.com/fleetdm/confidential/issues/new/choose). If you don't see what you need, or you are unsure, [create a custom request issue](https://github.com/fleetdm/confidential/issues/new/choose) and someone in business operations will reply within 1 business day. + + ## Kanban Any Fleet team member can view the [🐈‍⬛#g-ceo kanban board](https://app.zenhub.com/workspaces/-g-ceo-645b0eab68a4d40c0795ff61/board) (confidential) for this department, including pending tasks in the active sprint and any new or pending requests. -## Intake -To make a request of the business operations department, [create an issue using one of our issue templates](https://github.com/fleetdm/confidential/issues/new/choose). If you don't see what you need, or you are unsure, [create a custom request issue](https://github.com/fleetdm/confidential/issues/new/choose) and someone in business operations will reply within 1 business day. - ## Rituals (Who will...) + ## Slack channels | Channel | Purpose | Standard Operating Procedure | DRI | diff --git a/handbook/company/communications.md b/handbook/company/communications.md index bcfec5f141..5f63d83124 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -3,6 +3,36 @@ Fleet's [open-core](https://www.heavybit.com/library/video/commercial-open-source-business-strategies) style of communication and the [tools we use](https://docs.google.com/spreadsheets/d/170qjzvyGjmbFhwS4Mucotxnw_JvyAjYv4qpwBrS6Gl8/edit?usp=sharing) are part of the company's DNA and essential to moving Fleet into the future. +## Vision for dept handbook pages + +The idea here is to get this vision implemented on a single departmental handbook page first, starting with handbook/company/ceo. It's hard to know what the philosophy should be until we can see it. So we need to shorten the feedback loop so we can see it change live in one place. That way we can iterate in one place instead of having things go a bunch of different directions, and adding in all the complexity of extra redirects to keep track of and all that stuff. Then once we've got that looking good and have iterated a bit, we'll spread it out. + +Another thing is that we need to get a better intuitive understanding of who these pages are designed to serve. So in order to put ourselves in their shoes (get behind their eyeballs), we need something to look at. So doing a particular page first provides us with that canvas. + +- (h1) Top-level page title/ file name + + - (h2) Short section on _departmentally specific philosophy_ and the purpose of the page: If philosophy applies to more than your department, **pull it out**, make it easier for contributors to find. + - **Nice to have:** Tiny little link/sentence/button with call-to-action that links you to intake or intake options) + +- (h2) How can I… (outward facing first: e.g.non-Fleetie contributor) + + - e.g. (h3) CEO flaws + - e.g. (h3) Scheduling with the CEO + - e.g. (h3) Summoning the CEO (travel) + +- (h2) How-tos (Inward facing e.g. Fleetie) + - e.g. (h2) Process CEO email + +- (h2) Intake + +- (h2) Kanban + +- (h2) Rituals + +- (h2) Slack channels + + + ## Meetings Plan to join meetings on time. At Fleet, we start on time and do not wait for folks to join. @@ -24,7 +54,7 @@ In an all-remote company, “face time” matters. - Is there another way to distribute this info or align on a course of action that _doesn't_ take valuable time away from customers, projects, or personal time? Could you create a [Google Doc](https://docs.google.com/document/d/1TaZ654gTwadWGDYhP3zuAzWe0eiY0s9NhaU9KLCokgw/edit) and share it with would-be attendees? If the info can be documented it should be. Could the info be sent in Slack or by email? 2. Do I have all the information needed to schedule this meeting? - + -TODO ### Internal meeting scheduling