For each executive — and some department leaders — to discuss the key metrics of that department in order to:
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:
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:
If you would like to be added to a function's Key Meeting post in #key-meetings on Slack.
There are three 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. Some teams leverage Sisense's existing automation functionality to prepare Google Slides with automated charts.
Also see First Post is a badge of honor.
The original demo and proposal of using the KPI Slide project is on GitLab Unfiltered (internal).
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:
The following Key Meetings are automated: (all links are internal)
To create these slides, you will need Editor access in Sisense.
Video with explanation of this meeting format (GitLab Internal)
Many functions or departments now have Performance Indicator pages that allow one to move top-to-bottom in the handbook to see both KPIs and PIs. Here is an example of the Senior Director of Development presenting the Development Department's KPIs and PIs in advance of their monthly Key Meeting.
This method is ideal, as it is handbook-first and makes it easy for everyone to contribute. Commentary can be added via an MR to the data/performance_indicators.yml file. The executive summary section can help consumers of the information understand where to dig in futher.
The difficulty in using performance indicator pages for Key Meetings is for groups who have a signficant number of Performance Indicators that cannot be public. For folks looking to consume this information quickly, having to 2FA into Sisense to see the information can be frustrating. For functions or departments for which this is true, it is recommended to use a different key meeting format.