Package Category Maturity Scorecards
What's this issue all about? (Background and context)
As per the OKR, the Package team is going to be running the Category Maturity Scorecard research.
What are the overarching goals for the research?
Understand from the users' perspective on the viability and maturity of the Package Registry offering.
What hypotheses and/or assumptions do you have?
The latest version of the package registry stands as a Viable solution for their package manager needs.
What research questions are you trying to answer?
Do users believe that the package registry is a viable solution?
What persona, persona segment, or customer type experiences the problem most acutely?
This will probably be a mix of DevOps and/or Engineering leaders
What business decisions will be made based on this information?
Who will be leading the research?
@icamacho w/ @loriewhitaker for support.
What timescales do you have in mind for the research?
This OKR is due by April 30th. My focus on it will be in the 12.10 milestone, providing an additional 2 weeks of extra time (if required).
Relevant links (script, prototype, notes, etc.)
TODO Checklist
The process for Category Maturity lays out steps as the following:
-
Define the primary and secondary Jobs to be Done related to the Package Registry category (PM and PD) -
Define what participants would qualify for the study and create a screener in Qualtrics (PD) -
Create a recruitment issue including the survey and reach out to the Research Coordinator (PD and RC) -
Turn the JTBD defined above into research scenarios as laid out in the documentation (PD) -
Prepare the testing environment (PD and EN) -
Document the scenario, including the number of meaningful clicks. (PD) -
Have a coworker go through the defined scenario and refine if needed (Other) -
Write the discussion guide (PD and UXR) -
Schedule and perform the interviews (PD) -
Synthesize the new data from users -
Create a Maturity Scorecard issue following the instructions in the template. -
Add feedback to the Retro Issue about the experience and areas that could be improved.
Edited by Iain Camacho