Gamification of Auto DevOps (and other) setup
Problem to solve
Users are having a hard time understanding Auto DevOps and how to set it up properly to get all the functionality it offers. We did UX research and determined that a wizard walking users through setting up Auto DevOps greatly increased success. But a wizard assumes a (relatively) linear flow and there are many real-world circumstances where that linear flow isn't viable. And while you can make the wizard reentrant, being guided through previous choices repeatedly will wear on people. Soon you feel like you're fighting the tool. This is especially true when we consider the broader scope of setting up projects and groups on GitLab.
We can guide people towards successive improvements, letting them know what the next steps are, but letting them choose to complete them in their own order, on their own time. One way to handle this is via a gamification system like many others where you're presented with several steps to complete. But unlike traditional gamification, there should be no push to complete any specific number of them and users should not feel bad for only doing the parts they want to. This is just about letting them know what next steps are common and making it easy to get started.
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)