Dev:Create:Knowledge GMAU Product Performance Indicator - View/Create/Revise Designs in usage ping
⭐ ️ Product Performance Indicator - WIP
Sum of unique users who did the following:
- design view (.com FE track, SM usage ping)
- design create (.com BE track, SM usage ping)
- design update (.com BE track, SM usage ping)
Chart with both .com and self-managed
📖 Background and Overview
▶ Define your product feature's key benefit/value to customers
When Designs are viewed, created or revised we indicate growth and usage of the design across stages and features.
🥅 Define Product Performance Indicator that quantifies delivery of this "must have" value
Design Views are the most generic way we can use to indicate growth and feature adoption. Most of our work is in expanding the features that are available and in promoting the feature for the near term before we hit maturity complete.
- 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 did you pick this Product Performance Indicator for your feature/group/stage?
This is the most relevant indicator of designs being used across the team and stages. It's also the easiest indicator to move for growth as we are new.
❗ 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
- I don't know, need help to check whether this data exists or not
Please provide more details
- Currently we have instrumented a FE tracking for Design Views but the event has not shown up in our dashboard
- Currently we have a dashboard with page views using regex but it is missing the count on left/right views
- We need to instrument the Usage Ping counters for Design Views on self-managed
What is the data source for the proposed Product Performance Indicator? (Link, Explanation of how this data is captured, etc)
Design View will be captured by the full screen view of a Design.
Explanation from @.luke
When a full-sized image is displayed. This might happen within the design collection view when we haven’t (yet) generated a smaller design image (i.e., the full-size image will always be served in place of the resized thumbnail immediately after an upload, as we generate them async). We currently always serve the full-size image in the single design view. So this particular count could not reliably be used to say how many single design views had been opened, because sometimes the count will be counting views within the design collection when no thumbnail has been generated.
Who would be the best contact for the data source system? (Link or explanation)
🧩Answer these questions to provide more context
- Any alternative Product Performance Indicators you would consider, either because they are easier to get, or you are debating between that and the proposed NSM?
- Creation of designs but it does not support designs being viewing in other places like in the MR
- Does your feature play a bigger role in initial purchase, retention, or expansion/upgrade?
- Expansion mostly, designers are added to the engineering team.
- Does your feature play a bigger role in SMB sales, Enterprise sales, or both?
- Not sure yet, still dogfooding
- What are some dimensions you would expect to slice/dice your Product Performance Indicator? For example, by plan tier, by free/paid, etc.
- Tier
- User role (set during onboarding)
- Stage where viewed
- 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.
- They must have LFS enabled
- They must have adopted Issues to be able to use Designs
-
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: ______
- Please provide an example of how you would use the mock-up or chart to make the data-driven decision.
📈 Define Supporting KPI/metrics - [Optional]
- Once defined, please review with this checklist and iterate if needed
- Are these metrics an input into Product Performance Indicator?
- By improving these, do you improve the Product Performance Indicator?