Pilot: Connect UX Scorecards to Product Maturity Categories using Category Maturity Scorecards
Product Maturity Categories can be enhanced by including an objective way of measuring when an area of the product is Planned, Minimal, Viable, Complete, or Lovable.
Objective means we evaluate experiences with our users and ask them to score their experience - we do this today with UX Scorecards. If we take the grades from the UX Scorecards and apply them to our Product Maturity Categories it would look something like this:
- Definition: Elates customers by meeting and exceeding user needs. It's feature complete and a delight to use.
- How it's scored: Receives an "A" for the primary JTBD and "B's" or higher for others.
- Definition: Contains a competitive feature set that solves a JTBD, and is sufficient to displace other single-purpose DevOps tools. It has a good to excellent usability.
- How it's scored: Receives a "B" or higher for primary and secondary JTBDs.
- Definition: Can be used by users/customers to solve a real JTBD. It does not have major (blocking) usability issues but may have minor usability issues.
- How it's scored: Receives a "C" or higher for primary and secondary JTBDs.
- Definition: Provides a minimal foundation so people can see what we're solving for and to generate customer feedback. It does not have major (blocking) usability issues but may have minor usability issues, especially due to incompleteness of the feature.
- How it's scored: Assigned by the Product Manager (PM) and Product Designer (PD) based on Solution Validation activities.
- Definition: Not yet implemented in GitLab but on our roadmap.
- How it's scored: This is not scored because it does not exist in the product.
Goal: Test our hypothesis that we can enhance our ability to assess Product Maturity by using UX Scorecards. We'll call these specific scorecards, Category Maturity Scorecards to avoid confusion.
- PM and UX to collaboratively identify JTBDs for 6 categories to work on for the quarter.
- At least 5 participants are observed and then asked to score the experience using the Grading rubric.
- Participant-given scores are averaged to determine the overall grade for the UX Scorecard.
- Match scores to the Product Maturity categories:
- If a section is currently labeled as "Complete" but receives a "C", then we need to make some adjustments to the experience for it to retain that label.
- If a section is currently labeled as "Viable" and receives a "C", then we have appropriately labeled the maturity of the section.
Note: One JTBD is not enough to fully determine a Product Maturity category. Primary and secondary JTBDs need to be evaluated.
Known gap: There is still an angle we're missing from the Product side that includes how we measure against competitors and/or fill gaps in the market. [Need PM input here!]