Meetings are monthly starting on the 10th day after month end.
The EBA to the CFO is the Scheduling DRI for the Monthly Key Meetings.
Whereever possible, the goal is to have all Key Meetings in a large block of time.
Having back-to-back Key Meetings has the following advantage:
EBAs can add 1 hour prep time the day before for executives to prep for all the meetings, allowing them to be more prepared than they would be with less prep time for each meeting, leading to more effective meetings
Some evidence suggests it can take upwards of 20 minutes to re-engage after context switching
This is preferred, not mandatory.
The inability to consolidate Monthly Key Meetings should never block its scheduling but moving towards these is the goal.
Required invites are the CEO, the CFO, and the function head.
Optional attendees are all other members of the e-group.
The meetings are open to all team members who are interested.
The meetings are also to be livestreamed to GitLab Unfiltered.
Functions that have these meetings are:
Engineering (Eric Johnson - function DRI)
Finance (Paul Machle - function DRI)
Infrastructure (Gerardo Lopez-Fernandez - function DRI)
Marketing (Todd Barr - function DRI)
Meltano (Danielle Morrill - function DRI)
People Group (Carol Teskey - function DRI)
Product (Scott Williamson - function DRI)
Product Strategy (Mark Pundsack - function DRI)
Sales (Michael McBride - function DRI)
Support (Tom Cooney - function DRI)
If you would like to be added to a function's Key Meeting post in #key-meetings on Slack.
There are two meeting formats.
The preferred meeting format leverages the KPI Slides project which uses Reveal JS to automate the slide preparation and leverages version control to provide a history of changes over time.
Other teams leverage Google Slides for their meetings.
Before every key meeting, the OKR page for the quarter should be updated with the current status of the KRs.
A doc will be linked from the calendar invite for participants to log questions or comments for discussion and to any additional track decisions & action items.
Wherever possible, the KPI or KR being reviewed should be compared to Plan, Target, or industry benchmark.
There is no presentation; the meeting is pure Q&A. Of course, people can ask to talk them through a slide. If you want to present, please post a YouTube video like Todd did and link that from the slide deck, agenda, and/or Slack.
The functional owner is responsible for preparing the document 24 hours advance of the meeting. The owner should update the meeting invite and send to all guests so they know the materials are ready for review.
The KPI Slides project is a GitLab-internal project since it includes KPIs that are not public.
Those slides are deployed to GitLab pages (also internal, you must have access to the project to see the website).
Each group that presents has one markdown file with their KPIs.
Every month, groups create an MR to update that markdown file.
The following slides need to be updated with an MR:
Month on the first slide
Key Business Takeaways- should especially highlight any KPIs that need attention
The following Key Meetings are automated: (all links are internal)
The functional owner will prepare a google slide presentation with the content to be reviewed.
The finance business partner assigned to the functional area will meet with the owner at least one week in advance and ensure that follow-ups from last meeting have been completed and that data to be presented has proper definitions and is derived from a Single Source of Truth.
The title of every slide should be the key takeaway
A label on the slide should convey whether the metric result is "on-track" (green), "needs improvement" (yellow), or is an "urgent concern" (red).