Static Site Editor 🌟 North Star Metric

Purpose

Define a north star metric for the Create:Static Site Editor group

What is a north star metric

The singular, most important, trackable action that can measures success for our group.

Our north star

We want people to use the static site editor, and use it frequently. While we hope that we bring in a new personas and in general, new GitLab users to the platform, the feature can be successful entirely within our current user base.

I propose that our north star metric should be Monthly commits from the static site editor

We would track every commit generated from the static site editor, across all customer projects (who have opted into tracking).

There are a variety of inputs that can contribute to the monthly commits metric.

• SMAU (Stage Monthly Active Users): The more users of the feature, the more commits are generated.
• Adoption: The more sites that adopt the static site editor, the more commits are generated. But users adopting the framework doesn't inherently mean they are actively using the feature.
• MRs created: Ideally there will be a many-to-one relationship between commits and merge requests. Not every commit will result in an MR, so tracking only MRs might not capture the full picture of active engagement with the feature.

Baseline

The feature isn't in production yet, so we have a baseline of 0. We'll be instrumenting our MVC to include tracking and establishing a baseline as part of our first 2-3 milestones.