Highlights/lowlights from ConvDev Index
Problem to solve
We should do a better job of teaching users how to use GitLab at its best. In https://gitlab.com/gitlab-org/gitlab-ce/issues/41780, we explored a visual representation between cycle time and deeper engagement with GitLab features.
Showing a relationship is great, but we should also show instances what they should consider focusing on to improve (and what they're doing a great job at, and should continue doing).
Proposal
- Include two "highlights" and two "lowlights" in the redesigned ConvDev Index page.
- "Highlights" should be represented by the top 2 scores in the components of ConvDev Index.
- "Lowlights" should be defined by a pre-determined order. As it's likely a few of these may be 0, we should present them in a logical way (e.g. we should present using Pipelines as a possible improvement, rather than say, Service Desk)
If the instance has no reasonable "highlights" to show, we shouldn't show this section.
"Learn more" links should go to documentation. We should consider more informative pages for these respective features, explaining the benefits and telling users how to get started in a simple, tutorial-like way.
What does success look like, and how can we measure that?
- Return activity on the page (people who view it find it worth coming back to)
- Increased DevOps score over time among instances who engage with this page (instances that use it actually use it to educate themselves on things they could be doing)