Skip to content

GitLab Next

GitLab Data Team
GitLab Data Team
Open
Opened by Keanon O'Keefe@kokeefe🚀Developer7 of 9 tasks completed7/9 tasks

Dev:Plan:Portfolio Management North Star Metric

⭐️ North Star Metric - WIP

📖 Background and Overview

▶ Define your product feature's key benefit/value to customers

Epics provide our users an easy way to collect, organize, track, and report on a collection of work that is valuable to their organization.

🥅 Define north star metric that quantifies delivery of this "must have" value

We currently are tracking Epics viewed on .COM as our NSM as:

  1. Viewing an epic is a major action that provides significant value to the user
  2. Many of our new features on Epics have landed within the last 6mo, and many Self Managed users are not on a recent version to access them

As Epics mature, we want to transition from measuring success based on number of epics viewed to actual interactions with epics themselves. While viewing an epic actual conveys a tremendous amount of value (understanding the work hierarchy and weight/scope, seeing timelines associated, health status, and discussion/comments) a true usage based metric will allow us to have deeper understanding of how and when customers leverage Epics.

Proposal

At present, we are able to see Epic Usage for self-managed instances via Usage Ping. Having the same metric for .COM would allow us to unify our data reporting across the two.

  • Once defined, please review with this checklist and iterate if needed
  • Does this support sustainable revenue growth?
  • Does this reflect customer getting value?
  • Does this measure progress?
  • Why do you pick this north star metric for your feature/group/stage?

Portfolio Management features depend on an Epic existing and having work associated to provide an Epic Tree view, and Epic Hierarchy, and a Roadmap view.

AMAU Metric

  • What is the related AMAU metric calculation?

❗ What do you need from the Telemetry/Data team?

  • The data is available but I need analytics to visualize/re-structure
  • The data is not available and I need to implement tracking (for .COM)
  • I don't know, need help to check whether this data exists or not

🧩Answer these questions to provide more context

  • Any alternative north star metrics you would consider, either because they are easier to get, or you are debating between that and the proposed NSM? No

  • Does your feature play a bigger role in initial purchase, retention, or expansion/upgrade?

Based on discussions with customers, initial purchase and expansion/upgrade are both likely outcomes.

  • Does your feature play a bigger role in SMB sales, Enterprise sales, or both?

Epic provide significant value for any org planning larger projects, from SMB to Enterprise.

  • What are some dimensions you would expect to slice/dice your north star metric? For example, by plan tier, by free/paid, etc.
  1. Plan Tier
  2. Date
  3. org/namespace size
  4. # of issues assigned
  5. meta data associates (dates, labels, etc)
  • Are there any GitLab product features that are "downstream" or "upstream" to your product feature? For example, customers have to use feature A to use your feature, or once customers use your feature, they are more likely to use another feature.

Upstream

  1. Groups/Sub-Group organization
  2. Issues
  3. Milestones (optional but helpful)

Downstream

  1. Roadmaps
  • Please attach a mock-up, drawing, or chart in another system that will think will allow you to make a data-driven decision for the propose metric. Link: Portfolio Mgmt Dashboard

📈 Define Supporting KPI/metrics - [Optional]

  • Once defined, please review with this checklist and iterate if needed
  • Are these metrics an input into north star metric?
  • By improving these, do you improve the north star metric?
Edited by Mark Wood