fleet/handbook/ceo.md
Sampfluger88 a8cec5987b
CEO requests to be added to a call (#13589)
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
2023-08-29 22:22:57 -05:00

21 KiB
Raw Blame History

CEO

This page details processes specific to working with Mike McNeil, co-founder and Chief Executive Officer of Fleet, and the 🦿 CEO support team.

What we do

The CEO is the directly responsible individual for pricing, final review of UI or behavioral changes to fleetdm.com and the core product, signatures, changes to parts of the handbook, product marketing (brandfronts, pitchfronts, featurefronts, ICPs, personas, and targeting) and various other aspects of the company.

  • Note When the CEO is out of office, these responsibilities are either paused, delegated, or coordinated through the Apprentice to the CEO so they can be handled promptly. (It depends on the responsibility and the situation.) The process for the CEO going out of office is a work in progress.

Team

Role Contributor(s)
CEO Mike McNeil (@mikermcneil)
Apprentice to the CEO Sam Pfluger (@sampfluger88)

Contact us

  • If you mention the CEO or reply from within a Slack thread, he will not read your message.
    • If urgent or personal, send a Slack direct message (DM) to @mikermcneil right away.
    • If it can wait, add your message to the "🐈‍⬛🗣️ CEO office minutes (#g-ceo)" agenda and @mention the Apprentice in the #g-ceo Slack channel
    • Any Fleet team member can view the 🐈‍⬛#g-ceo kanban board (confidential) for this team, including pending tasks and requests.
  • If the CEO asks you to set up a meeting or add him to a call, please get scheduling help from the Apprentice. (Or if it's too late, let the Apprentice know what you've done so far in the #g-ceo Slack channel.)

Schedule time with the CEO

All meetings are welcomed and a top priority for the CEO to consider getting on the calendar quickly.

To grab time with the CEO @mention the Apprentice in the #g-ceo channel with:

  • Proposed date and time
  • Reason for meeting (e.g. include customer names or a related GitHub issue)

Meetings and blocked time can sometimes be moved to make room. External meetings, travel, and personal commitments can rarely be moved.

  • Why the extra step? There are not enough hours in the day for the CEO to accept every request to meet, so we have to prioritize.
  • Self-service scheduling: Unlike other team members, who you can schedule with by simply dropping an event on their calendar, unless requested directly from Mike, please do not directly schedule a meeting onto the CEO's calendar without using this process to confirm with the Apprentice first.
  • Rescheduling: All items on Mike's calendar are subject to change by the CEO to better serve the company. Send last-minute changes or cancellations to Mike via direct message (DM).

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.

Now that the company has grown, the CEO gets mentioned in threads too often to keep up with thread replies, even for threads he participates in.

From Mike:

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.

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!" 🙇

CEO flaws

Openness is one of Fleet's values and I want to live that by sharing the flaws I know I have. Im fully responsible for improving the things below, listing them is no excuse. They are listed here for two reasons. The first one is so that people know it is not them but my fault. The second one is so I can improve, I hope that listing them lets people know I appreciate when people speak up about them.

  • I often need to talk to think.
  • I can speak quickly. It is ok to say “Whoa, hold on a second. Let me take some notes.”
  • I can be quick to criticize, especially if something looks almost done. It is ok to ask “What do you see?” If helpful, you can add “What are three bright spots?”
  • I can hurry to decisions when I think something is time sensitive or nearly ready to ship. It is ok to say “Im looking for early feedback.” It is ok to say “Im not yet 70% sure Im 100% done with this."

Automated filing of signed documents

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. When the final signature is added to an envelope in DocuSign, it is marked as completed and sent to Zapier, where it goes through these steps:

  1. Zapier sends the following information about the DocuSign envelope to our Hydroplane webhook:
    • emailSubject - The subject of the envelope sent by DocuSign. Our DocuSign templates are configured to format the email subject as [type of document] for [signer's name].
    • emailCsv - A comma-separated list of signers' email addresses.
  2. The Hydroplane webhook matches the document type to the correct Google Drive folder, orders the list of signers, creates a timestamp, and sends that data back to Zapier as
    • destinationFolderID - The slug for the Google Drive folder where we store this type of document.
    • emailCsv - A sorted list of signers' email addresses.
    • date - The date the document was completed in DocuSign, formatted YYYY-MM-DD.
  3. Zapier uses this information to upload the file to the matched Google Drive folder, with the filename formatted as [date] - [emailSubject] - [emailCvs].PDF.
  4. Once the file is uploaded, Zapier uses the Slack integration to post in the #help-classified channel with the message:
    Now complete with all signatures:
       [email subject]
       link: drive.google.com/[destinationFolderID]
    

Responsibilities

Schedule CEO interview

From time to time, you will need to schedule an interview between a candidate and the CEO:

  1. Make a copy of the "¶¶ CEO interview template" (private Google doc)
  2. Change file name and heading of doc to ¶¶ CANDIDATE_NAME (CANDIDATE_TITLE) <> Mike McNeil, CEO final interview (YYYY-MM-DD)
    • Add candidate's personal email in the "👥" (attendees) section at the top of the doc.
    • Add candidate's LinkedIn url on the first bullet for Mike.
  3. Set the Google Calendar description of the calendar event to: Agenda: URL_FOR_NEW_COPY_OF_FINAL_INTERVIEW_DOC

Process the CEO's calendar

Time management for the CEO is essential. The Apprentice processes the CEO's calendar by checking for and correcting any double-booking (e.g. two meetings scheduled for overlapping times that the CEO needs to attend) or new meetings added.

Prioritizing in order of importance:

  • Travel and personal commitments
  • External meetings
  • Board meetings
  • Priority design reviews
  • E-group
  • Reserved until day of
  • Customer or prospect calls (up to the first 4 hours per week)
  • Design reviews
  • Puppet show

Please do not move external meetings, travel, and personal commitments without asking the CEO first.

Meeting agenda prep is especially important to help the CEO focus and transition quickly in and between meetings.

In the notes document include:

  1. LinkedIn profile link of all outside participants
  2. Screen-shot of LinkedIn profile pic
  3. Company name (in doc title and file name)
  4. Correct date (20XX-XX-XX in doc title and file name)
  5. Context that helps the CEO to understand the purpose of the meeting at a glance from:
    • CEO's email
    • LinkedIn messages (careful not to mark things as read!)
    • Google Drive Be sure to do this from Mike's browser so as to not lock him out of any meeting docs.

Process the CEO's inbox

  • The Apprentice to the CEO is responsible for processing all email traffic prior to CEO review. The Apprentice 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).
  • Escalate actionable sales communication and update Mike directly.
  • Ensure all calendar invites have the necessary documents included.

Send the weekly update

We like to be open about milestones and announcements.

  • Every Friday, e-group members report their KPIs for the week

  • Friday nights, the Apprentice will post a short update in #general including:

    • A link to view KPIs
    • Who was on-call that week
    • Fleeties who are currently onboarding
    • Planned hires who haven't started yet
    • Fleeties who had their lady day that week
  • Change the "" to "🔭" in the beginning of the formula

image
  • Select this week's cell (first week with the 🔮) in the KPI spreadsheet and copy the entire formula

  • Paste without formating (CMD+⇧+V) back into the same cell

  • The formula will now look like this:

image
  • Paste the newly formatted message in the #general Slack channel

  • 📬 Send it!

Schedule travel for the CEO

The Apprentice schedules all travel arrangements for the CEO including flights, hotel, and reservations if needed. CEO traveling preferences in descending order of importance are:

  • Direct flight whenever possible (as long as the cost of the direct flight is ≤2x the cost of a reasonable non-direct flight)
  • Select a non-middle seat, whenever possible
  • Don't upgrade seats (unless there's a cheap upgrade that gets a non-middle seat, or if a flight is longer than 5 hours. Even then, never buy a seat upgrade that costs >$100.)
  • The CEO does not like to be called "Michael". Unfortunately, this is necessary when booking flights. (He has missed flights before by not doing this.)
  • Default to carry-on only, no checked bags. (For trips longer than 5 nights, add 1 checked bag.)
  • Use the Brex card.
  • Frequent flyer details of all (previously flown) airlines are in 1Password as well as important travel documents.

Prepare for the All hands

Every month the Apprentice will do the prep work for the monthly "✌️ All hands 🖐👋🤲👏🙌🤘" call.

  1. In the "👋 All hands" folder, create a new folder using "yyyy-mm - All Hands - yyyy month name".
  2. Download a copy of the previous month's keynote file and rename the copy with the same name used to create the new folder.
  3. Update "🧑‍🚀 Welcome!" slide to reflect new hires since last month's All Hands meeting (pull this from the 🧑‍🚀 Fleeties spreadsheet using "name (pronoun), position".
  4. If applicable Update "🦉 Welcome!" slide to reflect new investors or advisors using "name (pronoun), position, company".
  5. If applicable Update "🤝 Welcome!" slide to reflect new customers.
  6. Update slides that contain dates to reflect current All Hands date.
  7. Update slides that contain metrics to reflect current information using the 🌈 Weekly updates doc.
  8. If applicable Update Quarterly OKRs to reflect current OKR goals for the quarter.
  9. Test that the transition on the last slides continue to work.
  10. If applicable Add new customer's logo to final slide.
  11. If applicable Add a "Star slide" for guest speakers.

The day before the All hands, Mike will prepare slides that reflect the CEO vision and focus.

After the All hands

TODO: rename to imperative mood (see rituals.yml)

The Apprentice will post a link to the All hands Gong recording and slide deck in Slack.

Template to use:

Thanks to everyone who contributed to today's "All hands" call.

:tv: If you weren't able to attend, please *[watch the recording](Current-link-to-Gong-recording)* _(1.5x playback supported)_.

You can also grab a copy of the [original slides](https://fleetdm.com/handbook/business-operations#all-hands) for use in your own confidential presentations.
  • Copy and paste the template to the "# general" Slack channel.

  • To create the recording link:

  • Open Gong recording and Share call

  • Share with customers

  • Copy link and paste the url *[Watch the recording](here-in-your-template-message)*.

  • The PDF can be found in the current months 👋All hands folder in Google Drive.

  • Download the PDF and upload (double click the +) into your updated Slack message, which will look like this:👇

image

📬 Send it!

Connect with recently active community members

Read the three 3 most recent questions asked in osquery and MacAdmins Slack. Find each contributor on LinkedIn. Send connect request (blank).

Goal: No one else is currently LinkedIn connecting with community Slack participants. This puts a face to the project and welcomes them to Fleet.

💻 Sid : Mike

TODO: rename to imperative mood (see rituals.yml)

Every two weeks, our CEO Mike has a 1:1 meeting with Sid Sijbrandij. The CEO uses dedicated (blocked, recurring) time to prepare for this meeting earlier in the week.

After each meeting, the Apprentice makes a copy of the original document and moves it into a particular folder in the "Fleet" shared drive, with a particular naming convention:

image

Post-e-group archival

TODO: rename to imperative mood (see rituals.yml)

  • Immediately after every e-group the Apprentice duplicates the e-group agenda doc as a backup copy saved to "Classified" shared drive. Rename it to "YYYY-MM-DD backup of e-group agenda". Then clear out all agenda items from the e-group doc (the ones that people add, not the standard fixtures), and replace them with a single item: Sam: FYI: Agenda from last time (YYYY-MM-DD): LINK

Unroll a Slack thread

From time to time the CEO will ask the Apprentice to the CEO to unroll a Slack thread into a well-named whiteboard google doc for safekeeping and future searching.

  1. Start with a new doc.
  2. Name the file with "yyyy-mm-dd - topic" (something empathetic and easy to find).
  3. Use CMD+SHFT+V to paste the Slack convo into the doc.
  4. Reapply formatting manually (be mindful of quotes, links, and images).
    • To copy images right-click+copy and then paste in the doc (some resizing may be necessary to fit the page).

Delete an accidental meeting recording

It's not enough to just "delete" a recording of a meeting in Gong. Instead, use these steps:

  • Wait for at least 30 minutes after the meeting has ended to ensure the recording and transcript exist and can be deleted.
  • Sign in to Gong through the CEO's browser.
  • Click Conversations
  • Select the call recording no longer needed
  • Click the "hotdog" menu in the right-hand corner image
  • Delete recording
  • Search for the title of the meeting Google Drive and delete the auto-generated Google Doc containing the transcript.
  • Always check back to ensure the recording and transcript were both deleted.

Process the #help-being-ceo channel

The #help-being-ceo Slack channel is a private hallway for the CEO to drop tasks and personal scheduling information.

When processing new requests from this channel, consider this:

  • Be extremely careful about confidentiality, especially tiny details in the text and screenshots.
  • Include screenshots and other images sent.
  • When creating a GitHub issue:
    • Use the issue description rather than comments.
    • Write an issue as a single-sentence user story is very helpful. (As the CEO, I want to X, so that Y.)
    • Don't assume people will scroll down. Put big honking screenshots at the bottom of the description, when possible (or make them smaller), rather than including them first above other text in the description.
    • Any link can be lost in the internet space time continuum, and "website time machine" doesn't always work. For ALL social media links, and maybe some other links, if the external content is necessary to understand the goal of the issue, include a copy of it in the issue description.

Rituals

  • Note: Some rituals are especially time-sensitive and require attention multiple times per day (). Set reminders for the following times (CT):
    • 9:30 AM /before start of business
    • 12:30 PM /beginning of "reserved block"
    • 6:30 PM /post-mortem days meetings