Update Product KPI charts in handbook and terminology for Recorded, Predicted, and xMAU

Why is this change being made?

We need alignment between all divisions leaders, CEO, and the Data team on the naming conventions for charts that have recorded, estimated, and predicted values and on xMAU naming convention. We currently have two SSOT in the handbook for this naming convention:

• SiSense Style Guide
• Three versions of xMAU

Changing the name of xMAU helps with readability on pages and ability to retain deep-links as we add more types of xMAUs.

Below are the list of changes to unify the company with one set of language, to prevent confusion, and to ensure we are working efficiently (given that name changes takes considerable bandwidth, especially with short deadlines, and deep links breaking due to other pages/references in issues ).

• Reported to Recorded
• Projected to Predicted
• MAU/TMAU/Section MAU/SMAU/GMAU/AMAU to XMAU

The immediate need for this is that this is a blocker for completing the Product Key Meeting Slide deck and affects the Data team's ability to update all the Product KPIs charts in the handbook page. This also affects updating all GMAU/SMAU charts before the end of the quarter - blocking the Product OKR as well. Moving forward, all charts in PI pages, Key Meeting Slide decks, etc will use this language for all divisions.

One additional recommendation is to only explicitly point out Estimated and Predicted since most of our charts are Recorded and would require significant effort to rework. Thanks!

Thank you all for your help!

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.