Hello, I am writing this issue in the hopes of bringing attention to a select few important metrics that potentially needs a closer examination in terms of proper instrumentation. ### Metrics in need of Examination | Metric | in SaaS? | in SM? | Notes | | -------------- | ---- | ---- | -----------------------------------------------| | Multiple Approvers in Code Review | N | N | For SM - we have a multitude of correlated metrics (MR with more/less reviewers than required) but nothing that is concretely matching this exact definition. | | Approval Rules for Code Review | N | Y | | | Merge Request Dependencies | N | N | | - SaaS = GitLab Dot Com *or* Snowplow - SM = Service Ping ### Background I have conducted research ([SaaS](https://docs.google.com/presentation/d/1GjZnKwgM5672jM9o4xKIY1XoGN9VCgP2hlFI1GNQWeA/edit), [SM](https://docs.google.com/presentation/d/1QzU8_rkrhNcjQCCbWxnQjRKQURzJn1_KOhbeWOL6HM8/edit)) into determining what may be the most important product features towards eventual conversion (purchase). Furthermore, I recently was able to derive a list of the [top 33 product features](https://docs.google.com/presentation/d/1pdbrqv0tFYbhMQ5ThmjVPfQTvi3bfG6UNsZCyKc1ZEg/edit#slide=id.g153652a3f3d_0_79) and delineated whether each metric was instrumented in both SaaS and SM. Having a clean set of product metrics will enable us as a business to have a full and complete understanding of customer behavior and better help us make proper business decisions. Please let me know if there is any way I can help in spearheading this effort or if there is a method I should be aware of. Thank you for your time!