Added the new board meeting and OKR planning cadence (#33133)

re: E-group/T-Group agenda:
https://docs.google.com/document/d/1stzTCnBjdoX07fF5780vP0TM0_jdTUij8qem477098A/edit?tab=t.0

---------

Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
This commit is contained in:
Savannah Friend 2025-09-17 16:58:47 -05:00 committed by GitHub
parent d886acb0ca
commit a8081148aa
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -91,6 +91,35 @@ Departmental page structure:
- `## Rituals`
## Board meeting and OKR planning
The board meeting and OKR planning happen during the first week of the third month of every quarter. Fleet uses the following agenda to prepare, execute, iterate on, and retro its in-person board meetings and quarterly Objective Key Results (OKRs):
**Day 1 _Prepare_ (in-person):**
- Board deck finalization:
- The CEO preps keynote on plane, absorbs graphs in the airport, and derives top-level OKRs in the hotel.
- T-Group arrives midday.
- Last-minute edits with the team in the evening.
- OKR brainstorming right after (+async for the E-Group who aren't physically there).
**Day 2 _Board meeting_ (in-person):**
- Mock board meeting
- Real board meeting
- Closed session
- Dinner with the board
**Day 3 _Travel_:**
- Leave, catch up with daily work, recover, and think.
**Day 4 _Plan and finalize_ (virtual):**
- OKR planning (entire E-Group, over Zoom, everyone comes prepared) for 3.5 hours.
- OKR finalization (CEO, EA, Interim Head of People and Head of Digital Workplace & GTM Systems to clean up any details and messaging out to remind/help executives to book time with their teams if it is not booked already for Friday) for 1 hour.
**Day 5 _Communicate_ (virtual):**
- Each manager will work with their team to ratify, understand, and raise any objections or initial edits to the OKRs, all the way down to the ICs.
- CEO, EA and Interim Head of People will meet for 1 hour to decide the location of the next board meeting and email board members.
## Key reviews
Every release cycle, each department leader discusses their [key performance indicators (KPIs)](https://docs.google.com/spreadsheets/d/1Hso0LxqwrRVINCyW_n436bNHmoqhoLhC8bcbvLPOs9A/edit#gid=0) (confidential) with the CEO. KPIs are numbers measuring results and everyday excellence, usually accompanied by time-bound goals.
@ -287,9 +316,6 @@ CEO shadows join all meetings on the [CEO's calendar](https://calendar.google.co
> Please **DO NOT** add yourself as an attendee to any of the CEO's meetings. The CEO regularly meets with prospects and customers in the community, and without the context of the CEO shadow program, an unknown name on the calendar event could be mistaken for a sales tactic.
## 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.